headers
fidelis okone | 1 Feb 2013 18:48
Picon
Favicon

(unknown)

http://stavilarul.uv.ro/erwdvb.html





























------------------------
fidelis okone
-------------------


_______________________________________________
Gnupg-doc mailing list
Gnupg-doc <at> gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-doc
Permalink | Reply | 0 comments |
headers
John A. Wallace | 17 Oct 2011 20:57
Picon

gnupg on USB drive

I have looked at the instructions here http://lists.gnupg.org/pipermail/gnupg-users/2008-March/032787.html for installing GnuPG on a USB drive, and I have followed the instructions pretty closely like so:

 

“if you … need to work from a public computer, and a usb, here are some guidelines:

 

[1] generate a new gnupg key, with a comment, 'usb key',

and keep this in a separate keyring (not the the keyring with your

'real' secret keys)

 

if you have any concern that this becomes compromised,

you can revoke it, without compromising your 'real' keys

 

[2] keep the keyrings and the entire gnupg program in a truecrypt

container on the usb. This has two advantages:

(a) it protects your keyrings

(b) it allows you to pick a drive letter that will stay the same

regardless of the hardware differences of the various public

computers (i.e., you can mount the truecrypt container as drive Z,

and have all the entries in your gpg.conf refer to z:\gnupg,

and never have to change it). truecrypt can be run in traveller mode from a usb,

without having it installed on the host computer

 

[3]copy the entire gnupg directory from your home computer,

into the truecrypt container

 

[4] put these lines into your gpg.conf file:

no-default-keyring

keyring z:\gnupg\pubring.gpg

secret-keyring z:\gnupg\secring.gpg

(use your 'new' keyrings with the special 'usb key')

 

[5] open notepad and types these lines:

command com

z:

cd gnupg

 

save this as gusb.bat in your truecrypt container.

whenever you want to run gnupg from the usb,

(and have already mounted the truecrypt container as drive z:)

double-clicking on gusb.bat

opens a dos command-line window

 

check it by typing gpg -h

if the gnupg version and guide appears, then you're ready”

----------------------------------

 

First I tried following these instructions exactly, but it would not work,

though not for reasons related to gpg itself. I am running WinXP Pro and normally

I use gpg 2.0.x.  However, for this project, I downloaded and used gpg 1.4.11

on the USB drive, and I also used the latest version of truecrypt 7.1.

 

I installed gpg on the usb here U:\gnupg, and into it I also copied the contents of

my pre-existing “%AppData%\gnupg” folder, which contained my keyrings and gpg.conf, etc.

  I cleaned it up a bit and changed the references in gpg.conf from c:\path to u:\gnupg,

like so:

 

###+++--- GPGConf ---+++###

utf8-strings

auto-key-locate local

verbose

###+++--- GPGConf ---+++### date and time data

# GPGConf edited this configuration file.

# It will disable options before this marked block, but it will

# never change anything below these lines.

no-default-keyring

homedir U:\gnupg

keyring U:\gnupg\pubring.gpg

secret-keyring U:\gnupg\secring.gpg

#list-options show-keyring

verify-options show-uid-validity

logger-file U:\gnupg\gnupg.log

keyserver hkp://keys.gnupg.net

load-extension U:\gnupg\idea.dll

ask-cert-level

------------------------------------

 

As for the aforementioned batch file qusb.bat, it was necessary to change

it because it would not complete as it stands (I had installed it in U:\).

What I mean is that when I clicked on the batch file, it would open a

command shell window and begin issuing the batch of commands.  Since the

first command was “command.com”, it just opened another new command shell

window and stayed there at the new command prompt in the current root directory:

 

U:\

 

I simply eliminated this command from the batch file and reran it; then

It worked as expected, opening a command shell and cd-ing to U:\gnupg.

 

At this point I entered “gpg –h” at the prompt.  It displayed the correct

Version gpg 1.4.11, but it failed to recognize homedir as U:\gnupg as I had

put in the file u:\gpg.conf.  Then I noticed in the manual that this command

would be recognized only from the command line; so I entered this at

the command prompt (from u:\gnupg):

 

