Re: gen-key non-interactively

> I strongly advise against using expect to generate keys. Your expect > script will break when we change the text that GPG displays. If you > want to generate keys unattended, then use the --batch --gen-key > interface. i clearly understand that, and will manage my script(s) accordingly. thanks

Re: gen-key non-interactively

here's an "expect"-based function i use in a bash script for just such purpose, # function: "DO_GENKEY_SESSION" # auto-execute a GPG --gen-key session # usage: # DO_GENKEY_SESSION (SELECTION) $NOTATION $COMMENT # gen-key dialog options (SELECTION):

Re: 'sensitive' designated revoker -- are the keyservers still aware?

> When exporting a key that has a sensitive designated > revoker set, the key is exported, but the designated revoker > information is not included. Anyone looking at the key from the > outside cannot tell the difference between this state, and no > designated revoker set at all. However, if the

'sensitive' designated revoker -- are the keyservers still aware?

if i've added a designated revoker to a key, WITH the 'sensitive' flag. am i correct that: (1) the 'sensitive' flag prevents the *export* of the add'l/designated revoker's key (2) the keyservers still learn/know that there IS a designated revoker, AND its KeyID/UID ? thanks. __

Re: explain nrsign & lsign?

john, david, thanks for the clarifications. > Can you explain what you're trying to do? that never hurts, does it. i want to have a 'master' trust key that, e.g., is owned/controlled by my company, -- with strongest-possible, highest-performance encryption (RSA? yes, i know this is a religio

Re: explain nrsign & lsign?

> There is somewhat constant debate over the best method. ... > the main point of signing a key is so that GnuPG (or PGP) can > use the signature in its trust calculations ... good info. thanks. last (yeah, sure ...) question, then. does gpg, &/or do the keyservers, require *valid* email addres

Re: explain nrsign & lsign?

> YES, this would do it; ok. thanks. > however, proper etiquette would be to *not* send > B's Key to the Servers, but rather to returned it 'Signed' to B and let > B make any 'publication' decisions/actions. understood. > There are folks who are > _very_ picky about their Keys being in General

Re: explain nrsign & lsign?

> > e.g., if i lsign "B" with "A", *which* key, then is made > > non-exportable? "A" or "B"? > > Neither key is made non-exportable. A local signature just means the > *signature* is local. nice & clear. thanks. > So if you lsigned B with A, then exported B (or > sent it to a keyserver), the l

Re: explain nrsign & lsign?

hi, > > e.g., if i lsign "B" with "A", *which* key, then is made > > non-exportable? "A" or "B"? > Neither. The *key* is still exportable. it is the signature that is local and > not exported. aha. a not-so-subtle distinction :-/ thanks! > You use a local signature when you wish to sign a UID

explain nrsign & lsign?

hi, i've a 'master', high-strength signing key, "A". i'm using it to tsign another key, "B". i note i can also nrsign(non-revocable)/lsign(non-exportable) "B" with "A". can someone please clearly explain the consequences of doing so? e.g., if i lsign "B" with "A", *which* key, then is made non

Re: [snowcrash+gnupg-users] pinentry-qt (svn/r153) crashes on exec @ "assuan_register_command"; v0.7.2 execs no error.

> but in Console, i see: > > pinentry-qt: invalid option -- p > pinentry-qt: invalid option -- s > pinentry-qt: invalid option -- n > pinentry-qt: invalid option -- _ > pinentry-qt: invalid option -- 0 > pinentry-qt: invalid option -- _ > pine

Re: [snowcrash+gnupg-users] pinentry-qt (svn/r153) crashes on exec @ "assuan_register_command"; v0.7.2 execs no error.

hi, > Thanks for researching this, please keep us posted if you find > something. there's already more in a subsequent post ... step-by-step, i suppose :-) > Works fine here: > > ./configure --prefix=/home/marcus/pinentry > make install hrm. something's wrong here, then ... will dig some moer.

Re: [snowcrash+gnupg-users] pinentry-qt (svn/r153) crashes on exec @ "assuan_register_command"; v0.7.2 execs no error.

fyi, i found/reproduced the problem with the BusError. it's an artifact of my (failed) attempt(s) to link in _my_ external/local libassuan. namely, if i setenv LDFLAGS "-L/usr/local/lib -lassuan -lncurses -lintl -liconv -F/System/Library/Frameworks -framework Carbon -framework QuickTime -lpng

Re: [snowcrash+gnupg-users] pinentry-qt (svn/r153) crashes on exec @ "assuan_register_command"; v0.7.2 execs no error.

hi marcus, On 1/24/07, Marcus Brinkmann <[EMAIL PROTECTED]> wrote: > thanks for the report. hi, well, for the life of me, i do NOT know what's changed (i've been building/rebuilding a lot!), but, atm, both pinentry-qt-svn pinentry-qt-v072 seem to launch correctly, and w/o BusE

Re: pinentry-qt (svn/r153) crashes on exec @ "assuan_register_command"; v0.7.2 execs no error.

> Could this help? > heh, not really. that's where i _started_ -- been all through those pages. afaict, nothing addresses the 'assuan' problem apparent i'm seeing in the svn src-build, but lacking in the v0.7.2 build, which is ok (mostly ...

pinentry-qt (svn/r153) crashes on exec @ "assuan_register_command"; v0.7.2 execs no error.

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 building each as, ./configure \ --with-prefix=/usr/local \ --enable-shared --enable-static \ --disable-rpath

Re: installed pinentry not found by gpg-agent/gpg2

hi, > Does pinentry-qt work at all? Try to start pinentry-qt from the command > line, and if it starts type the following lines on the prompt: > > SETDESC This is a test > GETPIN here's what i see, % pinentry-qt OK Your orders please SETDESC This is a test GETPIN OK

Re: installed pinentry not found by gpg-agent/gpg2

hi, does it really need to be in /usr/bin? as above, i've installed it purposefully in % ls -al `which pinentry-qt` -rwxr-xr-x 1 root admin 2245584 2007-01-21 11:29 /usr/local/bin/pinentry-qt and, the symlink to it already exists, % ls -al `which pinentry` lrwxr-xr-x 1 root admin 11 2007-01-

installed pinentry not found by gpg-agent/gpg2

i've built/installed, % glibtool --version ltmain.sh (GNU libtool 1.2361 2007/01/21 16:15:36) 2.1a % pinentry --version pinentry-qt (pinentry) 0.7.3-cvs % gpg --version gpg (GnuPG) 2.0.2-svn4407 on osx 10.4.8. testing as fol