RE: how long should a password be?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > Everyone says it should be as long as possible, but there comes a point > where it's just impossible to remember anything longer than 20 > characters. What do you think? Passwords should be as many characters as you can remember plus one. Actua

Re: Compile without libiconv or libintl on Solaris

Thanks but same error. Yes, I showed that same link to our sysadmin and he said "do it anyway". You know, we just run gpg in batch mode on files. We don't need no stinkin sockets. Let's make the sockets go away! On 5/6/08, David Shaw <[EMAIL PROTECTED]> wrote: > > On Tue, May 06, 2008 at 03:

Re: Compile without libiconv or libintl on Solaris

Okay, I disabled a slew of stuff and was able to build statically. --disable-card-support --disable-agent-support --disable-gnupg-iconv --disable-photo-viewers --disable-keyserver-helpers --disable-ldap --disable-hkp --disable-finger --disable-generic --disable-keyserver-path --disable-dns-srv --

Re: Compile without libiconv or libintl on Solaris

On Tue, May 06, 2008 at 03:50:29PM -0400, Scott Lambdin wrote: > No, I had that pesky --enable-minimal in the configure command. It can > compile statically with that. here is the error I get otherwise: > > /usr/local/bin/gcc -g -O2 -Wall --static -o gpg gpg.o build-packet.o > compress.o compr

Re: confused about public key strength

Hi! Matt Kinni schrieb: Hello, I can't seam to figure out how the different bitstrengh of my public key effects anything. If someone encrypts something to my private key, isn't the strength of the private key that matters? The length of the public key equals the length of the private key. And

Re: confused about public key strength

Matt Kinni wrote: > Hello, I can't seam to figure out how the different bitstrengh of my > public key effects anything. If someone encrypts something to my > private key, isn't the strength of the private key that matters? No. Asymmetric cryptography has keys that come in public and private part

Re: Compile without libiconv or libintl on Solaris

No, I had that pesky --enable-minimal in the configure command. It can compile statically with that. here is the error I get otherwise: /usr/local/bin/gcc -g -O2 -Wall --static -o gpg gpg.o build-packet.o compress.o compress-bz2.o free-packet.o getkey.o keydb.o keyring.o seskey.o kbnode.o main

Need recommendation on keyserver code

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I need to build a private keyserver for interanl use. I have tried to get SKS to build, but I have never been able to get it to work. (The project seems to be almost abandoned.) I am using Fedora 9 on an x86_64 box with 4 gigs of ram and Numerix

Re: Compile without libiconv or libintl on Solaris

If I do a config like this, and ldd the resulting gpg binary, it still needs libiconv and libintl. ./configure --prefix=/place/gnupg-1.4.8 --without-readline --disable-gnupg-iconv --without-intl --without-iconv I've tried a few variations on this. I would like to compile statically but that f

confused about public key strength

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I can't seam to figure out how the different bitstrengh of my public key effects anything. If someone encrypts something to my private key, isn't the strength of the private key that matters? So I have a 1024bit DSA pub and 4096 elgamal key

Re: Compile without libiconv or libintl on Solaris

On Tue, May 06, 2008 at 01:26:44PM -0400, Scott Lambdin wrote: > Hello - > > Has anyone been able to compile 1.4.8 or 1.4.9 on Solaris without iconv or > intl? The only way I have been able to do it is with --enable-minimal and > that disables too much. Or am I going to have to really learn Make

Compile without libiconv or libintl on Solaris

Hello - Has anyone been able to compile 1.4.8 or 1.4.9 on Solaris without iconv or intl? The only way I have been able to do it is with --enable-minimal and that disables too much. Or am I going to have to really learn Makefiles? Thanks, --Scott -- CILCIL

Re: Open Pgp Smartcard ssh authentication Woes :(

For anyone that this may help, It appears I have solved my problems. It turns out that gnome-keying-manager was interfering by taking control of the ssh socket. This was realised because echo $SSH_AUTH_SOCKET returned: /tmp/keyring-X which was different to the socket that gpg-agent was set

Re: how long should a password be?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sven Radde escribió: > A salt essentially makes precomputed rainbow tables useless. > > A rainbow table consists of two columns, "password" and "hashed > password" and is filled by hashing a great number of passwords. Now, if > you know only the hash

Re: [Fwd: Re: Question about GnuPG Smartcard]

On Tue, 6 May 2008 00:03, [EMAIL PROTECTED] said: > I think I remember that 2048-bit RSA cards might be available soon... > Was that by PPC Card? Any news on that? We even have a new draft which allows to re-activate blocked card. New cards will be done but that will take several months. > P.S

Duplicity

Hello all, Following, in a way, the discussion about "How long should a passphrase be?", I am currently trying to come up with a sensible backup scheme using duplicity. Duplicity creates full and incremental backups of local files, encrypts them using GnuPG and moves them to a (remote) locatio