Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#69930 - [encfs] encfs broken?

Attached to Project: Community Packages
Opened by David Rosenstrauch (darose) - Wednesday, 10 March 2021, 02:50 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Monday, 24 May 2021, 13:49 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Maybe I'm going crazy, but it looks to me like there's something broken with the encfs package. I'm not sure when this started, as I don't use encfs very often. But today I went to use one of my encrypted directories and encfs won't encrypt it - keeps telling me incorrect password. But I'm like 99.9% sure I'm typing the correct password. I'll admit there is a small chance that I could have the password wrong, and this is all me. But again I really don't think so.

Can anyone definitively confirm or deny whether the package is broken? Are there any recent package upgrades that could have broken encfs' operation? (I see that encfs itself hasn't been upgraded in quite some time.
This task depends upon

Closed by  Jaroslav Lichtblau (Dragonlord)
Monday, 24 May 2021, 13:49 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Not a bug.
Comment by David Rosenstrauch (darose) - Wednesday, 10 March 2021, 03:15 GMT
(Meant to type "... encfs won't *de*crypt it ...")

The package does appear to *work* - as in I can create a new encrypted directory, and then later access that. But it does not seem to be able to decrypt old encrypted dirs.

BTW, last time I successfully used encfs on some older encrypted data was "May 20, 2020", if that's of any relevance.
Comment by David Rosenstrauch (darose) - Wednesday, 10 March 2021, 19:50 GMT
My bad - I had the password slightly wrong. No bug. This can be closed.

Loading...