Skip to content

Wrong link to /usr/local/share/pam-configs/fscrypt #240

New issue
New issue
Closed
#244
Closed
Wrong link to /usr/local/share/pam-configs/fscrypt#240
#244
Labels
documentation
@Redsandro

Description

@Redsandro
Redsandro
opened on Jul 26, 2020

I (manually) installed fscrypt 0.2.9 on Ubuntu 20.04 on a couple of machines, and noticed that while sudo pam-auth-update expects /usr/share/pam-configs/fscrypt but it is actually installed in /usr/local/share/pam-configs/fscrypt (note the local).

On one computer I just copied the file over, and on the other computer I make a symlink:

ln -s /usr/{local,}/share/pam-configs/fscrypt

Both work fine, but I'm not sure what is technically the best workaround.

Perhaps this can be fixed in the Makefile, but that might break things for other distros.

See the following sections in README.md:

fscrypt/README.md

Lines 138 to 141 in 0972347

Running `sudo make install` installs `fscrypt` to `/usr/local/bin`,
`pam_fscrypt.so` to `/usr/local/lib/security`, and `pam_fscrypt/config` to
`/usr/local/share/pam-configs`. Use `make install-bin` to only install
`fscrypt`. Use `make install-pam` to only install the pam files.

fscrypt/README.md

Lines 335 to 340 in 0972347

Both the official `fscrypt` package for Ubuntu and `sudo make install`
will install a configuration file for [Ubuntu's PAM configuration
framework](https://wiki.ubuntu.com/PAMConfigFrameworkSpec) to
`/usr/share/pam-configs/fscrypt`. This file contains reasonable
defaults for the PAM module. To automatically apply these defaults,
run `sudo pam-auth-update` and follow the on-screen instructions.

Feel free to close this issue if #wontfix because of reasons.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions