Re: Donations, FSF as a charitable organization and merry minds of whizdom

-BEGIN PGP SIGNED MESSAGE- Hash: SHA224 Was Fri, 05 Jan 2007, at 08:17:26 -0500, when Robert J. Hansen wrote: > Matthias Kirschner wrote: >> But considering your motivation ("grateful [... to] have a Free >> Software implementation of the OpenPGP protocol.") you donated your >> m

Re: Donations

-BEGIN PGP SIGNED MESSAGE- Hash: SHA224 Was Fri, 05 Jan 2007, at 14:58:26 +0100, when Werner Koch wrote: > On Fri, 5 Jan 2007 11:06, [EMAIL PROTECTED] said: >> But considering your motivation ("grateful [... to] have a Free Software >> implementation of the OpenPGP protocol.") y

Re: gnupg clearsigning question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA224 Was Thu, 28 Dec 2006, at 10:14:53 -0500, when [EMAIL PROTECTED] wrote: > (1) the simplest: > just encrypt the keyfile, and decrypt it when necessary > (the problem is that this calls attention to itself, by having an > encrypted file present

Re: Christmas is upon us again.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA224 Was Tue, 05 Dec 2006, at 16:06:56 -0600, when Robert J. Hansen wrote: > Whether you're secular or religious, atheist or devout, I think we can > all agree that the time of the year known as Christmas will soon be upon > us. This is historic

Re: Logo contest closed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA224 Was Thu, 02 Nov 2006, at 19:12:30 +0100, when Werner Koch wrote: > Hi! > I have been reminded of another logo in my spam filters. It was > received on Monday; thus in time. It is now at > http://logog-contest.gnupg.org/subm-31.html . Thi

Re: Summary: Windows GUI recommendation for USB disk

-BEGIN PGP SIGNED MESSAGE- Hash: SHA224 Was Wed, 1 Nov 2006, at 20:43:19 -0800 (PST), when Robert Eden wrote: > My tool prompts the user for a pass-phrase (twice), places some > simple restrictions on the pass-phrase (10 characters, 3 words), and > opens up a dialog box. The user

Re: GPGDisk campaign

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Sun, 22 Oct 2006, at 15:53:11 +0200, when Werner Koch wrote: > Frankly, we are not very keen to do that because with most commonly > used OSes you need to dive deeply into that OS. After all it is a > matter of paying ;-). Every work sh

