From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how to create a pgp signature
Date: Tue, 22 Nov 2005 07:04:38 +0100 [thread overview]
Message-ID: <4382B4F6.1050402@mid.email-server.info> (raw)
In-Reply-To: <4382567E.4060407@planet.nl>
Holly Bostick schrieb:
> Jason Ausmus schreef:
>>> -----Original Message----- From: Alexander Skwar
>>> [mailto:listen@alexander.skwar.name] Sent: Sunday, November 20,
>>> 2005 3:48 AM To: gentoo-user@lists.gentoo.org Subject: Re:
>>> [gentoo-user] how to create a pgp signature
>>>
>>> You're answer was to a different question.
>>
>>
>> Whose answer was to a different question?
>>
>>
>>> Ralph Slooten schrieb:
>>>
>>>
>>>> gpg --gen-key
>>>
>>> Wrong.
>>>
>>>
>>>>> can anybody tell me methode to create my own pgp signature?
>>>
>>> That's the question.
>>
>>
>> Was the answer Ralph gave not correct? I don't understand what
>> you're trying to say...
>>
>>
>>> Alexander Skwar
>>>
>>> Posting out-of-order makes it easy to follow context.
>>
>
> Alexander may have been complaining about the top-posting,
Yep.
> or maybe the
> OP was not completely clear in the question,
Hm, possible as well, yes.
> or maybe Ralph
> misunderstood the difference between a /key pair/ and a /signature/:
That's what I assumed.
> Commands:
>
> ==> -s, --sign [file] make a signature
Yep. As I said - see the last line of my mail before the
mailinglist signature :) I don't think that it is helpful to
read man pages or help output to people.
> So if the question really does relate to creating a signature, Ralph was
> wrong. If the question was wrong, and a key pair needs to be generated
> in order to sign something, then Ralph was right.
Yes.
> However, other than pointing this out by the simple expedient of
> confusing everyone further, Alexander's reply was less than helpful,
> since it neither pointed out why the answer given was presumably not
> correct,
Uhm. Yes, I did not point that out. Why and how should I? OP
asked, how a signature can be created. That's a clear question.
I don't know how to explain, why --gen-key is the wrong answer.
It's just so plain totally wrong, that I just don't know how
to explain it.
> or provided a correct answer if the answer given was in fact
> not correct.
Oh, I did not? What about the "-s"? How's that not the "sign command"?
> .... but everybody could just read the man page and work it out for
> themselves, of course :) .
Or the help output. I wrote "gpg --help | grep 'make a'" which will,
among other things, return "-s". But that's not correct?
Alexander Skwar
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-22 6:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 22:46 [gentoo-user] how to create a pgp signature Jason Ausmus
2005-11-21 23:21 ` Holly Bostick
2005-11-22 6:04 ` Alexander Skwar [this message]
2005-11-22 10:20 ` Holly Bostick
2005-11-22 10:39 ` Alexander Skwar
2005-11-22 13:09 ` Ralph Slooten
2005-11-22 5:57 ` Alexander Skwar
-- strict thread matches above, loose matches on Subject: below --
2005-11-21 23:35 Peter Gordon
2005-11-20 10:48 El Nino
2005-11-20 11:19 ` Ralph Slooten
2005-11-20 11:48 ` Alexander Skwar
2005-11-20 11:46 ` Alexander Skwar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4382B4F6.1050402@mid.email-server.info \
--to=listen@alexander.skwar.name \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox