WoJ

84 reputation

bio	website
	location	France
	age
visits	member for	1 year, 5 months
	seen	12 hours ago
stats	profile views	8

	84 reputation	bio	website		visits	member for	1 year, 5 months
6 badges		location	France		seen	12 hours ago

summary answers questions tags badges favorites bounties reputation activity

33 Actions

suggestions reviews revisions comments badges posts accepts all

12h	comment	POC of a Java exploit using leftover JREs @Anorov: on the browsers I tested (Chrome, IE) there is just a warning about using the applet in the first place. This is not a deterrent for users determined to get hacked :) As for the payload -- I wanted to show a true exploit (working on systems with leftovers, not working on others)
1d	comment	POC of a Java exploit using leftover JREs @Ramhound: the question would be: would someone have a ready solution, or anything (a comment, a pointer) which could help me to build mine? (I was wrong assuming this is obvious, per the downvote. It is true that I could have just posted this for the sake of expressing my dreams :))
1d	revised	POC of a Java exploit using leftover JREs typo
1d	revised	POC of a Java exploit using leftover JREs added nessus reference
1d	asked	POC of a Java exploit using leftover JREs
Feb 5	answered	RSS Feeds: restrict access
Dec 4	awarded	Scholar
Dec 4	accepted	passphrases - lowercase and dictionary words
Aug 8	comment	Does password protecting an archived file actually encrypt it? The Appendix of the document mentions that AES 128 is used by default for Office for 2007+ . I will be meeting some MS security teams by autumn so I will ask the question about legacy algorithms and update my answer.
Aug 8	answered	Does password protecting an archived file actually encrypt it?
Apr 12	comment	nessus scan against metasploit exploits Thanks - I will be looking into that as well and update this page if any luck (I have some years of dev lagging :))
Apr 11	comment	nessus scan against metasploit exploits As for the ability to run scans from metasplot, I mentioned I am aware of it but it does not help to reduce the number of tests (it basically allows to run & import scan results to be reused by Metsploit)
Apr 11	awarded	Commentator
Apr 11	comment	nessus scan against metasploit exploits Thanks for the answer -- unfortunately what I am trying to do is to precisely fix the lack of persistent filtering in Metasploit you mentioned. Currently one needs to recreate the policy at each plugin update, which is not realistic in a distributed environment where the scans run automatically.
Apr 10	comment	nessus scan against metasploit exploits I am not sure I understand your comment. Current versions of Nessus are not that easy to script, but this is doable. My question was about the approach to match Metsploit and Nessus vulnerabilities. The 'unfathomable' part is about a critical option introduced to nessus but effectively hardly useable in an enterprise setup (where you have to run automated scans)
Apr 10	asked	nessus scan against metasploit exploits
Dec 13	comment	passphrases - lowercase and dictionary words I do believe that - please have a look to my other comments with an estimation on paraphrases based on common scrabble words. There is always the possibility of someone choosing "passwordpasswordpassword" as their passphrase (to take an example of a commonly used password) but this is also a matter of education - they can also write down their passwords on their whiteboards if they get too complex. Finding the right balance (complexity, ease of cracking, user choice of passwords, technical complexity to implement the restrictions, ...) is what I am looking for.
Dec 13	awarded	Supporter
Dec 13	comment	passphrases - lowercase and dictionary words About the password choice: "ilovemymum" would not meet the length restriction, "ilovemymumverymuch" would be fine and would be a good passphrase. I actually want people to choose easy to remember passphrases, thus the initial post.
Dec 13	comment	passphrases - lowercase and dictionary words Thanks for some interesting points. As for the DoS -- I am looking at avoiding a simplistic DoS on the login. A DDoS will in practical terms always be a threat and this is another story. The pr-IP login limit is something we will be putting in the design as well as the anti-CSRF measures (which are part of the OWASP adherence we design around).