I've seen the python pty trick in a few places, first when taking OSCP labs. However, if you've noticed there's still some problems. 2 years ago at HackFest @r00k [https://twitter.com/_r00k_] did a presentation where he improved the quality of the shell dramatically. Last year at HackFest, @jeffmcjunkin
One issue I've had with the new hashcat 3 is the ability to run it within 32-bit linux VM's. Intel doesn't make 32-bit OpenCL drivers [https://software.intel.com/en-us/articles/opencl-drivers#core_xeon]. IBM made some back in 2011 apparently (PDF link [https://www.ibm.com/developerworks/community/files/
I was trying something very simple today on Kali 2016.1 (Kali 2 rolling), passing the hash to an RDP session based on this Kali blog post [https://www.kali.org/penetration-testing/passing-hash-remote-desktop/]. It should have been as simple as apt-get install freerdp-x11 and then the correct command. Again and
I'm working through exercises in pen-testing and I ran into an slight problem. How do I tell what user I'm currently logged in as? * whoami - Doesn't work, box is too old (pre-vista) * echo %username% - Literally echos %username%, variables don't work. * set - Doesn't display username, and home directory
The official announcement is on the Hashcat forums [https://hashcat.net/forum/thread-4880-post-27398.html#pid27398]. This is amazing news, I can't wait to see what this brings. Among the things I can't wait for... * OSX Support * Huge improvements in several algorithms * Contributions from others in the security industry * Better integration
So I think it's time for my first "opinion piece". This is in response to the following article, and several tweets I've seen saying that pulling security clearances is a bad idea and amounts to a blame the victim mentality. http://arstechnica.com/security/2015/09/dhs-infosec-chief-we-should-pull-clearance-of-feds-who-fail-phish-test/ > "I get the
You can thank the user testingresults over on the Kali forums [https://forums.kali.org/showthread.php?485-How-To-Securely-Sanitize-your-Trash] for this one. That link will take you to his guide, which is much better than what I have. Very quick reproduction of the guide follows. apt-get install scrub vim empty_trash.