-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> Having GnuPG use swap partitions/files is a risky business.
As a general principle, I'm unconvinced of the truth of this as a
general statement.
It's risky within certain security models. Let's not go about saying
it's universally risky. Le
Hi there,
On Tuesday, 27. February 2007 02:56, Joseph Oreste Bruni wrote:
> Oh yeah, third thing:
>
> The "insecure memory" warning just means that the executable probably
> needs to be setuid-root in order to allocate wired memory. You can
> ignore this and still use the product. It just means th
On 2/27/07, at 1:57 AM, Benjamin Donnachie wrote:
> boksbox wrote:
>> I tried to install the 1.4.6 update to my 1.4.5 GnuPG. As I
>> followed the
>> compile instruction I encounter an error.
>
> Try my gnupg 1.4.6 binary install at
> http://www.py-soft.co.uk/~benjamin/download/mac-gpg/GnuPG1.4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> Following your advice, I ran:
>yum update gnupg
> a few days ago, and now I have v1.4.5 . But I
> see that you have v1.4.6 . I ran yum again,
> and it got nothing new. So what's happening?
I'm guessing that FC4 isn't getting updates very fre
On Sat, 24 Feb 2007 12:42:09 -0600, Robert J. Hansen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>> On FC4 with gpg 1.4.1:
>
> Please upgrade. There have been a couple of security updates since
> 1.4.1.
>
[...]
Following your advice, I ran:
yum update gnupg
a few days ag
A company I'm getting a data feed from sent me a public key and an
encrypted file. I want to decrypt it, but I don't know I'm doing. My
naive approach is not working:
$ gpg --homedir=/var/httpd/keyring --decrypt upc.xml.pgp
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.
Two things:
1) You can't decrypt a file with a public key. Obviously the company
who sent you the file doesn't understand public-key encryption either
because they would need YOUR public key in order to encrypt files to
you. The first step for them would have been to request a key from
yo
Oh yeah, third thing:
The "insecure memory" warning just means that the executable probably
needs to be setuid-root in order to allocate wired memory. You can
ignore this and still use the product. It just means that gpg tried
to allocate memory that cannot be swapped to disk and failed due
On Sat, 24 Feb 2007 19:55:58 +0100, Sven Radde wrote:
> Robert J. Hansen schrieb:
>>> If so, why was (sign and encrypt) not offered as an option?
>>
>> Having one key that can be used for both signing and encryption
>> operations is thought by some to be bad crypto policy. The problems
>> wi
On Sat, Feb 24, 2007 at 02:15:10PM -0800, Dan Tipton wrote:
> Hello,
>
> I have a question about how GPG assigns default
> preferences to a key. When I check the version I get a
> list of supported ciphers, digests, etc:
>
> Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256,
> TWOFISH
> Hash: MD
On Saturday 24 February 2007 00:22:34 John Clizbe wrote:
> Bruno Costacurta wrote:
> > On Sunday 18 February 2007 23:11:37 Bruno Costacurta wrote:
> >> Hello,
> >>
> >> I updated the expiration (via gpg --edit-key using expire option) of my
> >> key and (re)sended it to a keyserver (via gpg --send-
boksbox wrote:
> I tried to install the 1.4.6 update to my 1.4.5 GnuPG. As I followed the
> compile instruction I encounter an error.
Try my gnupg 1.4.6 binary install at
http://www.py-soft.co.uk/~benjamin/download/mac-gpg/GnuPG1.4.6.dmg
Ben
___
Gnu
> I tried to install the 1.4.6 update to my 1.4.5 GnuPG. As I
> followed the
> compile instruction I encounter an error. When I do ./configure
> an error
> comes up at the end of the display and according to the logs:
The configure script can't find a C compiler. Make sure you have the
X
Do you have the developer tools installed?
Joe
On Feb 23, 2007, at 10:36 PM, boksbox wrote:
I tried to install the 1.4.6 update to my 1.4.5 GnuPG. As I
followed the
compile instruction I encounter an error. When I do ./configure
an error
comes up at the end of the display and accordi
Robert J. Hansen schrieb:
>> If so, why was (sign and encrypt) not offered as an option?
>
> Having one key that can be used for both signing and encryption
> operations is thought by some to be bad crypto policy. The problems
> with it appear to be mostly theoretical, though.
If you use "gp
Hello,
I have a question about how GPG assigns default
preferences to a key. When I check the version I get a
list of supported ciphers, digests, etc:
Cipher: 3DES, CAST5, BLOWFISH, AES, AES192, AES256,
TWOFISH
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512
Compression: Uncompressed, ZIP, ZLI
I tried to install the 1.4.6 update to my 1.4.5 GnuPG. As I followed the
compile instruction I encounter an error. When I do ./configure an error
comes up at the end of the display and according to the logs:
...
configure:3397: checking for cl.exe
configure:3427: result: no
configure:3456: erro
17 matches
Mail list logo