gpg --homedir u:\gnupg

 

But after hitting <enter>, the program just hangs and fails to return

to the command prompt.  Consequently, I cannot seem to make it change

the homedir from the normal location on “%Appdata%\gnupg”

to the location U:\gnupg, and I cannot, therefore, “force” it to use

the keyrings on my USB.  Any ideas would be welcome.

 

 

John A. Wallace

 

_______________________________________________
Gnupg-doc mailing list
Gnupg-doc <at> gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-doc
Permalink | Reply | 4 comments |
headers
mezzanine | 31 Mar 2011 22:30

A diff file for generating a possible revised GNU Privacy Handbook

Attached to this message is a gzipped diff file that should be usable
for generating a revised version of the GNU Privacy Handbook. The
diff file should be applied to a downloaded copy of the current
English HTML version of the GNU Privacy Handbook
<http://www.gnupg.org/gph/en/manual.html> in order to produce the
revised version.

Notes: The existing GNU Privacy Handbook was licensed under the GNU
Free Documentation License (GFDL), and the GFDL specifies certain
conditions with regard to distributing modified versions of the
handbook, including the use of a different title for the work. For
now, the revised version of the handbook has the same title as before.
In addition, in the "Using trust to validate keys" section, the
revised version includes the statement "In such a case, the path of
signed keys from K back to your own key is subject to the same length
limit of five steps that was previously mentioned." I am not totally
sure as to the accuracy of this statement, but I am assuming that it
is probably correct. Lastly, the e-mail address for Mike Ashley that
is given in the handbook may no longer be valid.

--Richard
Attachment (gpg-handbook-rev-march-25-2011.diff.gz): application/x-gzip, 3452 bytes
_______________________________________________
Gnupg-doc mailing list
Gnupg-doc <at> gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-doc
Permalink | Reply | 0 comments |
headers
mezzanine | 10 Dec 2010 13:14

Revisions to the GNU Privacy Handbook

The current issue of the GNU Privacy Handbook appears to date back to the year 1999. Out of interest, I
obtained a copy of the handbook and edited it with the hope of making it somewhat more up-to-date. In
particular, the revisions include such things as generating RSA keys (from what one remembers, in 1999
RSA encryption was subject to licensing restrictions that probably prevented it from being widely
implemented in the GnuPG software), 2048-bit keys for public-key encryption (as opposed to 1024-bit
keys), the deprecation of the SHA-1 hash algorithm, graphical front-ends for the GnuPG software, and the
difference between fully valid and marginally valid keys (I am still not sure as to whether the path length
limit of five steps applies in all cases.) Some URLs have also been updated.

--Richard

