Quote from: Guru on August 11, 2012, 03:07 pmQuote from: LouisCyphre on August 11, 2012, 02:08 pmQuote from: Guru on August 11, 2012, 02:27 amQuote from: Shannon on August 10, 2012, 06:25 pmgpg 2.1 does eccThat'll be nice. I wonder if the 1.5.x version will include it as well -- that would be so damn sweet!There won't be a 1.5 or 1.6. According to Werner 2.1 is the future. That's what I was afraid of. I know that Werner had made noises about the 2.x series eventually becoming the default.... Yep, lurking on gnupg-users confirmed that.Quote from: Guru on August 11, 2012, 03:07 pmWhile the addition of ECC will be very welcome, It will indeed. 2.1 will also see the return of IDEA now that the patent has expired and the availability of Serpent for symmetric encryption.Quote from: Guru on August 11, 2012, 03:07 pmI have to wonder whether 2.1 will break all the current front-ends that so many people rely on.Maybe, it probably depends on each client.Quote from: Guru on August 11, 2012, 03:07 pmI know how to use the command-line, but I find gedit and seahorse _so_ damn convenient, it's not funny. If the GUIs are just calling the command line and piping the output and input in the right ways then it only matters if the options are hanged and I don't believe that's the case. Certainly Enigmail runs the GPG commands in the background and you can check the debug log or console to see what it's actually doing.Quote from: Guru on August 11, 2012, 03:07 pmI find myself wondering how long it's going to take the authors of the various GPG front-ends to revamp their offerings so as to work with 2.1. For example, the authors of Kleopatra hasn't even updated the default RSA key format, and that change was made 3 years ago now! I think it will vary according to each frontend and the methods each uses to perform different functions. I reckon Enigmail will keep working, which means all those Debian versions of it will be fine. Obviously GPA will be updated to play nicely where such updates may be necessary.Quote from: Guru on August 11, 2012, 03:07 pmI have the sick feeling in the pit of my stomach that this is going to be a train wreck.... new key formats, broken front-ends. The problem is, that software tends to persist -- just look at the train-wreck that is Portable PGP 1.0.x. -- the authors either cannot, or worse -- will not -- update their software to conform with current standards. I see things as only getting worse when 2.1 arrives on the scene. I hope to hell I'm wrong, but I don't think I'm gonna be. I'm not sure it will be as bad as you imagine. It might be just enough to leave BCPG in the dustbin of history where it belongs, though. Once that's dealt with we can more effectively kick all those implementations which rely on it (Portable PGP, IGolder, Countermail, etc.) to the kerb.There will be delays between the initial release of GPG 2.1 and other bundles (e.g. GPG4Win, GPGTools, GPG4USB). That's to be expected, though.