Thank you for the quick response. I now tried to script this using expect, which seems to be doing its job, but s3ql is not doing anything:
#!/usr/bin/expect -f spawn mkfs.s3ql s3://bucket/prefix expect "Enter encryption password: " send "PASSWORD\r" expect "Confirm encryption password: " send "PASSWORD\r Running the script produced the following output: root@localhost:~# ./test.sh spawn mkfs.s3ql s3://bucket/prefix Before using S3QL, make sure to read the user's guide, especially the 'Important Rules to Avoid Loosing Data' section. Enter encryption password: Confirm encryption password: root@localhost:~# Looks okay, but S3QL does not write anything to S3 and does not create the .params and .db files in ~/.s3ql/ Running all the commands manually works just fine. Any suggestions? Am Samstag, 14. März 2015 01:59:59 UTC+1 schrieb Nikolaus Rath: > > On Mar 13 2015, Bastian Noffer <[email protected] <javascript:>> > wrote: > > Hi, > > > > I am trying to manage s3ql using scripts including the fs creation in > > the bucket / container. I am using Debian 7 Wheezy which only provides > > S3QL 1.11.1. > > > > This works just fine when not using encryption, but when I need to > > create a new fs with encryption mkfs.s3ql prompts for the passphrase > > even if it is included in the authinfo2 file. > > That's deliberate to prevent accidental creation of a file system with > an unintended passphrase (because authinfo entries can be rather > generic). > > When scripting, you have to pass the passphrase via stdin. > > > Best, > -Nikolaus > > -- > GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F > Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F > > »Time flies like an arrow, fruit flies like a Banana.« > -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