The diff output below may be useful for generating the revised version of the handbook from the current
version (i.e. the version at the http://www.gnupg.org/gph/en/manual.html URL.)

33c33,34
< ></P
---
> ><BR />
> Last modified on December 10, 2010 by Richard</P
453,456c454,456
< gpg (GnuPG) 0.9.4; Copyright (C) 1999 Free Software Foundation, Inc.
< This program comes with ABSOLUTELY NO WARRANTY.
< This is free software, and you are welcome to redistribute it
< under certain conditions. See the file COPYING for details.
---
> gpg (GnuPG) 1.4.9; Copyright (C) 2008 Free Software Foundation, Inc.
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
459c459
<    (1) DSA and ElGamal (default)
---
>    (1) DSA and Elgamal (default)
461c461
<    (4) ElGamal (sign and encrypt)
---
>    (5) RSA (sign only)
473c473,477
< Option 4<A
---
> Option 5 creates a single RSA 
> keypair usable only for making signatures.
> In all cases it is possible to later add additional subkeys for encryption
> and signing.
> <B>Note:</B> Although it is not the default choice, the recommended choice for most circumstances is to
create a signature-only RSA keypair via Option 5 and to afterwards add an RSA subordinate keypair for encryption<A
477,481c481
< > creates a single ElGamal 
< keypair usable for both making signatures and performing encryption.
< In all cases it is possible to later add additional subkeys for encryption
< and signing.
< For most users the default option is fine.</P
---
> >.</P
485c485
< key may be of any size.
---
> key or an RSA key may be of any size.
493,497c493,494
< >About to generate a new ELG-E keypair.
<               minimum keysize is  768 bits
<               default keysize is 1024 bits
<     highest suggested keysize is 2048 bits
< What keysize do you want? (1024)</PRE
---
> >RSA keys may be between 1024 and 4096 bits long.
> What keysize do you want? (2048)</PRE
709c706
< >[2]</A
---
> >[3]</A
1226c1223
< HREF="http://www.counterpane.com/schneier.html"
---
> HREF="http://www.schneier.com/"
1232c1229
< HREF="http://www.counterpane.com/applied.html"
---
> HREF="http://www.schneier.com/book-applied.html"
1258c1255,1256
< Modern examples of symmetric ciphers include 3DES, Blowfish, and IDEA.</P
---
> Modern examples of symmetric ciphers include 3DES, Blowfish, Rijndael,
> and IDEA.</P
1306c1304
< Blowfish, and IDEA
---
> Blowfish, Rijndael, and IDEA
1310c1308,1310
< possible keys.
---
> possible keys. 2<SUP
> >128</SUP
> > is 340,282,366,920,938,463,463,374,607,431,768,211,456 keys.
1313c1313,1314
< the universe to find the key.</P
---
> the universe to find the key. (Some symmetric ciphers, such as Rijndael,
> can also use keys that are greater in size than 128 bits.)</P
1413c1414
< technology public keys with 1024 bits are recommended for most purposes.</P
---
> technology public keys with 2048 bits are recommended for most purposes.</P
1516c1517
< >[3]</A
---
> >[4]</A
1570,1571c1571
< algorithm that works as just described.
< DSA is the primary signing algorithm used in GnuPG.</P
---
> algorithm that works as just described.</P
1686a1687,1689
> >R</TT>
> for an RSA key,  <TT
> CLASS="LITERAL"
1850,1851c1853,1854
< The subkey may be a DSA signing key, and encrypt-only ElGamal
< key, or a sign-and-encrypt ElGamal key.
---
> The subkey may be a DSA signing key, an encrypt-only ElGamal
> key, a sign-only RSA key, or an encrypt-only RSA key.
2305c2308
< >[4]</A
---
> >[5]</A
2337c2340
< Formerly, a key was considered valid only if you signed it personally.
---
> Formerly, a key was considered fully valid only if you signed it personally.
2341c2344
< > is considered valid
---
> > is considered fully valid
2350c2353
< >it is signed by enough valid keys, meaning
---
> >it is signed by enough fully valid keys, meaning
2365c2368
< >it has been signed by three marginally trusted keys; and</P
---
> >it has been signed by at least three marginally trusted keys; and</P
2380,2381c2383,2393
< 
< The path length, number of marginally trusted keys required, and number
---
> A key <I
> CLASS="EMPHASIS"
> >K</I
> > is marginally valid if it has been signed by at least one
>  but less than three fully valid keys that are marginally trusted. In such a case, the path of signed keys
from <I
> CLASS="EMPHASIS"
> >K</I
> > back to your own key is subject to the same length limit of five steps that was previously mentioned. A
> key with only marginal validity, even if fully trusted, does not count as
> a valid key for the purpose of signing other keys.</P>
> <P>The path length, number of marginally trusted keys required, and number
2457c2469
< SRC="signatures.jpg"
---
> SRC="signatures.jpg"
2751c2763
< Finally, as of 1999, laws regarding digital encryption, and in particular
---
> Finally, as of 2010, laws regarding digital encryption, and in particular
2753c2765
< is currently being debated by many national governments.</P
---
> are currently being debated by many national governments.</P
2833c2845,2850
< key will be a DSA key, and the subkeys will be ElGamal keys.</P
---
> key will be a DSA key, and the subkeys will be ElGamal keys. Though it is not the default
> option, an RSA master key is recommended as a more secure alternative to a DSA key<A
> NAME="AEN35"
> HREF="#FTN.AEN35"
> >[2]</A
> >.</P
2840c2857
< >ElGamal keys, on the other hand, may be of any size.
---
> >ElGamal keys and RSA keys, on the other hand, may be of any size.
2856c2873
< 1024 bits is thus the recommended key size.
---
> 2048 bits is thus the recommended key size.
3132c3149
< >[5]</A
---
> >[6]</A
3182c3199
< HREF="http://www.herrons.com/kb2nsx/keysign.html"
---
> HREF="http://w4kwh.org/keysigning-party-guide/"
3212c3229
< HREF="http://cwis.kub.nl/~frw/people/koops/bertjaap.htm"
---
> HREF="http://rechten.uvt.nl/koops/"
3218c3235
< HREF="http://cwis.kub.nl/~frw/people/koops/lawsurvy.htm"
---
> HREF="http://rechten.uvt.nl/koops/cryptolaw/"
3250c3267
< HREF="http://www.cs.cmu.edu/~alma"
---
> HREF="http://www.gaudior.net/alma/"
3366c3383,3384
< ></P
---
> ></P>
> <P>If you are interested in graphical front-ends for GnuPG, the MacGPG and GPG4Win projects may be of
interest. The home page for the MacGPG project is located at <A
HREF="http://macgpg.sourceforge.net">http://macgpg.sourceforge.net</A> on the Web and the
homepage for the GPG4Win project is located at <A HREF="http://gpg4win.org">http://gpg4win.org</A>
on the Web.</P
3912c3930
< ><A
---
> >[<A
3915,3916c3933,3937
< >[1]</A
< ></TD
---
> >1</A>,<A
> NAME="FTN.AEN35"
> HREF="#AEN35"
> >2</A
> >]</TD
3922,3923c3943
< >Option 3 is to generate an ElGamal keypair that is
< not usable for making signatures.</P
---
> >The DSA algorithm may use the SHA-1 hash function. Due to cryptographic weaknesses that have been found
in SHA-1, RSA keys are a recommended alternative to DSA keys. It is also recommended that GnuPG be
configured to prefer the SHA-256 hash function over SHA-1. For more information about this issue, please
see the <A HREF="http://www.debian-administration.org/users/dkg/weblog/48">HOWTO prep for
migration off of SHA-1 in OpenPGP</A> &LT;<A
HREF="http://www.debian-administration.org/users/dkg/weblog/48">http://www.debian-administration.org/users/dkg/weblog/48</A>&GT;
weblog entry at <A HREF="http://www.debian-administration.org">Debian Administration</A>.</P
3934c3954
< >[2]</A
---
> >[3]</A
3954c3974
< >[3]</A
---
> >[4]</A
3974c3994
< >[4]</A
---
> >[5]</A
4004c4024
< >[5]</A
---
> >[6]</A
4019c4039
< >
\ No newline at end of file
---
> >
Permalink | Reply | 1 comment |
headers
smu johnson | 14 Aug 2010 01:48
Picon
Gravatar

Request for better instructions on verifying IDEA source signatures

Hi,

I've been experimenting with the IDEA cipher 3rd party plugin files, and I keep reading about how I should verify their signatures.

Unfortunately, the help provided by the GnuPG page for that is useless.  Sure, I get the .sig files, but nowhere, not even on the FTP site itself can I find the public keys to verify the signature.

I started surfing around the GnuPG pages and read that I could find a communal verifying key in the GnuPG\doc directory, but I don't see anything in my Mingw32 installation.  And the key provided in armored ascii format does not match the signature.  Great!

My argument:  I think this is bad for getting people used to doing things right, as actually doing the safe thing has become a wild-goose chase for me.  This by no-means encourages anyone to follow proper safety protocol if the suggestion to verify the IDEA code is impossible or extremely difficult, in this instance.

Thank you for reading.


--
smu johnson <smujohnson <at> gmail.com>

_______________________________________________
Gnupg-doc mailing list
Gnupg-doc <at> gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-doc
Permalink | Reply | 0 comments |
headers
Mueen Nawaz | 29 Dec 2007 19:59

Privacy Handbook down

Hi,

	The GnuPG Privacy Handbook is giving me a 404. I've tried a 
number of mirrors as well, along with a number of languages. None 
exists. 

	Just in case you didn't know. 

	I've found the handbook to be a useful introduction to the whole 
topic of public key cryptography, and was hoping to introduce some 
people to it - hence my searching for the link... 

--

-- 
The first piece of luggage out of the chute doesn't belong to anyone, ever.

                    /\  /\               /\  /
                   /  \/  \ u e e n     /  \/  a w a z
                       >>>>>>mueen <at> nawaz.org<<<<<<
                                   anl
Permalink | Reply | 0 comments |
headers
Adrian von Bidder | 5 Oct 2006 10:56
X-Face
Picon

gnupg subkeys HOWTO: looking for a kind soul

Yodel!

A long long time ago, I wrote the GnuPG Subkeys mini-HOWTO at 
<http://fortytwo.ch/gpg/subkeys>.  I have received a lot of positive 
feedback over the time, and the page still gets quite a few hits.  But over 
the last few years, I've not kept up with gnupg developments (though I'm 
still a regular user), and especially I have no idea about compatibility 
issues between various versions of GnuPG and possibly other OpenPGP 
implementations.