Re: GPGDisk campaign

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Sun, 22 Oct 2006, at 00:10:55 +0200, when Jřrgen Lysdal wrote: > lol, very cool with the steganography thing... Just checking environment. (-; Namely, on an other privacy/security related list, of a more general nature though, it happe

Re: GPGDisk campaign

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Sat, 21 Oct 2006, at 17:36:40 -0500, when Robert J. Hansen wrote: > Jørgen Lysdal wrote: >> lol, very cool with the steganography thing... > I'll be the bad guy and rain on the parade, and give the reasons why > this is very unlikely to

GPGDisk campaign

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Starting right now, with the fresh New Moon... GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GPGDisk GP

Re: decrypt problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Sat, 21 Oct 2006, at 13:54:52 +0200, when itsec.info wrote: > I have encrypted a large file (280MB) with gpg v1.4.2 on suse 10.0. > By decrypting the file I get the following error message: > gpg: Problem reading source (10429120 bytes

Re: [Announce] GnuPG 1.9.93 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Wed, 18 Oct 2006, at 19:18:09 +0200, when Werner wrote: > BTW, the logo-contest is still running and the submitters would > probably like to see some more donations ;-). See > www.gnupg.org/misc/logo-contest.html . Oh, Gee ... spot! I s

Re: RFCs, standards, pink bunnies and flower patterns

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Tue, 17 Oct 2006, at 22:07:03 -0500, when Ryan wrote: > On 10/17/06, Mica Mijatovic <[EMAIL PROTECTED]> wrote: >> ... >> There is no any whimsicality in it (the previous message and wider) and >> the answers/o

Re: RFCs, standards, pink bunnies and flower patterns

-BEGIN PGP SIGNED MESSAGE- Hash: TIGER192 Was Tue, 17 Oct 2006, at 14:31:34 -0700, when Cary wrote: > Mica, > While your comments are whimsical and, in some case very true, the point is > HTML mail is here to stay. You or I will not stop it. I think the point of > this thread w

Re: RFCs, standards, pink bunnies and flower patterns

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Tue, 17 Oct 2006, at 15:34:39 +0100 (BST), when Nicholas wrote: >> Of course that it doesn't mean that HTML should be banished >> completely from the 'lectronic mail world, but it has its essential >> limitations as for the cryptographic

RFCs, standards, pink bunnies and flower patterns was -- Re: GPG Outlook Plug-In and Signatures

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Sun, 15 Oct 2006, at 22:27:36 -0500, when Ryan wrote: > On 10/14/06, Werner Koch <[EMAIL PROTECTED]> wrote: >> Anyway, HTML mails are evil. > But unfortunately they're here to stay. RFC 2557 is now listed as > "standards track". RFCs a

Re: GPG Outlook Plug-In and Signatures

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Fri, 13 Oct 2006, at 23:36:43 -0400, when John wrote: > Alphax wrote: >> PGP/MIME capable mail clients /may/ handle it, but you'd have to >> actually try it to be certain. Such a test should be conducted off-list >> in order to avoid fl

Re: [Announce] GnuPG Logo Contest

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Wed, 20 Sep 2006, at 08:34:19 +0200, when Werner wrote: > On Wed, 20 Sep 2006 03:06, Benjamin Esham said: >> I believe what Werner meant was that your submitted image should be at >> least 300 pixels wide or 300 pixels tall. (Of course

Re: [Announce] GnuPG Logo Contest

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Tue, 19 Sep 2006, at 15:01:05 +0200, when Werner wrote: > Hi! > After 8 years the time has come to modernize the GnuPG logo and to > work on a new layout of the website. > We appreciate Thomas Löffelholz's Gnus-guarding-the-door logo w

Re: Compiling GnuPG 1.4.5 for Windows on Windows

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Fri, 08 Sep 2006, at 08:23:35 +0200, when Werner wrote: > On Thu, 7 Sep 2006 22:57, Mica Mijatovic said: >> And when I'm already at the desk, just a brief note that if a source >> code is being delivered as well, t

Re: Compiling GnuPG 1.4.5 for Windows on Windows

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Sat, 09 Sep 2006, at 11:28:26 -0500, when Troy wrote: >>> Werner Koch wrote: >>>> On Thu, 7 Sep 2006 22:57, Mica Mijatovic said: >>>>> >>>> Pretty easy. You only need to take

Re: Compiling GnuPG 1.4.5 for Windows on Windows

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Fri, 08 Sep 2006, at 10:59:13 -0500, when Troy wrote: > Werner Koch wrote: >> On Thu, 7 Sep 2006 22:57, Mica Mijatovic said: >> >>> >> >> Pretty easy. You only need to take the po/gnupg.pot fil

Re: Compiling GnuPG 1.4.5 for Windows on Windows

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Thu, 07 Sep 2006, at 13:25:25 +0200, when Carlo wrote: > By the way, I have to point out a small mistake in the credits in > the "PGP signed HTML" page > ... ;-) > I am not the autho

Re: Compiling GnuPG 1.4.5 for Windows on Windows

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Wed, 06 Sep 2006, at 07:54:13 -0400, when C wrote: > How do I do this? You have instructions here on how to compile the official version, CVS version and CVS version with some additions, both in MSYS

Re: signature comments?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Tue, 06 Jun 2006, at 00:28:18 -0400, when Zach wrote: > I've always wondered how to get comments put under the signature > header... I've seen them on sigs before and would like to have my > public key address put there. Does anyone know

Re: question about compiling gpg with cygwin

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Sun, 28 May 2006, at 11:36:06 +0200, when Henk wrote: > There's no other way, sorry. > Yes there is ;-) > I changed the settings from my Notepad2 from Windows (CR LF) to Unix > (LF) and that solved the problem. I apologize then. I

Re: question about compiling gpg with cygwin

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Sat, 27 May 2006, at 21:41:04 +0200, when Henk wrote: > On Sat, 27 May 2006 21:13:15 +0200GMT (27-5-2006, 21:13 +0200, where I > live), Mica Mijatovic wrote: >>>> Anyway, what is this prep.sh? >>> #!/bi

Re: question about compiling gpg with cygwin

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Sat, 27 May 2006, at 20:27:44 +0200, when Henk wrote: > On Fri, 26 May 2006 15:21:50 -0400GMT (26-5-2006, 21:21 +0200, where I > live), Joe Smith wrote: >>> configure: creating ./config.status >>> config.status: creating >>> .infig.s

Re: Date and time format

-BEGIN PGP SIGNED MESSAGE- Hash: TIGER192 Was Sat, 08 Apr 2006, at 13:58:45 +0400, when lusfert wrote: Is it possible to change date format in GPG output? >> >> I tried this to figure out many times but couldn't. >> >> I also expected that GPG will take over the local User's

Re: Date and time format

-BEGIN PGP SIGNED MESSAGE- Hash: TIGER192 Was Fri, 07 Apr 2006, at 13:55:47 +0400, when lusfert wrote: > John W. Moore III wrote on 07.04.2006 2:37: >> David Shaw wrote: >> OS setting via LC_TIME, according to Microsoft, though I have no idea how to set it on win32. >> >

Re: Date and time format

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Was Fri, 07 Apr 2006, at 01:31:40 +0400, when lusfert wrote: > Is it possible to change date format in GPG output? I tried this to figure out many times but couldn't. I also expected that GPG will take over the local User's setting of the

Re: failure notice

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Mon, 02 Jan 2006, at 14:46:59 +0100, when Werner wrote: > On Sat, 24 Dec 2005 14:49:23 +0100, Mica Mijatovic said: >> : >> 217.69.77.222_failed_after_I_sent_the_message./Remote_host_said:_550_Administrative_proh

Re: line wrapping

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Sun, 25 Dec 2005, at 08:58:57 -0800, when vedaal wrote: >>Your lines, as to the form they form, look like a verses. Is >>that done >>deliberately or your Eudora again entangles on its own? > done intentionally on my own, > each tho

Re: Create key's over 4096 bit ????

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Fri, 23 Dec 2005, at 10:07:07 -0800, when vedaal wrote: > might be interesting to see the year 2020 gnupg version, > the max keylength proposed then, > and then link back to this thread ;-) Your lines, as to the form they form, look

