Re: Windows editor destroys gpg.conf

2014-01-15 Thread vedaal 

On Wed, Jan 15, 2014 at 2:02 PM, Hauke Laging  wrote:


> 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)?

=

I often switch between Ubuntu and Windows, and have 2 separate gpg.conf. files,
(my keyrings are in a truecrypt container, and in Windows, truecrypt containers 
mount to their own file letter 
(e.g. V:\)
while in Ubuntu it mounts as a numbered directory as part of a dev/ directory,
so the home directory for gnupg has a different address).

Anyway, when using a gpg.conf file in windows that was done in Ubuntu,
Windows sometimes 'decides' that the lines are too long and wrap them, 
thereby creating a new line in gpg.conf that makes no sense.

This can happen if the 'Comment' option  line is too long, or a # commented out 
line is too long.

Another reason that might invalidate a gpg.conf, on windows,  is if there are 
any '/' instead of '\'  .

The actual program in Linux that is used to write the gpg.conf doesn't really 
matter.

Using Notepad to edit it in windows will quickly show if there is a problem.
Notepad is in every edition of windows, and opens files without .txt  
extensions.
(It easily open gpg.conf and saves it a gpg.conf).


vedaal


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Windows editor destroys gpg.conf

2014-01-15 Thread Tristan Santore 

On 15/01/14 13:33, Jerry wrote:

On Wed, 15 Jan 2014 14:02:12 +0100, Hauke Laging stated:


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-)


Personally, I use "PSPad" to edit files from different OSs on a Window's
machine. . It can save in several different
formats and styles. Plus, it is free.


unix2dos and dos2unix are your friends.

Regards,
Tristan

--
Tristan Santore BSc MBCS
TS4523-RIPE
Network and Infrastructure Operations
InterNexusConnect
Mobile +44-78-55069812
tristan.sant...@internexusconnect.net

Former Thawte Notary
(Please note: Thawte has closed its WoT programme down,
and I am therefore no longer able to accredit trust)

For Fedora related issues, please email me at:
tsant...@fedoraproject.org

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Windows editor destroys gpg.conf

2014-01-15 Thread Nomen Nescio 
i do testing

unix line end conf is ok on windows
of course dos line end is ok too

utf8-bom, unicode, unicode-be
file formats all fail


> gpg -K --options utf8-bom-conf.txt
gpg: utf8-bom-conf.txt:1: invalid option

> gpg -K --options unicode-be-conf.txt
gpg: unicode-be-conf.txt:1: invalid option
gpg: unicode-be-conf.txt:2: invalid option
gpg: unicode-be-conf.txt:3: invalid option
...

> gpg -K --options unicode-conf.txt
gpg: unicode-conf.txt:1: invalid option
gpg: unicode-conf.txt:2: invalid option
gpg: unicode-conf.txt:3: invalid option
...




___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Windows editor destroys gpg.conf

2014-01-15 Thread Pete Stephenson 
On Wed, Jan 15, 2014 at 2:02 PM, Hauke Laging
 wrote:
> 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)?

I like using Notepad++ . It understands
Unix and Windows end-of-line conventions and can switch between them
as needed. I've had no problems editing my gpg.conf file with it.

Cheers!
-Pete

-- 
Pete Stephenson

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: Windows editor destroys gpg.conf

2014-01-15 Thread Jerry 
On Wed, 15 Jan 2014 14:02:12 +0100, Hauke Laging stated:

> 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-)

Personally, I use "PSPad" to edit files from different OSs on a Window's
machine. . It can save in several different
formats and styles. Plus, it is free.

-- 
Jerry

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users