-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 6/2/2013 10:06 PM, John Clizbe wrote: > Speaking as one of those people who took part in the discussion > creating that advice...
Speaking as another one of those people who took part in that discussion: although the move to a pure-Javascript implementation has done a lot to minimize this rule, I think John's "the 'same place' rule is pretty much gone" needs a little explanation. The number of different Linux distros, the number of different customized Windows builds of Thunderbird, the number of different customized OS X builds of Thunderbird... if you add up all these variations you'll probably hit triple digits. On top of that, each distro may support several different versions of Thunderbird, and do different optimizations to each. We don't have the resources to test Enigmail against every custom version of Thunderbird, and so we can't make guarantees. Moving to all-Javascript has made it far more likely that Enigmail will work without a problem, but you're still taking chances. As John said, the 'same place' rule is pretty much gone. But make sure to remember the rest of what he said, which was that it's still a strong recommendation. -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJRrCj+AAoJEERqRG+BDbXQDRwH/juoHZeXaLGn2TXrlTl5EO4t ivNTt6HqlWy3PjGKxHSqH+BAWt5b86h10gVJ9c+K3zfZ1YWb1tNeA2ek1vY5RWZZ s9hPHga0hHK8nWEopiYtgc6uwT8+3yvjaWh4iFL4STVaP5tfse2mMxxdQ8SPfj0t HLkqlev0NVghQUdVyQ2SZpgDEYREB1t6zt6C8nAzdTXv6p72De9Mh1nOZGNFltE+ yZzooIMIyAB9R5zz3uJUB2lNpAf9t4PA/kB4BPelr4YBFZuxCAYj9UxQkP0nPa+u KhyEHmx73j+bz99LlBs+4R3FFASZENJ02jJFQh4MUZSVSDV+nYEMxUHRmnxFmS8= =hyQ4 -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
