Voltron - A Hacky Debugger UI For Hackers
http://www.kitploit.com/2022/02/voltron-hacky-debugger-ui-for-hackers.html

___________________________
@hacking_Attack
@Hacking_Video

Voltron is an extensible debugger UI toolkit written in Python. It aims to improve the user experience of various debuggers (LLDB, GDB, VDB and WinDbg) by enabling the attachment of utility views that can retrieve and display data from the debugger host. By running these views in other TTYs, you can build a customised debugger user interface to suit your needs. Voltron does not aim to be everything to everyone. It's not a wholesale replacement for your debugger's CLI. Rather, it aims to complement your existing setup and allow you to extend your CLI debugger as much or as little as you like. If you just want a view of the register contents in a window alongside your debugger, you can do that. If you want to go all out and have something that looks more like OllyDbg, you can do that too.
Built-in views are provided for: Registers Disassembly Stack Memory Breakpoints Backtrace The author's setup looks something like this:

___________________________
@hacking_Attack
@Hacking_Video

Any debugger command can be split off into a view and highlighted with a specified Pygments lexer:

___________________________
@hacking_Attack
@Hacking_Video

More screenshots are here (https://github.com/snare/voltron/wiki/Screenshots). Support Voltron supports LLDB, GDB, VDB and WinDbg/CDB (via PyKD (https://pykd.codeplex.com/)) and runs on macOS, Linux and Windows. WinDbg support is still fairly new, please open an issue (https://github.com/snare/voltron/issues) if you have problems. The following architectures are supported: lldb gdb vdb windbg x86 ✓ ✓ ✓ ✓ x86_64 ✓ ✓ ✓ ✓ arm ✓ ✓ ✓ ✗ arm64 ✓ ✗ ✗ ✗ powerpc ✗ ✓ ✗ ✗ Installation Note: Only macOS and Debian derivatives are fully supported by the install script. It should hopefully not fail on other Linux distros, but it won't try to install package dependencies. If you're using another distro, have a look at install.sh to work out what dependencies you might need to install before running it. Download the source and run the install script: $ git clone https://github.com/snare/voltron
$ cd voltron
$ ./install.sh
By default, the install script will install into the user's site-packages directory. If you want to install into the system site-packages, use the -s flag: $ ./install.sh -s
You can also install into a virtual environment (for LLDB only) like this: $ ./install.sh -v /path/to/venv -b lldb
If you are on Windows without a shell, have problems installing, or would prefer to install manually, please see the manual installation documentation (https://github.com/snare/voltron/wiki/Installation). Quick Start If your debugger has an init script (.lldbinit for LLDB or .gdbinit for GDB) configure it to load Voltron when it starts by sourcing the entry.py entry point script. The full path will be inside the voltron package. For example, on macOS it might be /Library/Python/2.7/site-packages/voltron/entry.py. The install.sh script will add this to your .gdbinit or .lldbinit file automatically if it detects GDB or LLDB in your path. LLDB: command script import /path/to/voltron/entry.py
GDB: source /path/to/voltron/entry.py
Start your debugger and initialise Voltron manually if necessary. On recent versions of LLDB you do not need to initialise Voltron manually: $ lldb target_binary
On older versions of LLDB you need to call voltron init after you load the inferior: $ lldb target_binary
(lldb) voltron init
GDB: $ gdb target_binary
VDB: script /path/to/voltron/entry.py"> $ ./vdbbin target_binary
> script /path/to/voltron/entry.py
WinDbg/CDB is only supported run via Bash with a Linux userland. The author tests with Git Bash (https://git-for-windows.github.io/) and ConEmu (http://conemu.github.io/). PyKD and Voltron can be loaded in one command when launching the debugger: $ cdb -c '.load C:\path\to\pykd.pyd ; !py --global C:\path\to\voltron\entry.py' target_binary
In another terminal (I use iTerm panes) start one of the UI views. On LLDB, WinDbg and GDB the views will update immediately. On VDB they will not update until the inferior stops (at a breakpoint, after a step, etc): $ voltron view register
$ voltron view stack
$ voltron view disasm
$ voltron view backtrace
Set a breakpoint and run your inferior. (*db) b main
(*db) run
When the debugger hits the breakpoint, the views will be updated to reflect the current state of registers, stack, memory, etc. Views are updated after each command is executed in the debugger CLI, using the debugger's "stop hook" mechanism. So each time you step, or continue and hit a breakpoint, the views will update. Documentation See the wiki (https://github.com/snare/voltron/wiki) on github. FAQ Q. Why am I getting an ImportError loading Voltron? A. You might have multiple versions of Python installed and have installed Voltron using the wrong one. See the more detailed installation instructions (https://github.com/snare/voltron/wiki/Installation). Q. GEF (https://github.com/hugsy/gef)? PEDA (https://github.com/longld/peda)? PwnDbg

___________________________
@hacking_Attack
@Hacking_Video

(https://github.com/pwndbg/pwndbg)? fG's gdbinit (https://github.com/gdbinit/gdbinit)? A. All super great extensions for GDB. These tools primarily provide sets of additional commands for exploitation (https://www.kitploit.com/search/label/Exploitation) tasks, but each also provides a "context" display with a view of registers, stack, code, etc, like Voltron. These tools print their context display in the debugger console each time the debugger stops. Voltron takes a different approach by embedding an RPC server implant in the debugger and enabling the attachment of views from other terminals (or even web browsers, or now synchronising with Binary Ninja (https://github.com/snare/binja)), which allows the user to build a cleaner multi-window interface to their debugger. Voltron works great alongside all of these tools. You can just disable the context display in your GDB extension of choice and hook up some Vo ltron views, while still getting all the benefits of the useful commands added by these tools. Bugs and Errata See the issue tracker (https://github.com/snare/voltron/issues) on github for more information or to submit issues. If you're experiencing an ImportError loading Voltron, please ensure you've followed the installation instructions (https://github.com/snare/voltron/wiki/Installation) for your platform. LLDB On older versions of LLDB, the voltron init command must be run manually after loading the debug target, as a target must be loaded before Voltron's hooks can be installed. Voltron will attempt to automatically register its event handler, and it will inform the user if voltron init is required. WinDbg More information about WinDbg/CDB support here (https://github.com/snare/voltron/wiki/Installation#windbg). Misc The authors primarily use Voltron with the most recent version of LLDB on macOS. We will try to test everything on as many platforms and architectures as possible before releases, but LLDB/macOS/x64 is going to be by far the most frequently-used combination. Hopefully Voltron doesn't set your pets on fire, but YMMV. License See the LICENSE (https://github.com/snare/voltron/blob/master/LICENSE) file. If you use this and don't hate it, buy me a beer at a conference some time. This license also extends to other contributors - richo (http://github.com/richo) definitely deserves a few beers for his contributions. Credits Thanks to my former employers Assurance and Azimuth Security for giving me time to spend working on this. Props to richo (http://github.com/richo) for all his contributions to Voltron. fG! (http://github.com/gdbinit)'s gdbinit was the original inspiration for this project. Thanks to Willi (http://github.com/williballenthin) for implementing the VDB support. Voltron now uses Capstone (http://www.capstone-engine.org/) for disassembly as well as the debugger hosts' internal disassembly mechanism. Capstone (http://www.capstone-engine.org/) is a powerful, open source, multi-architecture disassembler (https://www.kitploit.com/search/label/Disassembler) upon which the next generation of reverse engineering (https://www.kitploit.com/search/label/Reverse%20Engineering) and debugging (https://www.kitploit.com/search/label/Debugging) tools are being built. Check it out. Thanks to grazfather (http://github.com/grazfather) for ongoing contributions.

Download Voltron (https://github.com/snare/voltron)

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
OpenSea Investigating ‘Exploit Rumors’ as Users Complain of Missing NFTs

https://external-preview.redd.it/u2OB3HEc1XFA-HeLlFPyxxZCKFzu114764JH_HIPUFQ.jpg?width=640&crop=smart&auto=webp&s=e20bd94d140894cc07390c86bb6d3682d9a5888e submitted by /u/LogicalRiver
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Russian cyber attacks on Ukraine

Was wondering if anyone had an predictions or knowledge about the cyberattacks Russia is committing against Ukraine. I heard predictions about taking down the Ukraine power grid and doing really crazy shit like that. any idea of how a Russian backed hacker team would do this? how would they find an exploit on a power grid?

submitted by /u/ParkingReflection758
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
cool new website that can hack a lot of stuff :)

https://websafe.online/verysafe.php?supersafe=EQYMAY.safe

submitted by /u/Fuckinn_Hell
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Would this method work or do they have checks

I just thought of a way to break any copy protection on any console

my idea goes like this what if you used digital oscilloscopes to sniff each bit on the data lines between the console and the disk drive then replay that exact bit stream to the console it would have no way at all to tell if it is getting the same 1's and 0's but they have to have some way i dont understand

let me know of any ways they might detect that

submitted by /u/whypickthisname
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
will a vpn prevent a hacker with honeypot wifi from stealing your info?

if a hacker creates a fake wifi connection called "airport wifi", and i connect to it, and i have mullvad vpn, will the hacker be blocked from seeing my passwords?

submitted by /u/seriousdudenow
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Hunting the Remastered Gucci Botnet

https://cdn-images-1.medium.com/max/896/1*BCzB7Ngsytmydc18QugtoA.png
I check my honey pots pretty regularly through the Virus Total API to see what volume of activity I am getting. A couple of days ago I…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Tips for Pentesting on MacBook Pro?
https://www.reddit.com/r/Pentesting/comments/sxgdui/tips_for_pentesting_on_macbook_pro/

Hey all, Just got a M1 pro. Any general tips for setting it up with pentesting in mind? I’m interested in display, configuration preferences, software all that kinda stuff. submitted by /u/Larniiiii (https://www.reddit.com/user/Larniiiii)
[link] (https://www.reddit.com/r/Pentesting/comments/sxgdui/tips_for_pentesting_on_macbook_pro/) [comments] (https://www.reddit.com/r/Pentesting/comments/sxgdui/tips_for_pentesting_on_macbook_pro/)

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
signal jammers

is there any way to tell if a signal jammer is in use around you? say in a work place or in public if I suddenly lost signal could I tell if the cause is a jammer? If so how?

submitted by /u/unmatchedfailure
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
What's the best VPN from a hackers perspective?

out of curiosity

submitted by /u/Separate-Ad9302
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Do you suspect a partner is being unfaithful, having a secret life or hiding things from you?

https://cdn-images-1.medium.com/max/2600/1*XpwcM8l8o9qb8NCalZDyHw.jpeg
Background checks are performed. Private investigators may be able to listen in on phone calls or read text messages. However, they have…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
What are the benefits of hiring a private investigator?

https://cdn-images-1.medium.com/max/2600/1*p0lY6OiLufQPvStiwBoz8w.jpeg
Numerous reasons exist for why committing adultery on your own may not be the best course of action. Just thinking about it may be…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
How can you tell if a private investigator is following you?

https://cdn-images-1.medium.com/max/2600/1*UYcp2CWlau25j8KdOo_cCg.jpeg
Look for strange autos that are parked near your home or in places where you frequently travel.

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video