From: Kevin J. <ke...@in...> - 2009-09-05 16:14:33
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I'm currently working on adding some additional functionality to > Laudanum. I'm wondering what the best approach is in terms of file > structure. > > Should I add to the existing shell page, should there be a "utility" > page for selecting prebuilt chained commands/functionality, or > should each function have it's own page? I like the idea of separate utility pages. I am hoping to get things checked into SVN tonight. If you would like, we can provide SVN access and add you to the project? > > Examples of functions I'm working on are automatically searching for > and attempting to display commonly grabbed and sensitive files such > as passwd, shadow, ssl keys, ssh keys, etc. Another is providing an > IP address and injecting BeEF hooks in to the existing web pages. I think both of these are excellent. We need to make sure that we continue the scope limiting features. So for example, the BeEF injection hook could also include the IP limiting feature so that it would only inject if the requester was from an IP in scope? Make sense? Kevin Kevin Johnson Senior Security Analyst InGuardians, Inc. office: 202.448.8958 cell: 904.403.8024 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAkqijlYACgkQGDcWptZ2zmQPxACfckAafDRxP7M1oJpOxG0cMeSY XJcAnjLms83fvwYtWP92M2ohw1XZyCCY =QZhV -----END PGP SIGNATURE----- |