News for hackers. Stuff that matters.
Re:CryptoCat iOS Application Penetration Test [pdf] by venomsnake on Wednesday April 02, 2014 @05:27PM (#7519173)
There is a "many ways to skin a cat" joke here somewhere. It is actually terrible - the hmac timing attack requires around 3 minutes of google searching to avoid and is basic public domain knowledge. The other are much worse.
Re:CryptoCat iOS Application Penetration Test [pdf] by sliverstorm on Wednesday April 02, 2014 @05:35PM (#7519225)
I wish I knew how to find my way into security as a hobby. Such a fun topic.
Re:CryptoCat iOS Application Penetration Test [pdf] by tptacek on Wednesday April 02, 2014 @06:33PM (#7519527)
Why find your way in as a hobby? Are you a professional developer now? Do you like low-level code? Are you OK with jumping directly into the deep end of the pool and maybe drowning a little bit? Why not reach out and talk to us about working on a professional security team?

We have gotten very, very good at taking low-level devs and turning them into terrifying killing machines, and if you don't mind having all your flesh removed and your skeletal musculature replaced by pistons and servomotors, we'd be happy to do the same to you.

http://matasano.com/careers

Re:CryptoCat iOS Application Penetration Test [pdf] by ph0rque on Wednesday April 02, 2014 @08:46PM (#7520112)
...if you don't mind having all your flesh removed and your skeletal musculature replaced by pistons and servomotors...

Ah, but have you pen-tested the pistons and servomotors to make sure they're secure against attacks?

Re:CryptoCat iOS Application Penetration Test [pdf] by tptacek on Wednesday April 02, 2014 @08:47PM (#7520116)
We only care about their ability to inflict harm, not their ability to withstand it. :)
Re:CryptoCat iOS Application Penetration Test [pdf] by Tomte on Thursday April 03, 2014 @01:52AM (#7521189)
I'd be more interested in the safety of those electromechanical components.

Have you developed them under any applicable safety standards?

Otherwise I'd prefer to stay a purely organic organism.

Re:CryptoCat iOS Application Penetration Test [pdf] by lrigknat on Wednesday April 02, 2014 @06:56PM (#7519647)
And try their crypto challenges :)
Re:CryptoCat iOS Application Penetration Test [pdf] by sliverstorm on Wednesday April 02, 2014 @06:34PM (#7519536)
Coding is a purely ancillary function to my day job; I am not a developer.
Re:CryptoCat iOS Application Penetration Test [pdf] by tptacek on Wednesday April 02, 2014 @06:35PM (#7519539)
"I hate coding" would be a problem for us, but "I ship software every day", not so much.
Re:CryptoCat iOS Application Penetration Test [pdf] by nialo on Wednesday April 02, 2014 @09:40PM (#7520357)
How about "I really enjoyed microcorruption and the crypto challenges, but am mostly working as a mechanical engineer"?
Re:CryptoCat iOS Application Penetration Test [pdf] by tptacek on Wednesday April 02, 2014 @09:50PM (#7520403)
"Really enjoying Microcorruption and the crypto challenges" puts people pretty high up on my priority list.
Re:CryptoCat iOS Application Penetration Test [pdf] by oliwary on Wednesday April 02, 2014 @05:44PM (#7519288)
I am in the same position. Stanford Online started a Coursera course on cryptography yesterday, might be interesting for you.

https://www.coursera.org/course/crypto

Re:CryptoCat iOS Application Penetration Test [pdf] by scott_s on Wednesday April 02, 2014 @05:54PM (#7519341)
Long-time HN member tptacek's company has a challenge set that many praise highly: http://www.matasano.com/articles/crypto-challenges/
Re:CryptoCat iOS Application Penetration Test [pdf] by schoen on Wednesday April 02, 2014 @06:40PM (#7519562)
Are the Matasano crypto challenges currently stuck in some way, like with a grading backlog? I signed up some months ago, sent my first set of answers just after the new year, and have never heard back about the second challenge set.
Re:CryptoCat iOS Application Penetration Test [pdf] by tptacek on Wednesday April 02, 2014 @07:16PM (#7519733)
We are way. way. way. backlogged.

If anyone has any idea on how to help a hapless team of security researchers manage many thousands of people looking to get through the crypto challenges, we'd be t-h-r-i-l-l-e-d.

We were able to keep up last summer, but then Microcorruption happened, we got into a hole, and we're only slowly digging ourselves out of it.

Alex, Sean, and I are turning the challenges into a book, which we're going to release "choose-your-price" with all funds directly going to a charity (I like Watsi, but who knows); that book will also include Set 8, which is all ECC.

I'm hoping we'll be done with that by August.

Re:CryptoCat iOS Application Penetration Test [pdf] by Tomte on Thursday April 03, 2014 @01:48AM (#7521175)
I know I haven't submitted in forever (and may have been removed of the set of active participants), but I got your New Year's bankruptcy mail, but never the "bonus set".

Is that still part of the backlog?

Re:CryptoCat iOS Application Penetration Test [pdf] by rcsorensen on Wednesday April 02, 2014 @07:55PM (#7519905)
Have you considered taking people who have passed challenges (and are excited about them) on as volunteer assistants for the challenges?
Re:CryptoCat iOS Application Penetration Test [pdf] by tptacek on Wednesday April 02, 2014 @07:58PM (#7519923)
If anyone has ideas on how we could do that, I'm all ears. We'd have to mitigate the privacy issues somehow, because not everyone has given us permission to reveal that they're working through the challenges, and passing submissions to people outside the firm would be that.
Re:CryptoCat iOS Application Penetration Test [pdf] by orthecreedence on Wednesday April 02, 2014 @08:29PM (#7520037)
Not sure what you guys are using to track all of it, but maybe a simple web app would help you out. For instance, an email address would be attached to a "level" (so you guys could input your previous members and attach what level they're on so if they sign up with that same email it'd be aligned).

People could sign up and post their solutions, and others would be able to validate entries of levels below them (so someone on level 3 could validate a level 2 submission). Or hell, the webapp may even be able to validate some of it (obviously not entries where you paste code, but things like "Decrypt !4321hj4123$@!#$" could be automated).

This way, you could submit solutions via your login (attached to your email) and people validating the entries wouldn't be able to see the email address, just the answers, and could comment on the submission.

Sorry, this was a bit stream of consciousness. If this was particularly barebones, you might be able to slam it out in not too much time. If you don't mind PHP or Common Lisp in the backend, I might even be able to help out a bit.

Re:CryptoCat iOS Application Penetration Test [pdf] by tptacek on Wednesday April 02, 2014 @08:46PM (#7520110)
We actually do have a web application we use to track the challenges (the mail is all done through Mailgun).

Two things complicate managing the challenges:

* We have to actually read the code people send us (if you get things wrong, there's a pretty good chance we'll catch it). We try hard not to move people forward a level until they've gotten the previous challenges right.

* We don't dictate any particular format for submissions. Some people paste code into their email messages; some people attach lots of little files; some people attach archives. Some languages let you stick all that code in 1 file; others, like Java and C#, have complicated directory hierarchies.

Re:CryptoCat iOS Application Penetration Test [pdf] by lis on Thursday April 03, 2014 @04:32AM (#7521588)
We have a pretty cool submission system in use at my university, that will spin up a VM, compile and run your code and have a set of validators check if the output is correct. That way people can test their submission and immediately get feedback. You would still have to look into the code to make sure it's really valid, but I guess you could filter out lots of invalid submissions. If you are interested, I can hook you up with one of the developers of that system.