kingemer
Re:Pins now optional in Signal v3.13.1
on Wednesday July 15, 2020 @11:19PM (#23855379)
Well, it is encrypted with a pin. Unless you make a long pin or switch to optional alphanumeric, the contact list is just protected by SGX and a short pin.
The SGX works like the iPhone auto-wipe. But it is in an online service with lots of juicy data in one place, so the target is bigger. A vulnerability could leak your contact list.
Re:Hardcoded secrets, unverified tokens, and other common JWT mistakes
on Sunday June 28, 2020 @12:30AM (#23666746)
Just for the specific implementation. The reference implementation is the PHP version here:
https://github.com/paragonie/paseto
And has had a lot more attention.
Re:Mercurial’s journey to and reflections on Python 3
on Monday January 13, 2020 @02:11PM (#22037533)
Considering how much opposition there is in moving to python3, has there been any significant effort in the community keeping python2 alive?
Re:Mercurial’s journey to and reflections on Python 3
on Monday January 13, 2020 @02:08PM (#22037494)
It sounds like the cost was non trivial for them, partially because they weren’t allowed to break things for python2, or even disrupt the efforts of those using it.
The language wasn’t ready for the transition, but it feels like it may have been even harder on them because of the requirements imposed on their project.