[NSE API] Separate Dnet Objects?

[Kris Katterjohn <katterjohn () gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey everyone,

I have a question about the design of the NSE API: why is a separate
object needed for sending ethernet frames via dnet?

The socket object created by nmap.new_socket() is used for
connect()-style sending and receiving, and also for receiving via pcap.
 But for sending ethernet frames, an entirely different object has to be
created.  Why isn't dnet available through the socket object?

I see a couple different ways to organize the socket object(s):

- - A connect()-only-style object via nmap.new_socket() and a separate
"raw" object that includes pcap and dnet.

- - An all-in-one object with connect()-style networking, raw packet
receiving via pcap, and raw ethernet frame sending via dnet.  This is
what I prefer.

Is there are particular reason for this?  If not, is it too late to
change this?  Only promiscuous.nse appears to require the dnet
functionality, so that's the only script that would need changing.
Maybe an NSE student can do this this summer.

Feel free to smack me if there's an obvious reason for this separation
that I'm just not seeing :)

Thanks,
Kris Katterjohn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBR+xfBf9K37xXYl36AQJvSw/9GGqgqL6jrdywzMc9S5jqZtz3KDQIsBJi
HeiaLV2cq3WiGAiZZeDt3jzHzMXZo9WMV0DR5JbETrsqJB1sGzRi9C5j+oadxVJ/
xRKBXwoDwEk3NMe4giCQGofUC0baIbo9i+LWAP7KlJH7BcJtMXaK46qYJicLuqzh
rsXUvAA0nW/fde/jBWefi1qvys4+ayUdCwIs3eQBo9CTP8IzDLSkXhqUHsoMyWgm
JQiwf2zmv0yjnTqyk59R5WXUHEJZ8nP5oDgYWIBDS0voEw42i6qiGuGE33ivM0im
ha5o0p7zIUMFoIK2+EhMayalGWSsmzbp3sXbl1cUm+bqvU3eteZt9zTACMmV23mA
Kpphd7JvW3TS/N0TLf3TA4ejS5EPwI/8Mc5FBxbXK7idZTCWSwM6IFCxW0xrGHn1
MrwgeRrOxaauJiI/7w8DTRwTu+PEals0zgJVWKr41TWJH8CiLO5vgxMM1rNKPOaV
6NtuDekjOpykhZnKULf2faMPguj4Uu9wQ89lB0mR5B6JbgDYp3rU1S7aNcpHOPue
uOnxA8I8Btl3C1aqtxZXOgZMXSUHBDxd69GQXG/tzfIqzpmetMQ9EMpTOICZT9LT
ANX5pO/0uUrebM6DYgdq24cx9JSWUYClemlc4oQe2JO61MZFAG8Iqa9XbwGybIKO
u4IeXEFmJlE=
=Z3Fp
-----END PGP SIGNATURE-----

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org