Peter Palfrader schrieb:
> http://asteria.noreply.org/~weasel/PGPKeyserverSchema.zip
Thanks! One question, though: Where is this schema from?
Is it the "new" one the GnuPG announcement was talking about or
is it a schema shipped with with a commercial(?) keyserver?
> If you get an LDAP keyserver
Hello,
I need to sign files remotely. They're moderately large, so transmitting
them back to my firewalled-off laptop (I'm usually behind a slow line),
where the secret key lives, isn't a good idea.
Ideas?
--
Matthias Urlichs
___
Gnupg-users mailin
David Shaw wrote:
> On Sun, Feb 19, 2006 at 04:42:19PM +1030, Alphax wrote:
>
>>David Shaw wrote:
>>
>>>On Sun, Feb 19, 2006 at 04:09:32PM +1030, Alphax wrote:
>>>
>>>
Under GPG 1.4.3rc1 I'm completely unable to get the cURL-type keyserver
handlers to function correctly. For example, using
On Sun, Feb 19, 2006 at 11:24:40PM +1030, Alphax wrote:
> Host: sks.keyserver.penguin.de
> Command:SEARCH
> gpgkeys: HTTP URL is
> `http://sks.keyserver.penguin.de:11371/pks/lookup?op=index&options=mr
> &search=Alphax'
> ?: localhost: Unable to connect: ec=0
> gpgkeys: HTTP searc
David Shaw wrote:
> On Sun, Feb 19, 2006 at 11:24:40PM +1030, Alphax wrote:
>
>
>>Host: sks.keyserver.penguin.de
>>Command:SEARCH
>>gpgkeys: HTTP URL is
>>`http://sks.keyserver.penguin.de:11371/pks/lookup?op=index&options=mr
>>&search=Alphax'
>>?: localhost: Unable to connect: e
On Mon, Feb 20, 2006 at 01:52:40AM +1030, Alphax wrote:
> David Shaw wrote:
> > On Sun, Feb 19, 2006 at 11:24:40PM +1030, Alphax wrote:
> >
> >
> >>Host: sks.keyserver.penguin.de
> >>Command:SEARCH
> >>gpgkeys: HTTP URL is
> >>`http://sks.keyserver.penguin.de:11371/pks/lookup?op
Seeing as a detached sig is just a signed hash, you could hash the
file remotely then copy the hash over and construct a detached sig
from that. I imagine no current app supports that kind of thing(??) so
that might involve X amount of pissing about coding your own solution.
Many folk just run sha
On Sun, Feb 19, 2006 at 06:07:56AM +0100, Matthias Urlichs wrote:
> Hello,
>
> I need to sign files remotely. They're moderately large, so transmitting
> them back to my firewalled-off laptop (I'm usually behind a slow line),
> where the secret key lives, isn't a good idea.
create (and rotate fre
On Sun, Feb 19, 2006 at 06:07:56AM +0100, Matthias Urlichs wrote:
> Hello,
>
> I need to sign files remotely. They're moderately large, so transmitting
> them back to my firewalled-off laptop (I'm usually behind a slow line),
> where the secret key lives, isn't a good idea.
You have two good opti
Henry Hertz Hobbit wrote:
>Usually, if you are using a web interface to access your email, only the
>initial authentication is done via SSL. After that if your URL address
>shifts to using an "http://"; rather than the "https://"; you made your
>initial connection with means that your communicati
On Sunday 19 February 2006 01:14, [EMAIL PROTECTED] wrote:
> On Sat, Feb 18, 2006 at 12:33:03AM +0200, Alon Bar-Lev wrote:
> > I still don't understand why you use PKCS#1, PKCS#8, X.509, CMC,
> > S/MIME and more... Why don't you invent some replacements for these
> > too?
>
> Big news for you: We
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I have a key on an official Austrian banking card (the operating system of the
card is ACOS, the company that provides the keys is a-trust). How can I use
this card with my Reiner SCT CyberJack card reader to sign mails using gnupg?
The card
Reinhold Kainhofer wrote:
> Hi all,
> I have a key on an official Austrian banking card (the operating system of the
> card is ACOS, the company that provides the keys is a-trust). How can I use
> this card with my Reiner SCT CyberJack card reader to sign mails using gnupg?
>
> The card's OS is pr
Matthias Urlichs wrote:
> I need to sign files remotely. They're moderately large
> Ideas?
Use md5sum|sha1sum|[...] and sign the resulting file.
Ciao, Bjørn
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinf
Johan Wevers wrote:
> Henry Hertz Hobbit wrote:
>
>>Usually, if you are using a web interface to access your email, only the
>>initial authentication is done via SSL. After that if your URL address
>>shifts to using an "http://"; rather than the "https://"; you made your
>>initial connection with
David Shaw wrote:
> On Mon, Feb 20, 2006 at 01:52:40AM +1030, Alphax wrote:
>
>>David Shaw wrote:
>>
>>>That looks correct so far. I don't suppose you have an environment
>>>variable http_proxy set?
>>>
>>
>>Yes, but I thought that --no-options would disable it... also, I've
>>tried using an opti
On Sun, Feb 19, 2006 at 02:54:13PM -0500, Nicholas Sushkin wrote:
> On Sunday 19 February 2006 01:14, [EMAIL PROTECTED] wrote:
>> On Sat, Feb 18, 2006 at 12:33:03AM +0200, Alon Bar-Lev wrote:
>>> I still don't understand why you use PKCS#1, PKCS#8, X.509, CMC,
>>> S/MIME and more... Why don't you
On Sat, Feb 18, 2006 at 07:25:46AM +0100, Lionel Elie Mamane wrote:
> On Sat, Feb 18, 2006 at 12:33:03AM +0200, Alon Bar-Lev wrote:
>> I still don't understand why you use PKCS#1, PKCS#8, X.509, CMC,
>> S/MIME and more... Why don't you invent some replacements for these
>> too?
> Big news for you
John Clizbe wrote:
Henry Hertz Hobbit wrote:
Usually, if you are using a web interface to access your email,
only the
initial authentication is done via SSL. After that if your URL
address
shifts to using an "http://"; rather than the "https://"; you made
your
initial connection with mea
Benjamin Esham wrote on 20.02.2006 7:50:
> John Clizbe wrote:
>> Earthlink and Google's GMail use https on their signin page then then
>> switch
>> over to http once authenticated
>
> I saw a neat trick somewhere online... if you use
> "https://mail.google.com"; as your
> login page for Gmail, the
20 matches
Mail list logo
