Re: WinPT
engage wrote: can refresh or add to the public keyring from the CLI with gpg but I can't refresh the keys using the same server from within WinPT. There might be a problem with the code. Please can you check out 0.11.4 (0.10.1 is rather obsolete)? Timo ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: hard-copy backups
On Thu, Jan 05, 2006 at 02:07:17PM -0500, Atom Smasher wrote: > On Thu, 5 Jan 2006, Janusz A. Urbanowicz wrote: > > >from my experience, all keys for long-term, _safe storage_ (and after > >revocation) should be kept with no passphases at all > > > >human memory is very volatile and some day you gonna need to decrypt an > >old email encrypted with the key you revoked in 1993[1], and there's is > >no way you'll remember the old, long time not used, non-trivial > >passphrase > > > and then keep the printout in a very safe place? a very well hidden place? > very safe, well hidden place? > > hehe... the problem then isn't remembering the passphrase, but remembering > where you put the paper ;) At least this knowledge is not case sensitive. And not national-characters-encoding sensitive too. Keep it with other important papers of your life. And not necessarily printouts only, slowly burned CD kept in good conditions, or some solid state memory storage (like a small and cheap pendrive), can last a few years. -- mors ab alto 0x46399138 ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: hard-copy backups
> Keep it with other important papers of your life. And not necessarily > printouts only, slowly burned CD kept in good conditions, or some solid > state memory storage (like a small and cheap pendrive), can last a few > years. Burning a cd at low speeds doesn't neccessarily make it last longer. If you need them to stay in a good condition for a long time, buy gold cds. Like the Delkin archival gold series: http://keetweej.vanheusden.com/redir.php?id=58 Folkert van Heusden -- Try MultiTail! Multiple windows with logfiles, filtered with regular expressions, colored output, etc. etc. www.vanheusden.com/multitail/ -- Get your PGP/GPG key signed at www.biglumber.com! -- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
RE: BZIP2 algorithm
lusfert <[EMAIL PROTECTED]> wrote: >Hello. > >I downloaded GnuPG source and checked its signature (under Windows): >ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.2.tar.bz2 >ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.2.tar.bz2.sig You did that part right. >Then I rebooted into recently installed Debian GNU/Linux 3.1r0a system >and built program from source: > >$ cd /home/[user]/ >$ bunzip2 gnupg-1.4.2.tar.bz2 >$ tar xvf gnupg-1.4.2.tar better: $ bunzip2 gnupg-1.4.2.tar.bz2 | tar -xvf - >$ cd ./gnupg-1.4.2 >$ ./configure Where did the output go? To /dev/null? Since you are not using C Shell (please use bash, sh, of ksh), do it this way: $ ./configure > LOG.config 2> ERR.config Now you can study the results to decide what to do next... I can already tell you right now that you will be building the BZIP library. If you see the following magic line in the LOG.config file: "checking whether to enable the BZIP2 compression algorithm... yes" you will know you are okay. If you don't ... more on that in a moment... >$ make Ditto with output going to other files... $ make > LOG.make 2> ERR.make $ ls -l ERR.* If both of those files are empty, you may be okay. If they are and you are happy with what is in the LOG.* files, then you can proceed... ># make install > >After these steps command "gpg --version" displays the following: > >gpg (GnuPG) 1.4.2 >[...] >Compression: Uncompressed, ZIP, ZLIB First, I am assuming you put the program by default into /usr/local. Do you have /usr/local/bin and /usr/local/sbin first in your PATH? I ALWAYS DO THIS TO MY PATH VARIABLE. That is because I leave the older version of GnuPG (and whatever else) alone since I don't want to get whacked by an update from the OS creators that undoes all that nice work to get things as up to date as possible (especially useful with GnuPG). Download bzip2 and install it in all its glory (which includes not only the executables, but also the header and bzip2 link library files. http://www.bzip.org/ Strange, but it isn't as nicely integrated into ClamAV as it is in GnuPG. I may REALLY need it there in the future once MS Windows is dead and the virus writers move on to Linux and back to where the very first virus was written - TO UNIX! Strange - it seems like they would have provided bzip2 with the libraries and header files by now in most distributions by default. Does anybody know the reason why they are not doing it? Happy bzip2'ing, but I really would advise that if you are going to be sending to MS Windows people to use either gzip or zip as your default compression algorithm. Most Windows compression programs can handle them, but one of the things I do to contain the Trojan files while they are on Windows is to bzip2 them on Linux. When virus writers conceal their nasty worms in bzip2 files, all of this will change. Henry Hertz Hobbit __ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: BZIP2 algorithm isn't supported after compiling gnupg from source code
John Clizbe wrote on 05.01.2006 19:50: > lusfert wrote: >>Thus BZIP2 algorithm isn't supported after compiling GnuPG 1.4.2 from >>source code under Linux. >>How can I enable BZIP2 support using last version of GPG under Linux? > > > What was the output from configure? You should have seen lines like > (near top) > checking whether to enable the BZIP2 compression algorithm... yes > > (near bottom) > checking for bzlib.h... yes > checking for BZ2_bzCompressInit in -lbz2... yes > > './configure 2>&1 | tee configure.log' will save the output from > configure for diagnostic purposes. > OK, I tried again. Here is configure log: http://lusfert.land.ru/files/configure_log It contains these lines: - checking whether to enable the BZIP2 compression algorithm... yes checking for bzlib.h... no - > BZIP2 support won't be built if configure cannot find the bzlib.h include file > and the libbz2 library. You may need to 'help' configure find the bzip2 > library. > configure's --help will tell you: > > --with-bzip2=DIRlook for bzip2 in DIR > But what directory should I write here? > Finally, what version does apt-get install? > 1.4.1 Regards -- My current OpenPGP key ID: 0x500B8987 Key fingerprint: E883 045D 36FB 8CA3 8D69 9C79 9E35 3B56 500B 8987 Encrypted e-mail preferred. signature.asc Description: OpenPGP digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: BZIP2 algorithm isn't supported after compiling gnupg from source code
lusfert wrote: > John Clizbe wrote on 05.01.2006 19:50: > OK, I tried again. Here is configure log: > http://lusfert.land.ru/files/configure_log > > It contains these lines: > - > checking whether to enable the BZIP2 compression algorithm... yes > checking for bzlib.h... no > - > >> BZIP2 support won't be built if configure cannot find the bzlib.h include >> file >> and the libbz2 library. You may need to 'help' configure find the bzip2 >> library. >> configure's --help will tell you: >> >> --with-bzip2=DIRlook for bzip2 in DIR >> > But what directory should I write here? find / -name bzlib.h -print If you don't have it you can probably get it from the bzip2 source. If the test for libbz2 after this fails, you'll likely need to build your own BZIP2. Come on, Debianistas. I know there are Debian users out there who can answer all of this. -- John P. Clizbe Inet: JPClizbe(a)comcast DOT nyet Golden Bear Networks PGP/GPG KeyID: 0x608D2A10 "Be who you are and say what you feel because those who mind don't matter and those who matter don't mind." - Dr Seuss, "Oh the Places You'll Go" signature.asc Description: OpenPGP digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: BZIP2 algorithm isn't supported after compiling gnupg from source code
On Jan 07, 2006 at 00:10 +0300, lusfert wrote: > checking whether to enable the BZIP2 compression algorithm... yes > checking for bzlib.h... no maybe you must install somthing as bzip-devel? Vale! -- Pawel I. Shajdo ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: BZIP2 algorithm isn't supported after compiling gnupg from source code
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Clizbe wrote: > Come on, Debianistas. I know there are Debian users out there who can answer > all > of this. Taking this question self-contained: # apt-get install libbz2-dev Then gnupg's configure should find it just fine, without specifying a path. Kind regards, Philipp Kern -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (Darwin) iD8DBQFDvvZN7Ro5M7LPzdgRApGLAJ0evexwO0OtQrPoFrxBRY2fDVuUPgCguhlk SsRFhWTRA4mYqRXwr5BLa8o= =snTb -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: BZIP2 algorithm
Henry Hertz Hobbit wrote on 06.01.2006 16:34: > lusfert wrote: >>$ cd ./gnupg-1.4.2 >>$ ./configure > > > Where did the output go? To /dev/null? Output was on the screen... > Since you are not > using C Shell (please use bash, sh, of ksh),do it this way: > I use bash. > $ ./configure > LOG.config 2> ERR.config > > Now you can study the results to decide what to do next... > I can already tell you right now that you will be building > the BZIP library. If you see the following magic line in > the LOG.config file: > > "checking whether to enable the BZIP2 compression algorithm... yes" > > you will know you are okay. If you don't ... more on that in a > moment... > OK, see here: http://lists.gnupg.org/pipermail/gnupg-users/2006-January/027768.html Log file does contain above line. > >>$ make > > > Ditto with output going to other files... > > $ make > LOG.make 2> ERR.make > $ ls -l ERR.* > > If both of those files are empty, you may be okay. If they > are and you are happy with what is in the LOG.* files, then > you can proceed... > Both files (ERR.config & ERR.make) are empty. Log file contains magic line too. > > First, I am assuming you put the program by default into /usr/local. GnuPG installs into /usr/local/bin. > Do you have /usr/local/bin and /usr/local/sbin first in your PATH? > I ALWAYS DO THIS TO MY PATH VARIABLE. That is because I leave the > older version of GnuPG (and whatever else) alone since I don't want > to get whacked by an update from the OS creators that undoes all that > nice work to get things as up to date as possible (especially useful > with GnuPG). Download bzip2 and install it in all its glory (which > includes not only the executables, but also the header and bzip2 > link library files. > > http://www.bzip.org/ > Thanks, this helps. I installed bzip2-1.0.3.tar.gz and after this command "./configure" found bzlib.h without additional options. Now after compiling "gpg --version" displays: gpg (GnuPG) 1.4.2 [...] Compression: Uncompressed, ZIP, ZLIB, BZIP2 Thanks to everyone! -- My current OpenPGP key ID: 0x500B8987 Key fingerprint: E883 045D 36FB 8CA3 8D69 9C79 9E35 3B56 500B 8987 Encrypted e-mail preferred. signature.asc Description: OpenPGP digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
OpenPGP debugging
Hi, I am searching for an OpenPGP fileformat analyzer. gpg -v -v -v -v -v --list-packets openpgp.key is coming near, but I am still missing a hexdump of the individual fields, or even a description down to the bit level if necessary. This is necessary to analyze the correct encoding of certain fields. One interesting document I found today gives examples of the PKCS standards: http://www.zone-h.org/files/33/examples.pdf Is there something similar available for OpenPGP? Best regards, Philipp Gühring ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: OpenPGP debugging
On Sat, Jan 07, 2006 at 02:53:21AM +0100, Philipp Gühring wrote: > Hi, > > I am searching for an OpenPGP fileformat analyzer. > > gpg -v -v -v -v -v --list-packets openpgp.key > > is coming near, but I am still missing a hexdump of the individual fields, or > even a description down to the bit level if necessary. > This is necessary to analyze the correct encoding of certain fields. http://pgp.iijlab.net/pgpdump.html > One interesting document I found today gives examples of the PKCS standards: > http://www.zone-h.org/files/33/examples.pdf > Is there something similar available for OpenPGP? RFC-2440 has a few examples, but not that many. David ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