So - anybody wants to officially take over maintenance of this mini-HOWTO?  
Access to my host for publication can be arranged if necessary, but I'd 
prefer if the document moved, and I'd just place a redirect to the new 
location.

Please cc: me on replies.

Thank you & all the best
Adrian von Bidder

--

-- 
Maintenance-free: When it breaks, it can't be fixed...

_______________________________________________
Gnupg-users mailing list
Gnupg-users <at> gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Permalink | Reply | 0 comments |
headers
khalid Chapra | 7 Nov 2005 08:35
Picon
Favicon

Problem How to Use THe Source Code of GNUPG

Hi,

I am the new user of GNUPG. I have downloaded the
source code of GNUPG but can't able to use it. Plz
help me and also plz tell me that from where i can
download the documentation of source code

Khalid

	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com
Permalink | Reply | 1 comment |
headers
deans | 7 Sep 2005 19:00

gpg-mini-howto-japanese

Hi, 

I'am Dan Lu <at> Japan/Tokyo.
This is a GPG-mini-howto in Japanese,

Maybe somebody will need it.
But including only files written in html/euc-jp.

The SHA-1 hash for the archive(text only):
SHA1 (gnupg-mini-howto-j.tar.bz2) = 609090c553c927bd2d5460bca84f86b12dd78180
or you can access from web > http://www.isbsd.com/gnupg/

