> > I tried to use "preset passphrase" feature but it does not work.
> > Log shows that gpg-agent seemingly receives passphrase but later
> > when agent should use the cached passphrase it ask for it again
> > from pinentry.
> Now I started to debug gpg-agent.
> I.e. "miss" is changed to "hit". H
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I tried to use "preset passphrase" feature but it does not work.
> Log shows that gpg-agent seemingly receives passphrase but later
> when agent should use the cached passphrase it ask for it again
> from pinentry.
> 2008-07-14 11:10:00 gpg-agent[30
> 1. You are not root enough (no problem is /usr/local/bin writable by you)
Ooops!
I mean "no problem if /usr/local/bin is writable by you"
Gabor
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
> /usr/company/bin/ginstall: cannot remove `/usr/local/bin/gpgsplit':
> Read-only file
> system
> bash-2.05b$
1. You are not root enough (no problem is /usr/local/bin writable by you)
and
2. You forgot to remount /usr/local to r/w
Gabor
___
Gnupg-us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I'd start by asking whether you really need that key. 512-bit RSA is
> nowhere near modern standards of sufficiency; it is quite likely that in
> just a few years such keys will be able to be broken by motivated high
> school students.
This key is
I have the same problem as was answered by David Shaw in 2004:
http://osdir.com/ml/gnu.gnupg.users/2004-06/msg00022.html
(Converting a vry old PGP key (2.6.3ia) to GnuPG.)
However the method he suggested does not work for me:
$ gpg --s2k-cipher-algo cast5 --edit-key 0x5D144299
gpg (GnuPG) 1.
> gpg --list-public-keys
> 1024D/78830E32
> 1024D/44CAAE70
>
> gpg --encrypt -- sshfs-debug-v3.txt.tar.gz ??
"--recipient" is what you need.
It can be used multiple times.
It accepts key ID as well as email address.
gpg --encrypt --recipient 0x78830E32 \
--recipient [EMAIL PROTECTED]
> So did you. This scheme is poorly specified, based on an incorrect
> understanding of user needs, as a practical matter can be cracked, is
> rife with implementation difficulties, and you seem to have no
> understanding of the implicit tradeoffs and compromises which go into it.
I'm sure you ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> May I quote from the readme of loop-aes:
>
> Recommended key setup mode is multi-key-v3, which is based on gpg
> encrypted key files. In this mode, the passphrase is protected against
> optimized dictionary attacks via salting and key iteratio
> > $ cat /etc/passwd | aespipe | md5sum Password:
> > 9220c2e1d5a5a83710d020b04c306c24 - $ cat /etc/passwd | aespipe | md5sum
> > Password: 9220c2e1d5a5a83710d020b04c306c24 - $
> >
> ?
>
> Apples and Oranges. Consider:
Don't consider please. :-)
Original question was what are proper tools
> > The password is not random therefore every time you
> > encrypt the same plaintext you got the same cryptfile.
>
> No, you won't. All sound encryption schemes use a bit of random to make
> the resulting ciphertext different. In the easiest case this is called
> a salt and used to stop dictio
> Ian> I have a local file that I want to encrypt and upload to a remote
> Ian> machine in encrypted form. Encrypting is farily quick, but
> Ian> uploading is slow, so I use rsync for the other (unencrypted)
> Ian> files. But the fact that the encrypted file is different each time
> Ian> defeats
> I have a local file that I want to encrypt and upload to a remote
> machine in encrypted form. Encrypting is farily quick, but uploading is
> slow, so I use rsync for the other (unencrypted) files. But the fact
> that the encrypted file is different each time defeats the rsync
> incremental upl
Dear folks,
I tried to use "preset passphrase" feature but it does not work.
Log shows that gpg-agent seemingly receives passphrase but later
when agent should use the cached passphrase it ask for it again
from pinentry.
Is the problem mentioned by Andreas Hartmann fixed?
(http://www.mail-archive
14 matches
Mail list logo
