-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 the po/gnupg.pot file, copy it to
po/en.po, transla
Josef Wolf wrote:
> Don't most unices have /dev/random nowadays? I never planned to run
> this thing on a windows box :)
GnuPG has been ported to many platforms. BeOS, OpenVMS, Win32, and many
more that have no /dev/random.
> Hmm, the only drawback I see is a slowdown. The application will
> j
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I switched from XP to Ubuntu 6.06, now the SCR338 cardreader built into
the keyboard doesn't work.
~$ gpg --card-status
gpg: selecting openpgp failed: ec=6.108
gpg: OpenPGP card not available: general error
lsusb reports:
Bus 004 Device 001: ID
On Mon, Sep 11, 2006 at 03:27:59PM -0500, Robert J. Hansen wrote:
> Josef Wolf wrote:
> 1. /dev/random isn't available on all platforms. GnuPG's random number
> generator is.
Don't most unices have /dev/random nowadays? I never planned to run this
thing on a windows box :)
> 2. /dev/rand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Josef Wolf wrote:
> I wondered why /dev/random is not used.
A few reasons, any one of which would be sufficient.
1. /dev/random isn't available on all platforms. GnuPG's random number
generator is.
2. /dev/random is exhaustible. This is a Bad
Thanks for your response, Robert!
On Sun, Sep 10, 2006 at 05:36:33PM -0500, Robert J. Hansen wrote:
> Josef Wolf wrote:
> > 1. It locks the keyring. --lock-never will avoid this. Is it safe
> > to use --lock-never as long as it is guaranteed that _only_ "gpg -e"
> > is ever run? No ke
Hi.
I am having a problem with my smartcard. I am running Suse 10.1 and my
card has worked previously under Suse 10.0. Here is my debug log. Can
anybody give me an advice?
Cheers! Kai
gpg: DBG: ccid-driver: using CCID reader 0 (ID=04E6:5115:21120617208494:0)
gpg: DBG: ccid-driver: idVendor: 04E6
On Fri, 8 Sep 2006 19:33, Werner Koch <[EMAIL PROTECTED]> said:
> It is possible that the iconv detection does not work.
> And yes, we are falling back to an internal iconv replacement.
> Look into util/strgutil.c:
> You might want to just add a line
>|| !ascii_strcasecmp (newset, "885
On Mon, 11 Sep 2006 00:16, Josef Wolf said:
> 1. It locks the keyring. --lock-never will avoid this. Is it safe
> to use --lock-never as long as it is guaranteed that _only_ "gpg -e"
If the keyrings are read-only, there is no need for locking. Thus
--lock-never is safe.
> 2. There's the
