![john the ripper tool john the ripper tool](https://img.wonderhowto.com/img/13/66/63647565251018/0/cracking-passwords-using-john-ripper.w1456.jpg)
INSERT INTO `news` VALUES (1,'This is the first one',''),(2,'This is the second point',''),(3,'This is the third point','') *!40000 ALTER TABLE `news` DISABLE KEYS */ ) ENGINE=MyISAM AUTO_INCREMENT=22 DEFAULT CHARSET=utf8 `id` int(10) unsigned NOT NULL AUTO_INCREMENT, *!40000 ALTER TABLE `admin` ENABLE KEYS */
![john the ripper tool john the ripper tool](https://openwall.info/wiki/_media/john/johnny/johnnyscreen-7.png)
INSERT INTO `admin` VALUES (1,'admin','AA00A') *!40000 ALTER TABLE `admin` DISABLE KEYS */ ) ENGINE=MyISAM AUTO_INCREMENT=4 DEFAULT CHARSET=utf8 `user_pass` varchar(255) NOT NULL DEFAULT '', `user_name` varchar(255) NOT NULL DEFAULT '', `user_id` int(10) unsigned NOT NULL AUTO_INCREMENT, *!40101 SET character_set_client = utf8 */ The decoding result is as follows: - MySQL dump 10.13 Distrib 5.7.19, for Linux (i686) In other words, there are two passwords in the traffic packet: user passwords and website background passwordsĪfter searching, we found that the traffic packets of sql files were read using pseudo protocolĮxport all the files in the traffic package and find test.sql base64 encoding: After obtaining, submit using MD5 encryption. They are user passwords and website background passwords. However, we can directly track the flow direction here You can recover it by using the vim -r file name. This file is generated by an abnormal exit when editing a file with vim. The topic gives us a flow package, analysis In a competition, the Masters said they needed to use the tool and learn it