Bug 210510 - sysutils/fusefs-encfs: Can't create any files in encrypted drive.
Summary: sysutils/fusefs-encfs: Can't create any files in encrypted drive.
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on: 210532
Blocks:
  Show dependency tree / graph
 
Reported: 2016-06-24 06:38 UTC by freebsd
Modified: 2016-06-27 05:48 UTC (History)
2 users (show)

See Also:
vlad-fbsd: maintainer-feedback+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description freebsd 2016-06-24 06:38:19 UTC 
After updating encfs to fusefs-encfs-1.8.1 I have problems with handling encrypted fs. I am able to mount my disk but I can't create any files in encrypted drive. This is strange because I actually can create directories in it.
Everything was working on the previous version fusefs-encfs-1.7.4_7.
This happens not only with my old encrypted drive but with newly created also.

system: 10.3-RELEASE
all other ports are updated by portmaster -a
Comment 1 Dmitri Goutnik freebsd_committer freebsd_triage 2016-06-24 15:57:17 UTC 
Thanks for reporting this, I'll submit an update shortly.
Comment 2 Dmitri Goutnik freebsd_committer freebsd_triage 2016-06-24 17:36:06 UTC 
Submitted patch: bug 210532
Comment 3 VK freebsd_triage 2016-06-24 19:47:03 UTC 
Dmitri, thanks for your feedback. To help us track such issues better in the future, please flag the reports with maintainer-feedback(+) when you respond to such PRs requesting your feedback (as maintainer). ;)
Comment 4 Dmitri Goutnik freebsd_committer freebsd_triage 2016-06-24 19:54:53 UTC 
I will, thanks. I'm still figuring out FreeBSD Bugzilla.
Comment 5 Kurt Jaeger freebsd_committer freebsd_triage 2016-06-27 05:48:51 UTC 
Fix was committed. Dmitri: For future bugs: add the fix to the bug report, there's no need for an additional PR for the fix.