On Feb 27, 2007, at 12:13 PM, [EMAIL PROTECTED] wrote:
Joseph Oreste Bruni <[EMAIL PROTECTED]> writes:
Some OS's allow non-root users to allocate a limited
amount of wired memory (BSD, OS X) whereas HP-UX does not.
HP-UX can ! It just doesn't, by default.
root can use setprivgrp(1M) to all
Joseph Oreste Bruni <[EMAIL PROTECTED]> writes:
> Some OS's allow non-root users to allocate a limited
> amount of wired memory (BSD, OS X) whereas HP-UX does not.
HP-UX can ! It just doesn't, by default.
root can use setprivgrp(1M) to allow specified groups of
ordinary users the "mlock" privil
-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
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
