| Age | Commit message (Collapse) | Author | 
|---|
|  | In the error case, buf was not restored to the original
capacity. Instead of truncating "buf" and restoring (or forgetting to restore)
later, introduce the "data" slice.
Fixes https://github.com/rfjakob/gocryptfs/issues/356 | 
|  | Make sure we get only 1 warning output per
problem.
Also, add new corruption types to broken_fs_v1.4. | 
|  | This Warn() is causing panics in the test suite
on MacOS: https://github.com/rfjakob/gocryptfs/issues/213 | 
|  |  | 
|  | Misspell Finds commonly misspelled English words
gocryptfs/internal/configfile/scrypt.go
Line 41: warning: "paramter" is a misspelling of "parameter" (misspell)
gocryptfs/internal/ctlsock/ctlsock_serve.go
Line 1: warning: "implementes" is a misspelling of "implements" (misspell)
gocryptfs/tests/test_helpers/helpers.go
Line 27: warning: "compatability" is a misspelling of "compatibility" (misspell) | 
|  | We have to check if the input path is empty AFTER canonicalizing it,
too! | 
|  | internal/ctlsock/ctlsock_serve.go:73:1: comment on exported const
ReadBufSize should be of the form "ReadBufSize ..." | 
|  | The code was missing a "continue" in that branch.
Also improve the error messages a bit. | 
|  | Reading partial JSON would cause a mess. Just kill the connection.
Also, stop using syscall.PathMax that is not defined on Darwin
( https://github.com/rfjakob/gocryptfs/issues/15#issuecomment-264253024 ) | 
|  |  | 
|  | Both are achieved by opening the socket from main and passing
it to the ctlsock package instead of passing the path. | 
|  | You used to be able to crash gocryptfs by passing "/foo"
of "foo/" to the ctlsock.
Fixes https://github.com/rfjakob/gocryptfs/issues/66 | 
|  | At the moment, in forward mode you can only encrypt paths
and in reverse mode you can only decrypt paths. |