failure notice

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Hello GPGUsers, Could someone please explain to me what the term "Administrative_prohibition" means in the context of the text quoted here: /// Hi. This is the qmail-send program at mail.gmx.net. I'm afraid I wasn't able to deliver your message

Re: The never-ending GD discussion,part 74

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Thu, 27 Oct 2005, at 10:51:22 +0200, when Realos wrote: [about the personal web pages for public PGP keys] > Yes this may be the best of both types of servers. It seems to be a > very small change in protocol. Well, the protocols ar

Re: The never-ending GD discussion,part 74

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Sun, 23 Oct 2005, at 13:27:05 -0400, when David wrote: > It always amuses me that people complain bitterly about the GD storing > one key per email address, but don't complain, for example, about > people putting their key up on a web

Re: security measures?

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Sat, 15 Oct 2005, at 09:40:27 +0800, when nidhog wrote: > Do you have any suggestions as to what security measures can be > implemented in the following conditions: I'll give few ideas, if nothing else than to improve my "karma" for

Re: Lack of backwards compatability?

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Thu, 13 Oct 2005, at 18:51:33 -0400, when John wrote: > It would be easier to confirm the sig if one had the Key or ability to > Import it. Agree wholeheartedly. If someone would ask me if I could agree More I couldn't say I could.

Re: Lack of backwards compatability?

-BEGIN PGP SIGNED MESSAGE- Hash: TIGER192 Was Mon, 10 Oct 2005, at 21:09:59 +0930, when Alphax wrote: > Some old versions of GPG (1.0.x?) had support for the TIGER192 hash, but > this was later removed when it was dropped/rejected from the OpenPGP > standard. > However, these ver

Re: Recommended keyserver

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Thu, 13 Oct 2005, at 09:30:16 -0600, when Lares wrote: > Is there a recommended(read Endorsed) Keyserver? I'm looking at the > documentation we have here at gentoo.org and it recommends > pgp.mit.edu. It has been suggested that this s

Re: GPG Passphrase on the command line

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Mon, 26 Sep 2005, at 06:36:37 -0700, when nidhog wrote: > on the subject of piping, you might try to get a win32 port of unix's > echo command (echo.exe). win32's echo command sometimes have that ugly > \n attached and will mess up yo

Re: GPG Passphrase on the command line

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Mon, 26 Sep 2005, at 19:21:12 +0200 (MET DST), when Johan wrote: > nidhog wrote: >>it will show on ps and on your .bash_history > One of the reasons I don't use bash. I prefer tcsh. Who likes bash, may program/set it to not record

Re: Importing keys

-BEGIN PGP SIGNED MESSAGE- Hash: TIGER192 Was Wed, 14 Sep 2005, at 10:42:10 +0100, when Bob wrote: > I can't find anything in the man page about key import file formats. > Other than ascii files, can GnuPG import any other file formats and if > so what? Every file containing a va

Re: Sharing private.pub key and rings between two boxes

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Sun, 21 Aug 2005, at 20:09:34 +0100, when Sean wrote: > I have read the message below :) Hehehe... Okay, it's good for you. (: - -- Mica PGP keys nestled at: http://bardo.port5.com/pgpkeys/ ~~~ For PM please use my address as it is

Re: Sharing private.pub key and rings between two boxes

-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Was Sun, 21 Aug 2005, at 08:37:41 +0100, when Sean wrote: > I use GnuPG mainly on my Linux box but I also want to use it on my XP > box, is there anyway to share the keys safely between the both There is, yes, but it would help if you wo