Go beyond the impossible!
nokitel
As some of you might already know, me and Fredrik have been working on a low-level network library for the .Net framework.
Its name is nokitel and this post will cover the features of the library since the documentation is not finished yet.
- Sniffing
- Packet Crafting
- WiFi Analysis
- Premade TCP Client (With SOCKS5 support.)
- RealVNC 4.1.1 – Remote Authentication Bypass Vulnerability Scanner
- Simple packet parsing for the following protocols; ARP, ICMP, IGMPv2, IGMPv3, IPv4, TCP, UDP, DNS, Frame-Relay (Ethernet).
- Statistics of your NIC’s (Network Interface Cards), and various other network-related features.
- All functionality and information based on the two Windows WMI classes Win32_NetworkAdapter and Win32_NetworkAdapterConfiguration.
- ARP Scanning – Reversed engineered from Cain & Abel (oxid.it)
- …And of course, control over the already established TCP and UDP sockets handled by Windows.
The ones of you with some experience in raw packet crafting will probably enjoy playing around with this and the following posts will contain examples on how this library can be used.
The documentation is also being written and a simple tutorial for you to get a clue on how to use it as optimized as possible!
Sourcecode can be found here, and please give us credit and/or link to AckAck if you choose to use this in your own (none private) projects.
I hope you have great fun with this nifty library and if you extend it and would like us to update the original nokitel, just contact us on h@ackack.net !
Ciao!
| Print article | This entry was posted by Mathias Karlsson on 10/07/2010 at 23:00, and is filed under .Net, Network Security, nokitel. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site. |
about 1 month ago
Mathias, IP.vb – GetIPChecksum function has an error. IP.vb lines 115 and 116.
Peace
about 1 month ago
Do you mind sharing a snippet of your code?
I fail to identify the flaw, and what’s causing it.
about 1 month ago
My pleasure…..
DWORD(&H3) = (IIf(.DontFragment, &H1, &H0) << &HE) Or _
(IIf(.MoreFragments, &H1, &H0) << &HD) Or
.FragmentOffset
.FragmentOffset is orphaned, possibly a missing line continuation after the second 'Or'?
about 1 month ago
Oh yeah, I just noticed, however I was still able to compile it without any error in VS 2010.
Thanks for pointing it out though!
Uploading a patched version.
about 1 month ago
Do you see any advantage to my running through code analysis with Option Strict On in VS10? Perhaps some gains in performance? If so, I’ll proceed…
about 1 month ago
Yes. You should do that.
However we choosed not to so during the fundamental development of the nokitel library.
I just wanted it to be out; it’s still in a beta-phase.
I believe it’s time for me to turn on Option Strict and Option Explicit now as well. For the same reason as you, in order to gain even more performance.
If you wish, you can compile the library for the correct CPU-architecture as well, and you might earn an even greater performance boost.