From d4160e07cfc1942844160fdb8e6c9525da0bd2c8 Mon Sep 17 00:00:00 2001 From: "Joe Richey joerichey@google.com" Date: Wed, 31 May 2017 12:49:06 -0700 Subject: pam: checking a user's login passphrase This commit adds in the fscrypt/pam package. This package will hold all functionality related to Linux Pluggable Authentication Modules (PAM). Right now this package uses cgo to mock a PAM conversation, allowing the function to check if a provided passphrase actually belongs to a user. Due to the nature of cgo callbacks, global state of the key to check is necessary for this function. This commit also addresses some issues about building the cgo components. Now, only the minimal linking flags are included in the go files. Additional linker flags may now be necessary to build a static binary of fscrypt. This is addressed in the Makefile and README. Finally, this commit fixes a bug where the tests would not run correctly due to shared global state on the testing filesystem. Fixed, by having all the tests run sequentially. Change-Id: Ia43636801da984b505d2f43dd14127b7cfbf2c48 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index be0e3e3..caad7fe 100644 --- a/README.md +++ b/README.md @@ -101,7 +101,7 @@ You will also want to add `$GOPATH/bin` to your `$PATH`. `libblkid-devel` for RPM, should already be part of `util-linux` for Arch). Once this is setup, you can run `make fscrypt` to build the executable in -the root directory. Pass `"LDFLAGS += -static"` to `make` to get a static +the root directory. See the `Makefile` for instructions on building a static executable. If a Go project contains C code, the go compiler produces a dynamically linked binary by default. -- cgit v1.2.3