[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#831564: marked as done (RFP: gocryptfs -- encrypted overlay filesystem written in Go)

Your message dated Fri, 30 Sep 2016 22:40:52 -0400
with message-id <CAOHcdNbfTWHqie77QgEnpMGg6Hv_uHV1M8FiKjsVPkCGB=J+UA@mail.gmail.com>
and subject line gocryptfs ITP
has caused the Debian Bug report #831564,
regarding RFP: gocryptfs -- encrypted overlay filesystem written in Go
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

831564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831564
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist

gocryptfs is an encrypted FUSE overlay filesystem that uses modern
cryptography (GCM), fixes the leaks of EncFS while providing equivalent
performance. It is written in Go and MIT licensed.

This comparison page shows the differences to EncFS and other projects:

I am the author and have released version 1.0 today, declaring it ready for
general consumption.

gocryptfs is build-tested down to Go 1.3.3 using Travis CI
( https://travis-ci.org/rfjakob/gocryptfs ) but I recommend building using Go
1.6 to benefit from built-in AES-NI acceleration.

gocryptfs is released on github using signed git tags:
* repo at https://github.com/rfjakob/gocryptfs
* key at https://nuetzlich.net/gocryptfs-signing-key.pub
and additionally as binaries for Debian 8 and Fedora 24.

I will gladly provide other info you may need and work with the Debian team on
any issues.

Best regards,

--- End Message ---
--- Begin Message ---
Closed due to ITP #839279

"Le mieux est l'ennemi du bien" - Voltaire

--- End Message ---

Reply to: