Forgot your password?
typodupeerror

Comment: Re:Original premise is false (Score 1) 573

Yes, exactly. (My day job is static analysis)

"Many Eyes" are great for identifying and fixing the broken build... but have no good track record for monitoring security design and implementation flaws.

For security infrastructure critical code, the available tools should be coming up spot clean. This is absolutely not the case with Openssl.

Comment: Re:well, almost (Score 1) 143

by FormOfActionBanana (#46486893) Attached to: Weak Apple PRNG Threatens iOS Exploit Mitigations

repeatedly hashing a counter that is set with a random seed

But I think that's exactly why you don't roll your own. That would be a predictable sequence. I could make a rainbow table of sha1('1'), sha1('2') etc. up to 4 trillion, and then by sampling a few numbers from your stream I could very quickly identify the current counter value and the next sequences for ever. Total fail, and if the seed is the system time this is only a level of abstraction more difficult. (Chess & West, p. 398)

Comment: Re:Many Eyes (Score 1) 88

by FormOfActionBanana (#46415951) Attached to: Ask Slashdot: Reviewing 3rd Party Libraries?

That's utterly crap advice. Since a lot of softwares in popular, active use have critical vulnerabilities.

The example quoted just above (http://ask.slashdot.org/comments.pl?sid=4862577&cid=46414687) in which nobody got the sarcasm... says:

You know there won't be any bugs in those, or if there are they'll be very quickly fixed and not sit there unnoticed for years.

He was referring to https://www.gitorious.org/gnut... and https://www.imperialviolet.org..., not to mention http://bsd.slashdot.org/story/... which also sat unnoticed for years.

Comment: OpenBSD and the 1000M limit (Score 1) 290

by FormOfActionBanana (#46413543) Attached to: Interview: Ask Theo de Raadt What You Will

The last time I tried to run OpenBSD, it was so I could test our static analyzer Fortify SCA on the kernel.

One thing that really held me back in my research is that processes were limited to about 1 Gigabyte of RAM each. What exactly is the reasoning behind this hard limit?

Note: I never finished my work, but it would be totally cool to compete this someday.

Comment: OWASP (Score 5, Informative) 120

OWASP has guidance; for instance, here: https://www.owasp.org/index.php/IOS_Developer_Cheat_Sheet#Insecure_Data_Storage_.28M1.29

From https://www.owasp.org/images/5/5e/Mobile_Security_-_Android_and_iOS_-_OWASP_NY_-_Final.pdf
2. Insecure data storage
Solution
  Avoid local storage inside the device for sensitive information
  If local storage is “required” encrypt data securely and then store Use the Crypto APIs provided by Apple and Google
  Avoid writing custom crypto code – prone to vulnerability

Put your Nose to the Grindstone! -- Amalgamated Plastic Surgeons and Toolmakers, Ltd.

Working...