-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi Faramir,
> Is key 0x4F25E3B6 the current key used for signing files?
according to the website, it is:
In the 3rd text paragraph on http://gnupg.org/download/integrity_check.en.html
"signing key" links to http://gnupg.org/signature_key.en.htm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
Is key D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6 (
0x4F25E3B6 ) the current key used for signing files? I suppose it is,
but I'd like to ask before issuing a local signature.
Best Regards
-BEGIN PGP SIGNATURE-
Ver
On 1/30/12 6:09 PM, John Clizbe wrote:
> I always get a chuckle every time I read someone writing that inline signing
> is
> somehow "deprecated." Strangely enough, the only place I can find the
> origination of such an idea is in the PGP/MIME RFC 3156 itself which strikes
> me
> as somewhat self
Jerry wrote:
> On Mon, 30 Jan 2012 02:23:04 +
> MFPA articulated:
>
>> That is an unfortunate consequence of signing my message with GnuPG;
>> all lines lose trailing spaces and any line beginning with a dash gets
>> prefixed with a dash and a space.
>
> That is because you are using "inline"
MFPA wrote:
> Hi
> On Monday 30 January 2012 at 2:13:48 AM, Jerry wrote:
>> On Mon, 30 Jan 2012 01:52:44 + MFPA articulated:
>>> Looking through recent postings, the signature
>>> delimiter seems to appear in about half of the
>>> messages on this list.
>>> - --
>>> Best regards
>>> MFPA
>>> m
I figured it out, there was a "sign" button on the windows version which was
the clear sign.
Hauke Laging wrote:
>
> Am Montag, 30. Januar 2012, 22:53:56 schrieb Belleraphone:
>
>> So far
>> everytime I try to clearsign the .txt file with the info posted above
>> but
>> it does not work.
>
>
On Mon, Jan 30, 2012 at 3:12 PM, Belleraphone wrote:
>
> I realize that, but how do I make it so that my files are fit to be
> clearsigned? I was given a bunch of information from a website that said
> what needed to be clearsigned. How do I put this information into a file
> that gpu.exe can read
Am Montag, 30. Januar 2012, 22:53:56 schrieb Belleraphone:
> So far
> everytime I try to clearsign the .txt file with the info posted above but
> it does not work.
"It doesn't work" without any explanation what exactly you have done and what
"It doesn't work" means precisely does not make it ea
My instructions just tell me to clearsign the following and then the paste
the results in a box. Here's what i have to clearsign. Keep in mind I'm
using GnuPG for windows.
mode new_user
username XX
fprint
FUDForum XXX
Am Montag, 30. Januar 2012, 22:12:13 schrieb Belleraphone:
> I realize that, but how do I make it so that my files are fit to be
> clearsigned?
I am not sure whether I understand what you mean.
--clearsign is usable for text files only not for binary files. Those need
--sign or --detach-sign.
>
On 01/30/2012 13:12, Belleraphone wrote:
>
> I realize that, but how do I make it so that my files are fit to be
> clearsigned? I was given a bunch of information from a website that said
> what needed to be clearsigned. How do I put this information into a file
> that gpu.exe can read and clearsi
I realize that, but how do I make it so that my files are fit to be
clearsigned? I was given a bunch of information from a website that said
what needed to be clearsigned. How do I put this information into a file
that gpu.exe can read and clearsign?
Hauke Laging wrote:
>
> Am Montag, 30. Januar
Am Montag, 30. Januar 2012, 21:57:41 schrieb Belleraphone:
> I'm at the gpg.exe application, which file do I clearsign exactly?
You are probably the only one who knows which file(s) you want clearsigned.
Hauke
--
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
signature.asc
Description
I'm at the gpg.exe application, which file do I clearsign exactly? Do I need
to export my key? I'm a little new at this.
Werner Koch wrote:
>
> On Mon, 30 Jan 2012 07:57, cco...@gmail.com said:
>> Title of this says it all. How do I clear sign my stuff in the Windows
>> version of GnuPG?
>
>
On Mon, 30 Jan 2012 18:15, r...@sixdemonbag.org said:
> Out of the box, Outlook doesn't support PGP/MIME and won't even render
> the plain text portions -- or, at least, such was the case the last time
> I checked Outlook, which was some time ago: I try to avoid dealing with
It renders the plain
On Mon, Jan 30, 2012 at 10:41:19AM -0500, michaelquig...@theway.org wrote:
> I believe Doug's reference to MAILMAN settings is suggesting that you log
> into the mailing list manager
> (http://lists.gnupg.org/mailman/options/gnupg-users) Once you get in and
> edit your settings, the last settin
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
NotDashEscaped: You need GnuPG to verify this message
>>> - --
>>> Best regards
...
>> Interestingly enough, your "Sig Delimiter" is bonked.
> That is an unfortunate consequence of signing my message with GnuPG;
> all lines lose trailing spac
On 1/30/12 12:07 PM, Werner Koch wrote:
> Outlook has PGP/MIME support via a plugin.
Out of the box, Outlook doesn't support PGP/MIME and won't even render
the plain text portions -- or, at least, such was the case the last time
I checked Outlook, which was some time ago: I try to avoid dealing wi
On Mon, 30 Jan 2012 16:34, r...@sixdemonbag.org said:
> Fact two: it's easy to find MUAs, MTAs and other software in the chain
> that don't support (or outright break!) PGP/MIME. Outlook is a good
Outlook has PGP/MIME support via a plugin. Thunderbird has PGP/MIME
support via plugin. Both are
Hello!
We are pleased to announce the availability of a new stable GnuPG-1
release: Version 1.4.12.
The GNU Privacy Guard (GnuPG) is GNU's tool for secure communication
and data storage. It is a complete and free replacement of PGP and
can be used to encrypt data and to create digital sign
> - Message from Jerry on Mon, 30 Jan 2012
> 06:27:41 -0500 -
> Unfortunately, eliminating dupes, aka "CC'd" mail is not that easy.
I believe Doug's reference to MAILMAN settings is suggesting that you log
into the mailing list manager
(http://lists.gnupg.org/mailman/options/gnupg-user
On 1/30/12 4:42 AM, Steve wrote:
> I don't understand why Enigmail still uses inline as a
> default setting...
There is no "Enigmail-approved" reason. Everyone on the Enigmail team
who's contributed to this decision has their own reasons for their
support of PGP/MIME or lack thereof. These are
On Mon, 30 Jan 2012 15:27:37 +0100
Peter Lebbing articulated:
> On 30/01/12 12:27, Jerry wrote:
> > Now, thanks to you and a few other morons,
>
> For crying out loud, stop crying out loud. Get over it. People will
> CC you. Stop bothering us with your complaints every time. We all,
> including y
On Mon, 30 Jan 2012 07:57, cco...@gmail.com said:
> Title of this says it all. How do I clear sign my stuff in the Windows
> version of GnuPG?
gpg --clearsign FILE
results in FILE.asc
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
___
On 30/01/12 12:27, Jerry wrote:
> Now, thanks to you and a few other morons,
For crying out loud, stop crying out loud. Get over it. People will CC you.
Stop bothering us with your complaints every time. We all, including you,
have better things to do with our time than repeating this annyoing
dis
Title of this says it all. How do I clear sign my stuff in the Windows
version of GnuPG?
--
View this message in context:
http://old.nabble.com/Clearsigning-on-Windows-tp33227342p33227342.html
Sent from the GnuPG - User mailing list archive at Nabble.com.
_
> That is because you are using "inline" rather than "mime" for signing.
> The "inline"method has been for the most part deprecated. You might
> want to give serious thought to switching your signing method.
Which is, why I don't understand why Enigmail still uses inline as a default
setting…
Ch
On Mon, 30 Jan 2012 01:45:01 -0800
Doug Barton articulated:
> On 01/30/2012 01:34, Jerry wrote:
> > On Mon, 30 Jan 2012 02:23:04 +
> > MFPA articulated:
> >
> >> That is an unfortunate consequence of signing my message with
> >> GnuPG; all lines lose trailing spaces and any line beginning wit
On 01/30/2012 01:34, Jerry wrote:
> On Mon, 30 Jan 2012 02:23:04 +
> MFPA articulated:
>
>> That is an unfortunate consequence of signing my message with GnuPG;
>> all lines lose trailing spaces and any line beginning with a dash gets
>> prefixed with a dash and a space.
>
> That is because y
On Mon, 30 Jan 2012 02:23:04 +
MFPA articulated:
> That is an unfortunate consequence of signing my message with GnuPG;
> all lines lose trailing spaces and any line beginning with a dash gets
> prefixed with a dash and a space.
That is because you are using "inline" rather than "mime" for si
On 30/01/12 03:23, MFPA wrote:
>> Interestingly enough, your "Sig Delimiter" is bonked.
>
> That is an unfortunate consequence of signing my message with GnuPG;
> all lines lose trailing spaces and any line beginning with a dash gets
> prefixed with a dash and a space.
Or: how a boring off-topic
31 matches
Mail list logo