--

-- 
Regards,
Dan Lu
<- deans <at> isbsd.com ->
Attachment (gnupg-mini-howto-j.tar.bz2): application/octet-stream, 19 KiB
_______________________________________________
Gnupg-doc mailing list
Gnupg-doc <at> gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-doc
Permalink | Reply | 0 comments |
headers
Tang Hui | 19 Apr 2005 03:48

how to submit translation

hi all,
    I've made a chinese version of GNU Privacy Handbook. How can I submit it?
--

-- 
    ---        |   +---+
----------    |||  | + |
|    |        |||  +-+-+
|  --+--+    -----  +
| ---+--+--   | |  +-+--
|  --+--+     | |  --+--
|  +----+     | |    |
|  +----+     | |/   |

_______________________________________________
Gnupg-doc mailing list
Gnupg-doc <at> gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-doc
Permalink | Reply | 1 comment |
headers
Herbert Straub | 20 Jul 2004 10:09
Picon
Favicon

The GNU Privacy Handbook - possible error in the key integraty section example

Hallo,

the German translation of this handbook does'nt contain equal parts in the
section: 3. Key Management / Key-Integrity. Werner Koch answer in the gnupg-users list, that the german
examples are using own keys. Therefore the explanation text of the example contains the wrong key id in the
german translation. I suggest an update of the key id.  Details:

The example in the english version:

chloe% gpg --edit-key chloe
Secret key is available.

