Hi Sheetal, When replying to emails on this list, please do not put your reply above the quoted text, and do not quote the entire message you're answering to. This makes it unnecessarily hard for other readers to understand the context of your email. Instead, please cut quoted parts that are not relevant to your reply, and insert your responses right after the points you're replying to.
I would have done that in this email myself, but since you actually replied to your own email (instead of my response) things are a little messy now. On May 07 2016, [email protected] wrote: >> Are there any diagnostic steps or possible options for recovering this >> s3ql filesystem in this scenario where the encryption passphrase cannot >> decrypt the s3ql_passphrase keyfile ? >> Any help is really appreciated ! > > Thanks for your prompt reply. > We are running S3QL 1.19, so there is no backup of the passpharse file in > the object store. > > Does mkfs.s3ql return a master key ? How can we use that to recover the > passpharse file ? Hmm. I'm afraid you're out of luck then. As you said, S3QL 1.x did not create backup copies of the master key, nor does mkfs.s3ql print the master key on file system creation. The master key would have been printed (and backed up) when upgrading to S3QL 2.7 (for backups) or 2.13 (for printout on mkfs). 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.
