At 6:44 PM +0200 4/14/07, Alexander Feigl wrote:
[...]
Looks good.
Can anybody test it with 2.0.3 on Mac?
For me it look like there are problems with saving to key to disk. Importing
the key with 1.4.7 and then checking the key with 2.0.3 seems to work last
time I checked it (x86 Linux). At
Ludwig Hügelschäfer wrote the following on 4/14/07 8:57 PM:
Hi,
Charly Avital wrote on 14.04.2007 18:17 Uhr:
*Therefore, there is a difference in results (Key ID and fpr) when the
keyblock is imported from Thunderbird+Enigmail (inside option), and when
the same keyblock is saved
Alexander Feigl wrote the following on 4/14/07 12:30 AM:
[...]
So gpg behaves incorrectly on 1.4.7 for ppc, but correctly for i386, on 2.0.x
it behaves incorrectly for i386 but correct for amd64. Any chance there is
some problem in the architecture dependant part of gnupg?
That's way beyond
Philipp Gühring wrote the following on 4/10/07 1:35 AM:
Hi,
Is GnuPG supported on PowerPC architecture?
I tried to compile with the current GCC cross-compiler from
http://www.denx.de/en/News/WebHome
but I got a lot of compiler and linker errors about the MPI part of GnuPG,
and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alexander Feigl wrote the following on 4/7/07 9:30 PM:
[...]
I pasted a testing key below. The key with the key id 0x2D879666 gets
imported
as 0xB61454A3 here.
While such large keys seem like overkill. But gnupg also supports the SHA512
David Shaw wrote the following on 4/4/07 2:43 PM:
On Wed, Apr 04, 2007 at 02:02:17PM +0300, Charly Avital wrote:
Mark Dymek wrote the following on 3/27/07 6:02 PM:
when i install gnupg 1.4.7 on a mac os x systerm where does the
executable file get installed? in other words where does gnupg
David Shaw wrote the following on 4/4/07 2:43 PM:
On Wed, Apr 04, 2007 at 02:02:17PM +0300, Charly Avital wrote:
Mark Dymek wrote the following on 3/27/07 6:02 PM:
when i install gnupg 1.4.7 on a mac os x systerm where does the
executable file get installed? in other words where does gnupg
At 11:59 AM -0500 3/8/07, reynt0 wrote:
I apologize if I am wasting the time of some busy
and appreciated people, but I'd like to ask for
clarification:
Not that busy, let's try to sort out this issue.
The latest macgpg.sourceforge.net HowTo, v4.16,
says gcc 4.0.1 is needed.
You are right,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
reynt0 wrote the following on 3/7/07 3:51 AM:
[...]
I'm still looking
for an easy way to get the latest gnupg but for
OS 10.3.9, not OS 10.4.x.
[...]
At http://macgpg.sourceforge.net/, please scroll down to 'Files
where you will find:
For
Sascha Welter wrote the following on 3/7/07 4:11 PM:
(Wed, Mar 07, 2007 at 12:55:28PM +0200) Charly Avital wrote/schrieb/egrapse:
I can't remember whether or which security problems 1.4.1 comported, but
you will find complementary information in that site.
Since we've just had a security
David Shaw wrote the following on 3/7/07 8:08 PM:
[...]
Do you mean binary releases from somewhere or building your own? If
you're building your own, this is not the case, or at least, should
not be the case. If compiling 1.4.7 on Panther doesn't work, report
it as a bug. I will fix it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
At 6:21 PM -0500 3/7/07, David Shaw wrote:
[...]
Yes indeed.
Let me reiterate: as far as I'm concerned, if the current GPG doesn't
build on a particular version of OSX, that's a bug. And I'll do my
best to fix GPG so it does build.
David
On an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Tested successfully on PPC (Powerbook 15 G4 1.33GHz), and Intel Core 2
Duo (MacBook 2 13 2GHz), both running MacOS X 10.4.8.
Thank you Ben.
Charly
Benjamin Donnachie wrote the following on 2/20/07 4:22 PM:
Benjamin Donnachie wrote:
I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Benjamin Donnachie wrote the following on 2/17/07 2:35 AM:
[...]
Thanks as always to Charly for this patience. Thanks to Werner and his
team for such a great product, and thanks to the macgpg team for getting
me started! :-)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Benjamin Donnachie wrote the following on 2/17/07 1:01 PM:
Benjamin Donnachie wrote:
I'll throw together a friendlier GUI fronted install
package this afternoon and will make an announcement
when it's ready.
It was quicker than I thought...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Benjamin Donnachie wrote the following on 2/17/07 1:29 PM:
[...]
What happens if you use gpg2 for signing etc?
1. In Thunderbird, changed the executable path (typed in
/usr/local/bin/gpg2), quit TB, launch TB, everything works fine.
2. I still
pete wrote the following on 2/15/07 11:28 PM:
[...]
I played around for a while, and found a fix for this. The top of the
message looks like this:
-BEGIN PGP MESSAGE-
Version: PGP Desktop 9.5.2 (Build 4075) - not licensed for commercial use:
www.pgp.com
PGP Desktop adds a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Werner Koch wrote the following on 2/2/07 4:36 AM:
| Hello!
|
| We are pleased to announce the availability of a new stable GnuPG-2
| release: Version 2.0.2
[...]
| Thanks
| ==
|
| We have to thank all the people who helped with this release, be
snowcrash+gnupg-users wrote the following on 1/23/07 8:03 PM:
i'm building pinentry (v0.7.2 ** svn/r153) on OSX.
on the way to gpg2, i've built as prereqs,
libassuan svn/r234
libksba svn/r266
libgpg-error v1.5
libgrcyppt v1.2.3
pth v2.0.7
[snip]
Could this help?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Smits wrote the following on 12/22/06 1:44 AM:
I'm using the KGpg that comes with Suse 10.1. I use the KDE desktop and hence
Kmail to send my email.
When I sign a message with my personal key, when it leaves my outbox the
message is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ludwig Hügelschäfer wrote the following on 12/9/06 10:32 AM:
Hi,
David Shaw wrote on 08.12.2006 14:53 Uhr:
On Fri, Dec 08, 2006 at 11:49:18AM +0100, Michael Bienia wrote:
On 2006-12-08 02:08:37 -0500, Charly Avital wrote:
1. Patch applied
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doug Barton wrote the following on 12/8/06 4:04 AM:
Charly Avital wrote:
Further to my previous posting, I applied the patch to a fresh copy of
2.0.1, and tried ./configure --disable.nls
Did you do that exactly, or did you really try
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Doug Barton wrote the following on 12/8/06 4:04 AM:
Charly Avital wrote:
Further to my previous posting, I applied the patch to a fresh copy of
2.0.1, and tried ./configure --disable.nls
Did you do that exactly, or did you really try
Michael Bienia wrote the following on 12/8/06 5:49 AM:
On 2006-12-08 02:08:37 -0500, Charly Avital wrote:
1. Patch applied:
- --
$ cd /Users/shavital/Desktop/gnupg-2.0.1/
Charly-Avitals-PBG4:~/Desktop/gnupg-2.0.1 shavital$ patch -p0
/Users/shavital/Desktop/gnupg-2.0-osx-iconv.patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Shaw wrote the following on 12/7/06 5:48 PM:
On Thu, Dec 07, 2006 at 10:21:18AM +0100, Werner Koch wrote:
On Wed, 6 Dec 2006 08:23, [EMAIL PROTECTED] said:
-
/usr/bin/ld: Undefined symbols:
_libiconv
Well, you need a proper iconv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Shaw wrote the following on 12/7/06 5:48 PM:
On Thu, Dec 07, 2006 at 10:21:18AM +0100, Werner Koch wrote:
On Wed, 6 Dec 2006 08:23, [EMAIL PROTECTED] said:
-
/usr/bin/ld: Undefined symbols:
_libiconv
Well, you need a proper iconv
Randy Burns wrote the following on 12/5/06 9:01 PM:
It's a great idea. A more direct link is:
https://www.fsf.org/associate/support_freedom/donate
Randy
--- Robert J. Hansen [EMAIL PROTECTED] wrote:
[...]
This year, I'm giving $10 to the Free Software Foundation
(http://www.fsf.org) in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Todd Zullinger wrote the following on 12/6/06 11:37 PM:
I was updating my system to 1.4.6 today and noticed the following in
the make install output (I've got 2.0.1 installed already):
install-info: menu item `gpg' already exists, for file
Werner Koch wrote the following on 12/5/06 3:10 PM:
On Tue, 5 Dec 2006 18:45, [EMAIL PROTECTED] said:
I am having a problem with configure. It doesn't recognise that I have
these libraries already installed (which I do, and all the latest versions).
I'm using OSX 10.4.8...
You need to
Werner,
My version of libtool is
Apple Computer, Inc. version cctools-622.5
Sorry for the omission,
Charly
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Shaw wrote the following on 11/29/06 10:21 PM:
We are pleased to announce the availability of the first release
candidate for the forthcoming 1.4.6 version of GnuPG:
ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.4.6rc1.tar.bz2 (3.0M)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
1. Apple's Powerbook G4 1.33GHz, MacOSX 10.4.8, gpg 1.4.5, gpg2 (with
gpg-agent) 1.9.20, card reader SCR243, OpenPGPCard.
2. Public key URL
http://homepage.mac.com/shavital/iblog/B788933981/C1591872826/E20061125110933/index.html
3. This is a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
1. Apple Powerbook G4 1.33GHz, MacOSX 10.4.8, GnuPG 1.4.5, gpg2 1.9.20
(with gpg-agent), Card Reader SCR243 PCMCIA, OpenPGP Card.
2. Key on card:
http://homepage.mac.com/shavital/iblog/B788933981/C1591872826/E20061125110933/index.html
3. This
Sorry for the double post. The first e-mail was reported not sent (smtp
failure), disappeared from TB's list.
Thanks John.
Charly
John W. Moore III wrote the following on 11/25/06 3:02 PM:
[...]
Again, Good Sig!
JOHN ;)
Timestamp: Saturday 25 Nov 2006, 15:02 --500 (Eastern Standard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I can use tsign in the command line. It is included in the
Command
prompt, after you use --edit-key.
Charly
Running gpg 1.4.5 compiled from source code, for Macintosh OS 10.4.7
Laurent Jumet wrote the following on 8/27/06 11:06 AM:
Hello !
Hi,
I have received your post on this subject four times: the three first
versions were identical, the fourth one (quoted hereafter) is different
both in Subject and contents (you have added an EDIT paragraph).
I am checking my own POP settings, to find out whether something is
wrong with them,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
1. Was the person to whom you sent a signed e-mail able to verify your
signature, and if she verified it, what was the result?
2. I *guess* that your correspondent, when she answered to your message,
quoted it in full, including your signature. The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Compiled for PPC MacOS 10.4.7 with IDEA.
Runs fine.
Thanks.
Charly
Werner Koch wrote the following on 8/1/06 11:37 AM:
Hello!
We are pleased to announce the availability of a new stable GnuPG
release: Version 1.4.5
This is maintenance
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
1. Compiled on PPC with 'cp idea.c cipher'. Running fine.
2. Compiled on PPC without 'cp idea.c cipher', on a gnupg system where
$ gcc -Wall -O2 -fPIC -dynamiclib -o idea idea.c
which requires to have 'load-extension idea' enabled in gpg.conf.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ben,
although I had already compiled 1.4.4 from src, I thank you for your
contribution to MacGPG users.
As well as for your gpg2 package.
Charly
Benjamin Donnachie wrote the following on 7/18/06 3:46 PM:
As macgpg hasn't been updated yet,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Compiled from source with idea.c, under MacOS 10.4.6, configured for
Darwin (powerpc-apple-darwin8.6.0)
Thanks to the GnuPG Team.
Charly
Werner Koch wrote the following on 6/25/06 9:43 AM:
Hello!
We are pleased to announce the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Zach Himsel wrote the following on 6/7/06 5:45 AM:
Janusz A. Urbanowicz wrote:
[...]
| Is there anything I have missed in spec or in gnupg to forbid this?
|
| read about eyes only option in gpg
|
| alex
Eyes Only?
Aka 'Secure viewer'.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Zach Himsel wrote the following on 6/5/06 7:09 PM:
Hello,
I am using Thunderbird with the Enigmail extension. It gets annoying
to me to have to enter in my password every time I want to send a
signed (every email) or encrypted (only some) email.
Who encrypted the file, for whom, using what system?
Is it a text e-mail, or a stand-alone file?
If it is an encrypted text e-mail, can you post the actual encrypted
file? If not, can you URL a location where the actual file could be viewed?
I am not familiar with your system (I am a Mac user);
As I wrote in a separate e-mail, no luck yet.
Take care,
Charly
Benjamin Donnachie wrote on 5/3/06 10:13 AM:
Charly Avital wrote:
I very much doubt I'll be able to do what you did. I'll try.
If I don't succeed, I'll e-mail you again a week or so from now,
thanking you in advance for your
2:02 PM:
Charly Avital wrote:
New to this list. Running Mac OSX 10.4.6 (Darwin 8.6.0), gpg 1.4.3.
Installed gpg-agent 1.9.10 using darwin.ports following the instructions
contained in url: http://gpg-agent.darwinports.com/.
After much fuss, I recently persuaded gpg-agent v1.9.20 to compile
I could verify the signature as Good.
Charly
Robert Smits wrote the following on 4/25/06 6:22 PM:
On Friday 21 April 2006 03:21, you wrote:
A 'bad signature' can be caused by many different factors, one frequent
cause being a text wrap problem.
When a message is not only signed but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
New to this list. Running Mac OSX 10.4.6 (Darwin 8.6.0), gpg 1.4.3.
Installed gpg-agent 1.9.10 using darwin.ports following the instructions
contained in url: http://gpg-agent.darwinports.com/.
Upon completion of installation of all required
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A 'bad signature' can be caused by many different factors, one frequent
cause being a text wrap problem.
When a message is not only signed but encrypted+signed, the encryption
process *might* write off the cause of a bad signature.
You might try
, Apr 05, 2006 at 06:07:18PM -0400, Charly Avital wrote:
I have chosen to quit without saving any changes, because the truth is I
do not fully understand what the change is, and what it would do to my
key and/or to my signing subkey.
http://www.gnupg.org/faq/subkey-cross-certify.html
You should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks to the patches posted by Remco Post in this forum, for libksba
and gnupg 1.9.20, I could have the latter configured for:
Platform: Darwin (powerpc-apple-darwin8.5.0)
OpenPGP: no
S/MIME:yes
Agent: yes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Compiled from source and installed under MacOS X 10.4.5 Darwin
(powerpc-apple-darwin8.5.0)
Thanks to the Team.
Charly
Thanks
Werner Koch wrote the following on 4/3/06 8:13 AM:
Hello!
We are pleased to announce the availability of a new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Option 2 is better, IMO.
I don't think you can create a new uid *without* an e-mail address,
unless you present it (when going through the generation's prompts) as
something that looks like an e-mail address, e.g.
[EMAIL PROTECTED], of whatever you
Not really 2¢. More like 2M.
Thanks, I didn't know about that option (from the man pages):
--allow-freeform-uid
Disable all checks on the form of the user ID while generating a new
one. This option should only be used in very special environments as it
does not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks for the information. I have never succeeded to build gpg 1.9.xx
on MacOS, in spite of help and tips from WK, so I gave it up.
If you are kind enough to keep posting your findings and tips, I shall
be very grateful.
Charly
MacOS 10.4.5 -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Running Thunderbird version 1.5 (20051201) + enigmail 0.94.0, Macintosh
OSX 10.4.4, GnuPG 1.4.2.
When I received Daniel's message, TB+Enigmail indicated, in a colored
strip over the message's text click the Decrypt icon to import key (I
don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Henk M. de Bruijn wrote the following on 9/6/05 8:48 AM:
| Hi all,
|
| Forgive my ignorance but how do I select a subkey?
|
| TIA
I take it that you mean an additional subkey.
$ gpg --edit-key [key ID]
Command addkey
Key is protected.
You need a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
From man gpg:
To revoke a subkey or a signature, use the --edit command.
Provided you didn't sign that key using the nrsign command, you can
still revoke your own signature.
It could look like this:
$ gpg --edit-key [key ID]
Command revsign
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
From man gpg:
To revoke a subkey or a signature, use the --edit command.
Provided you didn't sign that key using the nrsign command, you can
still revoke your own signature.
It could look like this:
$ gpg --edit-key [key ID]
Command revsign
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
compiled for Darwin 8.2.0, with idea.c, libcurl (afer applying the
patch to g10/keyserver.c).
Thank you for your work.
Charly
Werner Koch wrote the following on 7/27/05 3:53 AM:
Hello!
We are pleased to announce the availability of a
Upload the revocation certificates to a keyserver. They will be
disseminated to other keyservers automatically.
Charly
Graham wrote the following on 7/10/05 7:22 AM:
Recently I generated some keypairs with their relevant revocation
certificates, but was not able to save my new keyrings
On Jul 7, 2005, at 12:29 PM, [EMAIL PROTECTED] wrote:
Can you please verify that there are no issues with the FTP Server at
gnupg.org. I am trying to download the 1.4.1 code, but am unable
to get
through. I am unsure if I am being blocked, or if it is an issue
with the
FTP server. Any
Hiamal wrote the following on 7/6/05 9:00 AM:
I'm a litle bit confused about two different messages, one from gnupg
1.4.1(Debian sid) an one from PGPfreeware 6.5.3(Win) for the same
e-mail.
gnupg gpg: BAD signature from .
pgp *** Status: Good Signature from Invalid Key
It
Werner Koch wrote the following on 6/29/05 10:36 AM:
On Wed, 29 Jun 2005 10:55:02 +0200, Janusz A Urbanowicz said:
Some form of secure viewer was present in PGP 2.3 and 2.6 which were FLOSS.
Huh, that's new to me. Both versions are pure command line tools
without a graphical part. No
I have grown tired to receive out office notifications from
[EMAIL PROTECTED] everytime I post to the list.
That address is now on my junk list.
Charly
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
While carrying out some tests with GnuPG and the options
--for-our-eyes-only and --output [filename], within the macgpg-users list,
I tried to decrypt a test message composed with MacGPG (GnuPG for the Mac)
1.4.2rc2 configured with these two options.
The received message could be decrypted
On Jun 26, 2005, at 5:15 PM, Tom McCune wrote:
[...]
I don't know about Macs, but on Windows, the option is there when
using
Current Window usage from PGPtray.
I have found how to do it, it requires to force PGP to display the
window where encryption key(s) can be selected manually to
According to man gpg:
---
Set the `for your eyes only' flag in the message. This
causes GnuPG to refuse to save the file unless the --output
option is given, and PGP to use the secure viewer with a
Tempest-resistant font to display the message. This option
overrides
[EMAIL PROTECTED] wrote the following on 6/20/05 8:13 AM:
Hi
I have a key where the sub key has expired
Is there a way to extend the validity of the *sub key* using GPG command
line interface
p.s. - As of now I am little hesitant to set up GPG shell etc - learn
these and then do the
On Jun 10, 2005, at 10:13 AM, Julian Kramer wrote:
--
Is GnuPGP compatible with Eudora and Apple Mail?
For Eudora see http://mywebpages.comcast.net/chang/EudoraGPG/
index.html
For Apple.mail see http://www.sente.ch/software/GPGMail/
English.lproj/GPGMail.html .
There are different
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
configured 1.4.2rc1 with --with-libcurl on Powerbook CPU PowerPC G4
(1.1), under Mac OS X 10.4.1 (code named Tiger), Darwin (powerpc-
apple-darwin8.1.0), including idea.c.
No problems while compiling. Running fine.
MacGPG (GnuPG for the
201 - 271 of 271 matches
Mail list logo
