Jason Harris wrote:
> [...]Also, while the GD itself doesn't retain its past sigs, elsewhere
> one can see that 0xB56165AA was signed by 0xCA57AD7C starting on
^^
> 2004-12-29 while 0x99242560 was signed by it starting 2004-12-08.
Hey, stop picking on me! :)
(darren)
--
On Thu, Mar 17, 2005 at 11:18:26PM -0500, Jason Harris wrote:
> On Thu, Mar 17, 2005 at 05:31:41PM -0500, David Shaw wrote:
> > On Thu, Mar 17, 2005 at 05:10:31PM -0500, Jason Harris wrote:
>
> > > It was my impression that expired sigs would be retained by default.
> > > Removing expired sigs is
On Thu, Mar 17, 2005 at 05:31:41PM -0500, David Shaw wrote:
> On Thu, Mar 17, 2005 at 05:10:31PM -0500, Jason Harris wrote:
> > It was my impression that expired sigs would be retained by default.
> > Removing expired sigs is tantamount to removing expired/revoked
> > userids and subkeys, IMO, and
On Thu, Mar 17, 2005 at 05:10:31PM -0500, Jason Harris wrote:
> On Thu, Mar 17, 2005 at 04:15:29PM -0500, David Shaw wrote:
> > On Thu, Mar 17, 2005 at 03:55:23PM -0500, Jason Harris wrote:
> > > On Tue, Mar 15, 2005 at 06:22:11PM +0100, Werner Koch wrote:
>
> > > > I forgot to insert the NEWS for
On Thu Mar 17 2005; 15:22, Anonymous wrote:
> winptee: This is a collection of gpg utilities, unfortunatly the explorer
> extentions (context menu) do not appear to be open source.
All parts of WinPTEE are free software (GPL). But WinPTEE is obsolete and
should not be used anymore. The successor
On Thu, Mar 17, 2005 at 04:15:29PM -0500, David Shaw wrote:
> On Thu, Mar 17, 2005 at 03:55:23PM -0500, Jason Harris wrote:
> > On Tue, Mar 15, 2005 at 06:22:11PM +0100, Werner Koch wrote:
> > > I forgot to insert the NEWS for 1.4.1; there are actually not that
> > > many as those for the last rel
Rusty Shackleford wrote:
>Is this feature possible with GPG?
This isn't portable: on what OS do you want these executables to create, and
on which OS to run? A typical windows-only option that will probably never
be supported.
--
ir. J.C.A. Wevers // Physics and science fiction site:
[
On Thu, Mar 17, 2005 at 04:09:41PM -0500, Rusty Shackleford wrote:
> My office uses PGP to create self-extracting executable files.
>
> I found the -c option for GPG which encrypts with a symmetric key, but
> this doesn't seem to do the next step of making the encrypted data an
> executable progra
On Thu, Mar 17, 2005 at 03:55:23PM -0500, Jason Harris wrote:
> On Tue, Mar 15, 2005 at 06:22:11PM +0100, Werner Koch wrote:
>
> > I forgot to insert the NEWS for 1.4.1; there are actually not that
> > many as those for the last release. Here we go:
>
> > * New "import-unusable-sigs" and "expo
My office uses PGP to create self-extracting executable files.
I found the -c option for GPG which encrypts with a symmetric key, but
this doesn't seem to do the next step of making the encrypted data an
executable program that prompts for a password.
Is this feature possible with GPG? I'm tryin
winptee: This is a collection of gpg utilities, unfortunatly the explorer
extentions (context menu) do not appear to be open source.
winfpse: This is just the name for winPT's explorer extentions (context
menu).
gpgsx: This is open source (GPL) and is witten in delphi, but unfortunately
the pa
On Tue, Mar 15, 2005 at 06:22:11PM +0100, Werner Koch wrote:
> I forgot to insert the NEWS for 1.4.1; there are actually not that
> many as those for the last release. Here we go:
> * New "import-unusable-sigs" and "export-unusable-sigs" tags for
>--import-options and --export-options. Th
You, Kurt Fitzner, wrote:
>I am looking for the source code - any source code old or new - for
>winptee, winfpse, or gpgsx. Those are all Windows shell extension
>projects that add context menu support for GnuPG in windows.
If you mean WinPT, the source can be found at http://www.winpt.org/
--
* Grimes, Dean [2005/03/17 12:31]:
> My problem is that libz on some of the remote systems is not current. I'm
> compiling on the development server with 1.1.4 now and some of the older
> remote systems have 1.1.3. I guess I have some recompiling to do to bring
> all of the remote systems up-to-da
My problem is that libz on some of the remote systems is not current. I'm
compiling on the development server with 1.1.4 now and some of the older
remote systems have 1.1.3. I guess I have some recompiling to do to bring
all of the remote systems up-to-date.
Thanks,
Dean
-Original Message---
* On 2005.03.17, in <[EMAIL PROTECTED]>,
* "Grimes, Dean" <[EMAIL PROTECTED]> wrote:
>
> I have successfully compiled and installed gnupg-1.4.1 on SCO OpenServer and
> everything works great. However, I have approximately 500 remote servers I
> need to install it on. I tried tarring up all o
Hi,
I have successfully compiled and installed gnupg-1.4.1 on SCO OpenServer and
everything works great. However, I have approximately 500 remote servers I
need to install it on. I tried tarring up all of the installed binaries and
associated directories and installing it on one of the remote serv
On Thu, 17 Mar 2005, Zuxy wrote:
Either under edit-key or directly from the command line? I've tried
edit-key, key N, fpr but it still showed the primary key's fingerprint.
$ gpg --fingerprint --fingerprint {keyid}
--
...atom
__
On Thu, 17 Mar 2005 21:49:55 +0900, Kory T said:
> I remember reading about GnuPG supporting PKSC#15 (ISO7816-15)
GnuPG 1.9 has support for S/MIME (i.e.X.509). However this requires
OpenSC which has several drawbacks. However I have a new pkcs#15
module in the works which will be lean implement
Either under edit-key or directly from the command line? I've tried
edit-key, key N, fpr but it still showed the primary key's
fingerprint.
--
Zuxy
Beauty is truth,
While truth is beauty.
PGP KeyID: E8555ED6
___
Gnupg-users mailing list
Gnupg-users@gnu
On Wed, Mar 16, 2005 at 08:59:34PM -0800, Melissa Reese wrote:
> Hi David,
>
> On Wednesday, March 16, 2005, at 8:49:01 PM PST, you wrote:
>
> > It means that you have "--trust-model always" set. GnuPG is warning
> > you that it isn't checking trust.
>
> Thanks! I'll remove that option from my c
I remember reading about GnuPG supporting PKSC#15 (ISO7816-15)
compatible cards for the smartcard support. I know currently only the
OpenPGP Card is supported, but does anyone know if PKSC#15 support is
what the developers are still thinking about for future version of gpg?
Kory
PGP.sig
Desc
22 matches
Mail list logo