pub  1024D/26B6AAE1  created: 1999-06-15 expires: never      trust: -/u
sub  2048g/0CF8CB7A  created: 1999-06-15 expires: never
sub  1792G/08224617  created: 1999-06-15 expires: 2002-06-14
sub   960D/B1F423E7  created: 1999-06-15 expires: 2002-06-14
(1)  Chloe (Jester) <chloe <at> cyb.org>
(2)  Chloe (Plebian) <chloe <at> tel.net>

Command> check
uid  Chloe (Jester) <chloe <at> cyb.org>
sig!           26B6AAE1 1999-06-15         [self-signature]
uid  Chloe (Plebian) <chloe <at> tel.net>
sig!           26B6AAE1 1999-06-15         [self-signature]

As expected, the signing key for each signature is the master signing key with
key ID 0x26B6AAE1.

And now the same section in the german version:

chloe$  gpg --edit-key chloe
geheimer Schlüssel ist vorhanden.

pub  1024D/1B087D04  created: 2000-06-07 expires: never      trust: -/u
sub  2048g/6A3E902A  created: 2000-06-07 expires: never    
sub  1792G/7D5D4DAE  created: 2000-06-07 expires: 2002-06-07
sub   960D/C0A27DBE  created: 2000-06-07 expires: 2002-06-07
(1)  Chloe (Journalistin) <chloe <at> cyb.org>
(2)  Chloe (Freie Autorin) <chloe <at> tel.net>

Befehl> check
uid  Chloe (Journalistin) <chloe <at> cyb.org>
sig!       1B087D04 2000-06-07   [Eigenbeglaubigung]
uid  Chloe (Freie Autorin) <chloe <at> tel.net>
sig!       1B087D04 2000-06-07   [Eigenbeglaubigung]

Wie erwartet, wird für jede Unterschrift der primäre Schlüssel mit der
Schlüssel-ID 0x26B6AAE1 genommen.

Look at the Key 0x26B6AAE1. The german version does'nt have it.  I think, it should be 0x1B087D04.

2. The header specify the  <gnupg-doc.de <at> gnupg.org> mailinglist, but Werner said, that this list was
closed, due to inactivity. I suggest to update this to <gnupg-doc <at> gnupg.org>

Below a patch file (diff to the current cvs version of the gph)

Thanks
Herbert Straub

Index: keymanag.sgml
===================================================================
RCS file: /cvs/gph/gph/de/keymanag.sgml,v
retrieving revision 1.3
diff -u -r1.3 keymanag.sgml
--- keymanag.sgml       28 Aug 2000 21:54:40 -0000      1.3
+++ keymanag.sgml       20 Jul 2004 08:02:25 -0000
 <at>  <at>  -217,7 +217,7  <at>  <at> 
 </screen>

 Wie erwartet, wird für jede Unterschrift der primäre Schlüssel mit der
-Schlüssel-ID <literal>0x26B6AAE1</literal> genommen. Die Eigenbeglaubigungen auf
+Schlüssel-ID <literal>0x1B087D04</literal> genommen. Die Eigenbeglaubigungen auf
 den Subkeys sind in dem öffentlichen Schlüssel enthalten, doch
 werden sie vom Schlüsseleditor nicht gezeigt.
 </para>
Index: manual.sgml
===================================================================
RCS file: /cvs/gph/gph/de/manual.sgml,v
retrieving revision 1.14
diff -u -r1.14 manual.sgml
--- manual.sgml 6 Oct 2000 15:57:36 -0000       1.14
+++ manual.sgml 20 Jul 2004 08:02:26 -0000
 <at>  <at>  -93,7 +93,7  <at>  <at> 
 <para>
 Richten Sie bitte Ihre Fragen, Fehlermeldungen oder Anregungen,
 sofern sie dieses Handbuch betreffen, an die Mailingliste
-<email>gnupg-doc.de <at> gnupg.org</email>.
+<email>gnupg-doc <at> gnupg.org</email>.
 Mike Ashley ist der Autor des orginalen englischen Version dieses
 Handbuchs, Beiträge lieferten auch Matthew Copeland,
 Joergen Grahn und David Wheeler.
Permalink | Reply | 1 comment |

Gmane