Omphalos: Difference between revisions
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
* '''The latest release is [https://github.com/dankamongmen/omphalos/releases/tag/v0.99.8 0.99.8], released 2019-04-16.''' | * '''The latest release is [https://github.com/dankamongmen/omphalos/releases/tag/v0.99.8 0.99.8], released 2019-04-16.''' | ||
* [[Arch]]'s AUR contains [https://aur.archlinux.org/packages/omphalos/ omphalos] | * [[Arch]]'s AUR contains [https://aur.archlinux.org/packages/omphalos/ omphalos] | ||
Omphalos is not a "''point-and-click''" tool so much as "''pull the pin''" or perhaps "''spray the area''". Default behavior is to redirect and seize all traffic, attack weak cryptosystems, archive authentication materials, and learn everything that can be learned. Ideally, a tiny microprocessor would be paired with power and a network device, stealthily physically inserted into a network, and left there; <tt>omphalos</tt> and [[Hackery#liburine|liburine]] would then combine to provide complete network dominance. I hope to combine network programming and the techniques of high-performance computing to create a tool capable of much havoc. | Omphalos is not a "''point-and-click''" tool so much as "''pull the pin''" or perhaps "''spray the area''". Default behavior is to redirect and seize all traffic, attack weak cryptosystems, archive authentication materials, and learn everything that can be learned. Ideally, a tiny microprocessor would be paired with power and a network device, stealthily physically inserted into a network, and left there; <tt>omphalos</tt> and [[Hackery#liburine|liburine]] would then combine to provide complete network dominance. I hope to combine network programming and the techniques of high-performance computing to create a tool capable of much havoc. | ||