Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kwallet pam fix #103080

Closed
wants to merge 1 commit into from
Closed

Conversation

SCOTT-HAMILTON
Copy link
Contributor

@SCOTT-HAMILTON SCOTT-HAMILTON commented Nov 7, 2020

Motivation for this change

#101904

Things done

Tried the fix provided by the gentoo guys, this seems to cause massive rebuilds, I don't have the processing power to try it. sddm/sddm#1265

  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@FRidh
Copy link
Member

FRidh commented Nov 7, 2020

Note the PAM upgrade is not really a possibility for 20.09.

@arapov
Copy link
Contributor

arapov commented Nov 13, 2020

This fixed kwallet issue on my system. Tested today.

@ttuegel
Copy link
Member

ttuegel commented Dec 5, 2020

According to SDDM upstream, we should not even be using their PAM configuration, it is provided only as an example. Also, it seems like the PAM update is not necessary for the fix?

@Ekleog
Copy link
Member

Ekleog commented Jan 14, 2021

@SCOTT-HAMILTON This PR currently can't be merged as the current version of pam master is higher than the one in this PR. Could you remove that change from the PR? :)

As for the sed command itself, I would not feel comfortable doing such a direct sed on the pam file, as it can very easily become a security liability, if an update to the configuration file starts relying on the fact that it is include and not substack. Could you instead copy the whole file, and maybe assert that upstream is the old file before using the new file instead? (or, alternatively, a patch that has as context the whole file would probably fit the bill too)

@SuperSandro2000
Copy link
Member

a patch that has as context the whole file would probably fit the bill too)

Good catch. I would prefer a patch.

@SuperSandro2000
Copy link
Member

Please do not merge branches into PRs to fix meme conflicts. Instead please use rebase.

@SCOTT-HAMILTON SCOTT-HAMILTON force-pushed the kwallet-pam-fix branch 2 times, most recently from 1d581ee to 3469029 Compare February 23, 2021 10:12
@stale
Copy link

stale bot commented Aug 22, 2021

I marked this as stale due to inactivity. → More info

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Aug 22, 2021
@Mindavi
Copy link
Contributor

Mindavi commented Nov 27, 2021

I haven't seen this issue for a long time now (but I did see this issue a year ago too). Please reopen if it's still an issue and if this fix is still valid.

I'm running unstable, so it may be that I'm just lucky that I'm not experiencing this anymore.

@Mindavi Mindavi closed this Nov 27, 2021
@stale stale bot removed the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Nov 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants