On 10/16/06, Mica Mijatovic <[EMAIL PROTECTED]> wrote:
RFCs are not any "standards" nor they are by (their own) definition
supposed to be.
They are just collection of less or more recommended routines, and often
also nothing but the lists of (most usual/mass) _habits_.
Many RFCs *are* standar
On Mon, 16 Oct 2006 17:56, Peter Lebbing said:
> Is the implementation of the current OpenPGP Card open source? If so,
> how can I obtain the source?
Sorry, that is not possible due to the strict NDAs you have to sign
with the chip vendors. Unless we can impleemnt it on a free and
reasonable pri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is the implementation of the current OpenPGP Card open source? If so,
how can I obtain the source?
I'm just interested in seeing how it is done, I don't plan to use it for
any practical purposes.
Thanks,
Peter Lebbing.
-BEGIN PGP SIGNATURE-
-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
Julia Dashkevich wrote:
> no tool for uninstalling my current version separately
> from gpg4win. What are the steps for updating winpt
> to the newer version and can it be done without
> affecting the current gpg installation?
Just unzip the ZIP archive and overwrite the ptd.dll
and the winpt.d
On Sat, Oct 14, 2006 at 03:21:42AM -0600, Henry Hertz Hobbit wrote:
> [8] IMPORT somebody ELSE'S key and sign it; Werner's signing
> key for example.
> $ cd $TO_WHERE_WERNERS_PUB_KEY_IS
> $ sha1sum WernerKoch.asc
> c151479c9231455f18bccd09e3423679683a9ba9 WernerKoch.asc
> # It
Hi,
first of all thanks for your answers. I gave up my lib-directory for the
dll's and copied them to the root of gpg.exe. But honestly I'm still
confused, because it worked using version 1.4.3. That's why I thought it
could be a bug in the new version.
Bye
--
View this message in context:
htt
