1.4.1 announced

[John Clizbe]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sean C. C. wrote:
> After reading the announcement from cross-posted on the enigmail and
> pgp-basics @ yahoo lists, and reading what minimal information is on the
> gnupg.org website (I couldn't find anything on there other than the
> download and a reference to a seemingly nonexistent NEWS file.) I
> noticed that it speaks very little about upgrading. Actually this is the
> only information I could find:
> 
>>>Upgrade Information
>>>===================
>>>
>>>If you are upgrading from a version prior to 1.0.7, you should run the
>>>script tools/convert-from-106 once.  Please note also that due to a
>>>bug in versions prior to 1.0.6 it may not be possible to downgrade to
>>>such versions unless you apply the patch
>>>http://www.gnupg.org/developer/gpg-woody-fix.txt .
>>>
>>>If you have any problems, please see the FAQ and the mailing list
>>>archive at http://lists.gnupg.org.  Please direct questions to the
>>>gnupg-users at gnupg.org mailing list.
> 
> Are there any concerns with upgrading from gnupg 1.4.0a on win32 (WinXP
> Pro)?

NEWS file: http://lists.gnupg.org/pipermail/gnupg-users/2005-March/025131.html

Melissa Reese started a nice upgrade thread over on PGP-Basics.  Perhaps
you could check that.

Your upgrade concerns will mainly be dependent upon how you first setup
GnuPG. If you followed the old C:\GnuPG way you'll have more to change
than if you followed the page at http://enigmail.mozdev.org/gpgconf.html.
(Points go to Werner - his program location is /more correct/ than ours.)
We agree on the keyring location, is all that should need to be changed in
your PATH.

FWIW the only change I had to make after using the installer was to add
the characters "Gnu/" to my PATH environment variable. Of course, YMMV.

If you use other programs such as GPGshell, WinPT, or GPGrelay, they make
use of non-GnuPG registry entries such as OptFile and gpgProgram - You
will have to fix these yourself.

BTW, I had to change some of my build scripts to reference \Gnu\GnuPG
instead of just \GnuPG under %ProgramFiles%, but that will only affect
folks who build the code for themselves.

We'll be rewriting the gpgconf page at the Enigmail site in the next few
days to reflect the 1.4.1 installer.

- --
John P. Clizbe                      Inet:   John (a) Mozilla-Enigmail.org
You can't spell fiasco without SCO. PGP/GPG KeyID: 0x608D2A10
"what's the key to success?"        / "two words: good decisions."
"what's the key to good decisions?" /  "one word: experience."
"how do i get experience?"          / "two words: bad decisions."

"Just how do the residents of Haiku, Hawai'i hold conversations?"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: When cryptography is outlawed, b25seSBvdXRsYXdzIHdpbGwgdXNlIG
Comment: Be part of the £33t ECHELON -- Use Strong Encryption.
Comment: It's YOUR right - for the time being.
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFCOHRbHQSsSmCNKhARAi03AKC/pURzrGcWazESCaZGLAojwXIGLACeOUjt
7OYqv1JY090YYw4b4gChdsE=
=uFoJ
-----END PGP SIGNATURE-----