46,993 reputation
12109197
bio website en.wikipedia.org/wiki/…
location United Kingdom
age 26
visits member for 2 years, 11 months
seen 20 hours ago

Pentester, ex-developer, security researcher, reverse engineer, electronics tinkerer, internet activist, zombie eradicator, promulgator of useless facts, shrubbery inspector, bacon aficionado, devourer of donuts.

Strengths: Security, Crypto, Win32 API, C#, .NET, PHP, x86 assembly

All answers and comments are encrypted with ROT256-ECB.

Opinions are my own. Advice provided with no warranty.


Aug
8
comment Header opening a PDF file, can someone hack a website from there?
@Paul He's saying that if a second user can control the PDF somehow, they could infect people. You just have to look out for vulnerabilities that might allow one user to upload a PDF that might overwrite another user's.
Aug
7
comment Where should I go from here to be a pentester?
Under the question there's a "flag" link. Click it, and choose "Exact duplicate". From there you can enter a link, or browse similar questions.
Aug
7
comment Why shouldn't we roll our own?
@AndrewSmith Sorry, but when every security expert I've ever spoken to or read articles by disagrees with you, I cannot take your views as having any merit. Security by obscurity has been proven to be absolutely devastatingly broken as a concept, both in terms of theory and practice. Modern cryptography that has undergone stringent peer review over a long period, with proper security proofs and complete mathematical analysis, is the only guarantee of any real cryptographic security.
Aug
7
comment Diagnosing possible svchost.exe thread on Windows 7
@yakiv Not got round to it, sorry. Crazy busy recently! It'll probably have to be tomorrow or later.
Aug
7
comment Mars Curiosity Rover Security
Related tweet.
Aug
7
comment Can signing too much compromise a private key?
That's a dangerous assumption to make.
Aug
7
comment Why shouldn't we roll our own?
@Ramhound I'm aware, I'm just asking the question for the sake of having a go-to answer. It'd be great if you could offer a second answer to compete with dr jimbob's.
Aug
7
comment Publicly available Botnet Traffic dataset
Just to clarify, are you looking for packet dumps to/from infected machines, packet dumps to/from C&C servers, or samples of the malware itself?
Aug
7
comment Why shouldn't we roll our own?
@AndrewSmith The comments are not for sharing of personal opinions or random chatter. They are for asking for clarification about a question. You've been warned about this before, and I've seen you do it again on several other questions. If you want to chat, please do so in the DMZ.
Aug
6
comment Dangers of a vulnerability in a local installer?
Ah, ok. Still, if you're shipping to customers, 99% of this still stands.
Aug
6
comment Why shouldn't we roll our own?
For reference, D.W. posted a great starting point here.
Aug
6
comment How many possibilities can today's computers check (per second) in a SHA512 hash of a 50-byte-long random entry?
The salt would never be typed in by a person. It's generated randomly and stored in the database with the hash.
Aug
6
comment How many possibilities can today's computers check (per second) in a SHA512 hash of a 50-byte-long random entry?
You're making this a lot more complicated than necessary. I suggest you read through the answer I linked (this one) and improve your understanding of password hashing and salting schemes before continuing.
Aug
6
comment How many possibilities can today's computers check (per second) in a SHA512 hash of a 50-byte-long random entry?
Where are you storing it, then? I sincerely hope that the salt is unique to each user.
Aug
6
comment How many possibilities can today's computers check (per second) in a SHA512 hash of a 50-byte-long random entry?
What do you mean by "the salt will remain in the hash"? If you hash the salt, you cannot retrieve the original salt, so how do you verify that a password is correct?
Aug
6
comment How many possibilities can today's computers check (per second) in a SHA512 hash of a 50-byte-long random entry?
No, that's incorrect. The attacker already knows your salt, because he's breached your database to get the hash. The point of the salt is to make every hash unique, so that a precomputed database cannot be used to look up all hashes and get the plaintext. The reason you should use a large random salt is that it makes the probability of duplicates near zero.
Aug
6
comment Detect changes in /boot when using full disk encryption
+1 for going to the heart of the problem - you can't verify anything absolutely, just do the best you can with the tools and information you have.
Aug
6
comment What CVE identifier will follow after CVE-2012-9999?
+1 for the advice around emailing Mitre. They're curt, professional and accomodating, even in cases where the vendor is being (to put it bluntly) an asshole.
Aug
6
comment My server is being DDoS'ed with 13 gbit and my provider nulled my ip, taking down my server - what can i do
Duplicate of How can a Software application defend against DoS or DDoS? and Accessing a site which is under DDoS?
Aug
6
comment What's the deal with SMS archiving?
There are a number of possibilities, but it's difficult (without knowing internals of your provider's systems) to identify which is the right one. It could be caching / archives, it could be due to an old delivery request stuck in the system, or it could just be that your handset tripped out and sent an old text again.