tomb

commit 1affad00d5a03b69b72fd1b3cafc9d534e4581c7
parent e8c7120fa4e0bd592bb5179be90d236a2befcadb
Author: Jaromil <jaromil@dyne.org>
Date:   Fri, 13 May 2011 16:30:19 +0200

fix permissions of new tomb
and notice if tomb hasn't right permissions

in future we should check permissions of tomb from the suid commandline
this way we can also change its permissions and make it ours

Diffstat:
M
src/tomb
 | 
2
+-
M
src/tomb-open
 | 
2
+-

2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/tomb b/src/tomb
@@ -442,7 +442,7 @@ create_tomb() {
 
     # set permissions on the tomb
     sudo chown $UID:$GID ${tombfile}
-    sudo chmod go-rwx ${tombfile}
+    sudo chmod 600 ${tombfile}
 
     act "done creating $tombname encrypted storage (using Luks dm-crypt AES/SHA256)"
     notice "Your tomb is ready in ${tombdir}/${tombfile} and secured with key ${tombfile}.key"
diff --git a/src/tomb-open b/src/tomb-open
@@ -221,7 +221,7 @@ if [ $1 ]; then # is it a file?
 		exit 1
 	    fi
 	else
-	    tomb-notify "Not a real Tomb." "We found no real bones in there."
+	    tomb-notify "Not a real Tomb." "We found no real bones in there, or the tomb file permissions won't allow us in."
 	    exit 1
 	fi