On Thu, 1 Aug 2013 20:40, bill.allomb...@math.u-bordeaux1.fr said:
> gpg: keyblock resource `/root/.gnupg/secring.gpg': file open error
I did a quick test:
$ fortune | gpg --no-options --homedir=$(pwd) --no-default-keyring \
--keyring ~/.gnupg/pubring.gpg --secret-keyring /dev/null \
Hi,
thanks for the reply!
>> I think "method" in the example above is just indicating that this is a PGP
>> key.
Exactly. However, how does RIPE server-side software detect that it's
a PGP key? Is this information(besides other information like key
creation date and UID) written into pubring.gp
On Fri, 2 Aug 2013 08:55, w...@gnupg.org said:
> If used in an empty directory it only creates one file: trustdb.gpg. I
> thinkl it is pissible to do something about that. The hack with using
Alright. Done for all branches. See git.gnupg.org.
Shalom-Salam,
Werner
--
Die Gedanken sind
Hi,
I need to create a public and private key pair for a person
representing an organization, upload the public key to RIPE(regional
Internet registry in Europe) public server, create some database
entries using those public and private keys and finally hand over the
private key + password protect
Martin T wrote:
> Hi,
>
> I need to create a public and private key pair for a person
> representing an organization, upload the public key to RIPE(regional
> Internet registry in Europe) public server, create some database
> entries using those public and private keys and finally hand over the
>
Diego,
I'm afraid this doesn't work because at the beginning I need to have
both the private and public key in order to carry out operations in
RIPE database. I don't see a difference if he generates the key pair,
uploads the ASCII armored public key to RIPE public database and then
has to send th
Martin T wrote:
> Hi,
>
> thanks for the reply!
>
>>> I think "method" in the example above is just indicating that this is a PGP
>>> key.
>
> Exactly. However, how does RIPE server-side software detect that it's
> a PGP key? Is this information(besides other information like key
> creation dat
On Aug 2, 2013, at 3:56 AM, Martin T wrote:
> Hi,
>
> thanks for the reply!
>
>>> I think "method" in the example above is just indicating that this is a PGP
>>> key.
>
> Exactly. However, how does RIPE server-side software detect that it's
> a PGP key? Is this information(besides other infor
On 02.08.2013, Doug Barton wrote:
> However, what you really want to encourage is the verification of the
> signature (ignoring the bootstrapping problem for the moment), and even
> forcing people to download the signature file won't do that.
Enforcing something to people mainly results in the o
Hi,
> Your description sounds, to me, as if you are only generating a key for the
> other persons use.
Not quite. At the beginning I need to use those keys myself in order
to create the needed database objects. Once those are done, I need to
hand over the private key to other person. So basicall
On 08/02/2013 01:31 PM, Martin T wrote:
> Hi,
>
>> Your description sounds, to me, as if you are only generating a key for the
>> other persons use.
>
> Not quite. At the beginning I need to use those keys myself in order
> to create the needed database objects. Once those are done, I need to
>
Il 02/08/2013 14:25, Martin T ha scritto:
> I'm afraid this doesn't work because at the beginning I need to have
> both the private and public key in order to carry out operations in
> RIPE database. I don't see a difference if he generates the key pair,
> uploads the ASCII armored public key to R
On Aug 2, 2013, at 1:17 AM, Philip Jägenstedt wrote:
> Hi all,
>
> I'm new to GnuPG and have probably been a little too ambitious for my
> own good. I originally signed key AB4DFBA4 at level 3 after a meetup,
> but was later paranoid that I was too lax and wanted to resign it at
> level 2, but d
13 matches
Mail list logo
