Hello, when I help Windows users create keys then my script converts the Linux version of gpg.conf (after some editing) to the Windows line endings. This works.
But if I edit the file with the Windows editor (unfortunately I have forgotten the Windows version) then gpg crashes with an error message like "error in gpg.conf:1". I have experienced that several times in the past already. Unfortunately I both don't have Windows at home and have forgotten to make a copy of the damaged file so that I cannot have a look at it. A wild guess is that the editor adds a UTF-8 BOM at the beginning of the file (but that wouldn't affect XP, would it?). Two concerns: 1) Does anyone know what the problem is and/or whether I can avoid it by using another program which is part of Windows (or widely used)? 2) Would it make sense to make gpg work with such config files...? 8-) Hauke -- Crypto für alle: http://www.openpgp-schulungen.de/fuer/unterstuetzer/ http://userbase.kde.org/Concepts/OpenPGP_Help_Spread OpenPGP: 7D82 FB9F D25A 2CE4 5241 6C37 BF4B 8EEF 1A57 1DF5
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users