summaryrefslogtreecommitdiff
path: root/src/share/m/update_known_hosts
diff options
context:
space:
mode:
authorJameson Rollins <jrollins@finestructure.net>2010-10-22 16:25:04 -0400
committerJameson Rollins <jrollins@finestructure.net>2010-10-24 11:51:02 -0400
commitaf9ff0feedd40dadc8df15bf9f5392a599e5279e (patch)
treeb97a3f94a107b045d29cd527515e697e477c0464 /src/share/m/update_known_hosts
parentc7d807fb792096862a27fa0742f825d4792b7a01 (diff)
don't fail if authorized_keys file not present
we create a new function here, touch_key_file_or_fail, which will touch a new key file if there isn't one already present. This is now used in the update_authorized_keys and update_known_hosts functions when looking for authorized_keys and known_hosts respectively. Closes Debian 600644
Diffstat (limited to 'src/share/m/update_known_hosts')
-rw-r--r--src/share/m/update_known_hosts18
1 files changed, 4 insertions, 14 deletions
diff --git a/src/share/m/update_known_hosts b/src/share/m/update_known_hosts
index 737666d..57176b8 100644
--- a/src/share/m/update_known_hosts
+++ b/src/share/m/update_known_hosts
@@ -21,28 +21,18 @@ update_known_hosts() {
# touch the known_hosts file so that the file permission check
# below won't fail upon not finding the file
- if [ ! -f "$KNOWN_HOSTS" ]; then
- # make sure to create any files or directories with the appropriate write bits turned off:
- newUmask=$(printf "%04o" $(( 0$(umask) | 0022 )) )
- [ -d $(dirname "$KNOWN_HOSTS") ] \
- || (umask "$newUmask" && mkdir -p -m 0700 $(dirname "$KNOWN_HOSTS") ) \
- || failure "Could not create path to known_hosts file '$KNOWN_HOSTS'"
- # make sure to create this file with the appropriate bits turned off:
- (umask "$newUmask" && touch "$KNOWN_HOSTS") \
- || failure "Unable to create known_hosts file '$KNOWN_HOSTS'"
- fi
-
+ touch_key_file_or_fail "$KNOWN_HOSTS"
check_key_file_permissions $(whoami) "$KNOWN_HOSTS" \
- || failure "Bad permissions governing known_hosts file '$KNOWN_HOSTS'"
+ || failure "Bad permissions governing known_hosts file $KNOWN_HOSTS"
lock create "$KNOWN_HOSTS"
# FIXME: we're discarding any pre-existing EXIT trap; is this bad?
- trap "lock remove $KNOWN_HOSTS" EXIT
+ trap "log debug TRAP; lock remove $KNOWN_HOSTS" EXIT
tmpFile=$(mktemp "${KNOWN_HOSTS}.monkeysphere.XXXXXX")
- trap "lock remove $KNOWN_HOSTS; rm -f $tmpFile" EXIT
+ trap "log debug TRAP; lock remove $KNOWN_HOSTS; rm -f $tmpFile" EXIT
cat "$KNOWN_HOSTS" >"$tmpFile"