Authfile is ignored if it's a symlink

[GoogleCodeExporter]

Hi as said above, i made a correct authfile as specified in the docs.
I later even chmodded it to 600

Now with any s3ql command that i try to use, it still asks me to enter 
credentials manually in the terminal.

Example: 

sudo fsck.s3ql --authfile /home/work/SecureData/keys/s3ql_auth.txt s3://testtest

authfile:

[s3]
storage-url: s3://testtest
backend-login: xxxx
backend-password: xxxx

Any hints?

I also tried authfile like that:

[s3]
storage-url: s3://
backend-login: xxxx
backend-password: xxxx

[testtest]
storage-url: s3://testtest

No change...

Thanks in advance!

Original issue reported on code.google.com by rali...@gmail.com on 18 Dec 2013 at 7:41

[GoogleCodeExporter]

S3QL 1.9 on ubuntu 12.04

Original comment by rali...@gmail.com on 18 Dec 2013 at 7:52

[GoogleCodeExporter]

Ok i found out:

if the authfile is behind a symbolic link, it will not work..can we fix this?

Original comment by rali...@gmail.com on 18 Dec 2013 at 8:28

[GoogleCodeExporter]

Issue 449 has been merged into this issue.

Original comment by Nikolaus@rath.org on 19 Dec 2013 at 6:51

[GoogleCodeExporter]

Original comment by Nikolaus@rath.org on 19 Dec 2013 at 6:52

• Changed title: Authfile is ignored if it's a symlink

[GoogleCodeExporter]

This seems to work just fine for me:

$ md testbucket; mkfs.s3ql --quiet local://testbucket
Enter encryption password: 
Confirm encryption password: 

$ cat > authfile_real
[test]
storage-url: local://    
fs-passphrase: justthis

$ chmod 600 authfile_real
$ ln -s authfile_real authfile
$ fsck.s3ql --version
S3QL 2.5
$ fsck.s3ql --authfile `pwd`/authfile local://testbucket
Wrong file system passphrase
$ fsck.s3ql --authfile does_not_exist local://testbucket
Enter file system encryption passphrase: 

Could you give more detailed information about what you tried?

Original comment by Nikolaus@rath.org on 24 Dec 2013 at 11:36

• Changed state: NeedsInfo
• Added labels: Type-Improvement

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ok I tested more deeply now. Symlinking on the same file system works. It does 
not work if I  symlink over 2 different filesystems. In my case ext4 (linkfile) 
--> encfs (real file) . The reason I try to do this is obviously securing the 
authfile...;-) merry xmas

Original comment by rali...@gmail.com on 25 Dec 2013 at 2:11

[GoogleCodeExporter]

Could you please post an example (command by command, including output) that I 
can use to reproduce the problem? S3QL does not care about where the symlink 
points, it just opens the file and the OS takes care of the rest. It should not 
matter if the symlink target is on a different file system.

Original comment by Nikolaus@rath.org on 25 Dec 2013 at 7:03

[GoogleCodeExporter]

Lacking further information, I'll close this issue for now. Please feel free to 
report an issue on the new bug tracker 
(https://bitbucket.org/nikratio/s3ql/issues) if you can provide the missing 
information.

Original comment by Nikolaus@rath.org on 26 Jan 2014 at 2:40

• Changed state: Moved