On Wed, 11 May 2016, Bruno Randolf wrote:
On 10/05/16 21:00, Ben Greear wrote:
Here is an initial pass at a script to gather pertinent info about
a LEDE (or similar) system. Suggestions for improvement are welcome.
If someone could add a way to put the git commit ID(s) into
the file system somewhere, I think that would be an excellent
addition.
And once the script is in place, a way to call it through the web UI would
be most welcome.
Some of these commands could be replaced by ubus calls. The benefit of
this is could be that we get it structured as JSON so it's easier to
parse and easy to upload to a webservice (e.g. for submitting test
results or bug reports).
I like, however I am a little concerned about leaking authentication info.
Especially if you have more 'interesting' configs.
I understand the need to have the basic interface config info, but do we really
need the IP details and routing info? I can see some cases where they would
matter, but most of the time they don't.
I'm not arguing for security by obscurity, but I am willing to argue against
providing info to attackers instead of making them work a little for it :-)
David Lang
_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
