From 38d9be677ee1928e92b6c914a5467fe9bf8bcd4e Mon Sep 17 00:00:00 2001 From: Jamie McClelland Date: Sun, 3 Aug 2008 16:36:03 -0400 Subject: redirect sample refresh keys cron tab to /dev/null. --- doc/README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/README b/doc/README index bed0380..8d386de 100644 --- a/doc/README +++ b/doc/README @@ -10,7 +10,7 @@ Keeping your keyring up-to-date Regularly refresh your GnuPG keyring from the keyservers. This can be done with a simple cronjob. An example of crontab line to do this is: -0 12 * * * /usr/bin/gpg --refresh-keys +0 12 * * * /usr/bin/gpg --refresh-keys > /dev/null This would refresh your keychain every day at noon. -- cgit v1.2.3 From 09dac2ce10990b98e5cae82e5a52409f1c3a2447 Mon Sep 17 00:00:00 2001 From: Jamie McClelland Date: Tue, 5 Aug 2008 09:51:49 -0400 Subject: adding new feature request for silent option to monkeysphere-ssh-proxycommand. --- ...monkeysphere-ssh-proxycommand-quiet-option.mdwn | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 website/bugs/monkeysphere-ssh-proxycommand-quiet-option.mdwn diff --git a/website/bugs/monkeysphere-ssh-proxycommand-quiet-option.mdwn b/website/bugs/monkeysphere-ssh-proxycommand-quiet-option.mdwn new file mode 100644 index 0000000..170fc7c --- /dev/null +++ b/website/bugs/monkeysphere-ssh-proxycommand-quiet-option.mdwn @@ -0,0 +1,22 @@ +I don't mind the monkeysphere-ssh-proxycommand output on regular connections. + +For me it looks something like this with a server not participatingin the +monkey sphere: + + ms: processing host: chavez.mayfirst.org + ms: - key not found. + +And like this for a server participating: + + ms: processing host: george.riseup.net + ms: primary key found: 7353A74E3B757F8C + ms: * acceptable key found. + ms: known_hosts file updated. + +However, I have some batch scripts that run ssh that also provide output, so the monkeysphere output clutters things up. + +I would really like to either have a -q/--quiet option, or, preferable for me +at least, would be for silent output to be the default and have a -v/--verbose +option to get the output. Or - maybe these should be environmental variables? +In any event - someway to suppress informational output would be a useful +improvement. -- cgit v1.2.3 From ec967faab6f191a33e4a804fc6c913d07d2cf15e Mon Sep 17 00:00:00 2001 From: Jamie McClelland Date: Tue, 5 Aug 2008 12:38:41 -0400 Subject: fixing redrect of /usr/bin/gpg to redirect error as well as standard output to /dev/null for truly quiet output. --- doc/README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/README b/doc/README index 8d386de..2fc2d5f 100644 --- a/doc/README +++ b/doc/README @@ -10,7 +10,7 @@ Keeping your keyring up-to-date Regularly refresh your GnuPG keyring from the keyservers. This can be done with a simple cronjob. An example of crontab line to do this is: -0 12 * * * /usr/bin/gpg --refresh-keys > /dev/null +0 12 * * * /usr/bin/gpg --refresh-keys > /dev/null 2>&1 This would refresh your keychain every day at noon. -- cgit v1.2.3 From 619616567842d79cc960a37f6212f04f80c9100b Mon Sep 17 00:00:00 2001 From: Jamie McClelland Date: Tue, 5 Aug 2008 12:57:29 -0400 Subject: adding directions to pass your key id as the first argument. Also added extra test for people who don't pass anything as the first argument - so the help explanation is shown. --- src/seckey2sshagent | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/seckey2sshagent b/src/seckey2sshagent index 2a98cf1..ecfd7aa 100755 --- a/src/seckey2sshagent +++ b/src/seckey2sshagent @@ -26,6 +26,10 @@ explanation() { echo -n "The basic strategy of seckey2sshagent is to dump your OpenPGP authentication key(s) into your agent. +The first argument to the command should be your gpg key id (the 8 +character hex string; try gpg --list-key your@emailaddress.org to +lookup your key id). + This script is a gross hack at the moment. It is done by creating a new, temporary private keyring, letting the user remove the passphrases from the keys, and then exporting them. The temporary @@ -57,7 +61,7 @@ You can check on it with: # if no hex string is supplied, just print an explanation. # this covers seckey2sshagent --help, --usage, -h, etc... -if [ "$(echo "$1" | tr -d '0-9a-fA-F')" ]; then +if [ -z "$1" ] || [ "$(echo "$1" | tr -d '0-9a-fA-F')" ]; then explanation exit fi -- cgit v1.2.3 From 31162d196d875c6b5d44c704b59b8b8743c685a9 Mon Sep 17 00:00:00 2001 From: Jamie McClelland Date: Tue, 5 Aug 2008 13:04:33 -0400 Subject: chaning my previous edits - which were made before I realized that the script is supposed to work with no arguments! This change also removes the "$GPGID" part for listing all private keys, which generates an error. --- src/seckey2sshagent | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/src/seckey2sshagent b/src/seckey2sshagent index ecfd7aa..b7b7ec2 100755 --- a/src/seckey2sshagent +++ b/src/seckey2sshagent @@ -26,10 +26,6 @@ explanation() { echo -n "The basic strategy of seckey2sshagent is to dump your OpenPGP authentication key(s) into your agent. -The first argument to the command should be your gpg key id (the 8 -character hex string; try gpg --list-key your@emailaddress.org to -lookup your key id). - This script is a gross hack at the moment. It is done by creating a new, temporary private keyring, letting the user remove the passphrases from the keys, and then exporting them. The temporary @@ -61,7 +57,7 @@ You can check on it with: # if no hex string is supplied, just print an explanation. # this covers seckey2sshagent --help, --usage, -h, etc... -if [ -z "$1" ] || [ "$(echo "$1" | tr -d '0-9a-fA-F')" ]; then +if [ "$(echo "$1" | tr -d '0-9a-fA-F')" ]; then explanation exit fi @@ -72,7 +68,7 @@ GPGIDS="$1" if [ -z "$GPGIDS" ]; then # default to using all fingerprints of authentication-enabled keys - GPGIDS=$(gpg --with-colons --fingerprint --fingerprint --list-secret-keys "$GPGID" | egrep -A1 '^(ssb|sec):.*:[^:]*a[^:]*:$' | grep ^fpr: | cut -d: -f10) + GPGIDS=$(gpg --with-colons --fingerprint --fingerprint --list-secret-keys | egrep -A1 '^(ssb|sec):.*:[^:]*a[^:]*:$' | grep ^fpr: | cut -d: -f10) fi for GPGID in $GPGIDS; do -- cgit v1.2.3