News for hackers. Stuff that matters.
Re:BoringSSL by swsieber on Tuesday October 20, 2015 @02:19PM (#10420808)
I feel like this would actually be a good project for a rust re-write. I like to think of rust as c or c++ except with memory "static type-checking". That seems like a huge incentive.
Re:BoringSSL by dyladan on Tuesday October 20, 2015 @04:31PM (#10421617)
It's difficult/impossible to write constant time functions in rust in it's current state afaik.
Re:BoringSSL by viraptor on Tuesday October 20, 2015 @09:12PM (#10422965)
Could you link something relevant? I find it hard to believe - seems you could do it the same way every other language does. For example OR all the bytes XORed between two arrays, then compare to 0.

Maidsafe seems to be implementing it somehow for example: http://maidsafe.net/sodiumoxide/master/maidsafe_sodiumoxide/... (see comments about PartialEq)

Re:BoringSSL by swsieber on Tuesday October 20, 2015 @07:08PM (#10422488)
I did not realize that; looking things up I can verify your claim. There is an RFC out there for the ability to write constant time functions. That would be great and I hope it makes it in. Thanks for informing me.
Re:BoringSSL by arielby on Tuesday October 20, 2015 @05:41PM (#10422006)
Not more difficult than C - you write the crypto functions in asm. You could use a C compiler to handle the ABI but the code isn't really C code.
Re:BoringSSL by MichaelGG on Tuesday October 20, 2015 @05:53PM (#10422074)
How much code needs to be constant time? Compared to all the management code and parsing and so on?