netdev - Re: [RFC][GENETLINK] introduce command names

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061204092857.GO8693@postel.suug.ch>
Date:	Mon, 4 Dec 2006 10:28:57 +0100
From:	Thomas Graf <tgraf@...g.ch>
To:	jamal <hadi@...erus.ca>
Cc:	davem@...emloft.net, netdev@...r.kernel.org
Subject: Re: [RFC][GENETLINK] introduce command names

* jamal <hadi@...erus.ca> 2006-12-02 07:11
> [GENETLINK] introduce command names
> 
> Introduce optional command names.
> While command names can be put in user space by the author of the
> command, this alleviates things for the discovery process without
> requiring any user space code written.
> In a recent tutorial that i gave, the desire for this feature was
> the highest.

I assume you're planning to export this to userspace at some point?
What's the real advantage besides that when listing avaiable
operations we can output names instead of numbers? Userspace should
be aware of operation numbers when using it. I'm all for this if
the direction is to move towards having some form of scriptable
genetlink tool which can be used to communicate with simple genetlink
families.

I guess the desire was the highest because you sold it as such :-)
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html