Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 07:16
    yaleman commented #991
  • 06:02
    yaleman review_requested #991
  • 06:02
    yaleman edited #991
  • 06:02
    yaleman synchronize #991
  • 06:02

    yaleman on issue989

    clap tweaks (compare)

  • 06:00
    yaleman opened #991
  • 06:00

    yaleman on issue989

    updated kanidm help string (compare)

  • 05:37

    yaleman on issue989

    first commit of this change checkpoint it verks (compare)

  • Aug 13 06:50
    yaleman assigned #989
  • Aug 13 01:17
    yaleman synchronize #171
  • Aug 13 01:17

    yaleman on 20220805-fido-mds

    maybe actually possibly fixing … (compare)

  • Aug 13 01:10
    yaleman synchronize #171
  • Aug 13 01:10

    yaleman on 20220805-fido-mds

    fixin dem testing (compare)

  • Aug 13 00:11
    Firstyear synchronize #171
  • Aug 13 00:11

    Firstyear on 20220805-fido-mds

    logadapter (compare)

  • Aug 12 23:58
    Firstyear synchronize #171
  • Aug 12 23:58

    Firstyear on 20220805-fido-mds

    Add authenticator-cli - should … Nothing to see here (compare)

  • Aug 12 23:45
    Firstyear commented #990
  • Aug 12 23:41
    Firstyear commented #990
  • Aug 12 22:09
    yaleman labeled #990
James Hodgkinson
@yaleman
So many different SSL libs, why can't we just have a standard :D
Triss Healy
@trissylegs
Well everyone used to use OpenSSL until Shellshock and the ecosystem shattered
(or NSS for Firefox and Chrome)
I succesfully managed to setup PAM and NSS switch for everythign but actually authentication
Firstyear
@Firstyear
@trissylegs What issues are you hitting?
Did you set an allowed group ?
Also yeah, I think it was heartbleed that caused a lot of panic and initial forks like libressl, but it also prompted a lot of investwent into openssl and it's actually gotten a lot better since.
Where libressl seems to have languished
Heck, openssl 3.0.0 today
Triss Healy
@trissylegs
libressl also suffers from nobody wants to work with OpenBSD devs if they can help it.
Firstyear
@Firstyear
Loooooolllll
Yeah
@trissylegs When you say you can't authenticate what's the actual logs or symptmos from a login attempt? Can users resolve with getent passwd <name>?
Triss Healy
@trissylegs
# getent passwd nirya                        
nirya:x:1001:1001:Triss Healy:/home/nirya:/usr/bin/zsh
Firstyear
@Firstyear
Okay that's a solid start
Triss Healy
@trissylegs
(Yes I'm using name instead of spn because there's too many names to fix up)
Firstyear
@Firstyear
No that's fine
That's why it's there
I use name as well at home too
the spn thing is meant for future proofing when (if?) i add trusts
Triss Healy
@trissylegs
It's also good for RDM and other weird things.
Firstyear
@Firstyear
Okay, can you show me your /etc/kanidm/unixd config?
Triss Healy
@trissylegs
% cat /etc/kanidm/unixd
# this should be at /etc/kanidm/unixd, and configures kanidm-unixd
# some documentation is here: https://github.com/kanidm/kanidm/blob/master/kanidm_book/src/pam_and_nsswitch.md
pam_allowed_login_groups = ["humans"]
# default_shell = "/bin/bash"
home_prefix = "/home/"
home_attr = "uuid"
home_alias = "name"
uid_attr_map = "name"
gid_attr_map = "name"
Oh this is the message I get:
$ su -l nirya
Password: 
su: Authentication service cannot retrieve authentication info
Firstyear
@Firstyear
can you show me getent group humans?
Triss Healy
@trissylegs
$ getent group humans
humans:x:2001:test_user,nirya
Firstyear
@Firstyear
Which distro?
Triss Healy
@trissylegs
Arch linux. Editing PAM is mostly been guessing because its different to both SUSE and Redhat
Firstyear
@Firstyear
Right
Okay, so the next steps would be

systemctl edit kanidm-unix.service

[Service]
Environment="RUST_LOG=kanidm=debug"

in pam, on lines with pam_kanidm.so, add the option debug

Then restart kanidm-unixd, and try su again.
Youll have more info in journalctl, and it prints more to the TTY from the pam module.
But after that I'll need to see your /etc/pam.d/su and probably other fules.
files*
There is a troubleshooting section here which is honestly what I'm reading XD
Triss Healy
@trissylegs
Yea. I've been through most of that
I think it'll be something in /etc/pam.d
Firstyear
@Firstyear
Yeah, most likely
Pam is really tricky and delicate at the best of times :(
Triss Healy
@trissylegs
Firstyear
@Firstyear
That all looks happy
content of /etc/pam.d/su ?
It may have include statements, so if those are present, can you provide those files too?
Triss Healy
@trissylegs
From what I gathered. Arch linux pam nearly all includes system-login
Firstyear
@Firstyear
Yeah, but better to check what /etc/pam.d/su actually says :P
Triss Healy
@trissylegs
% cat su
#%PAM-1.0
auth            sufficient      pam_rootok.so
# Uncomment the following line to implicitly trust users in the "wheel" group.
#auth           sufficient      pam_wheel.so trust use_uid
# Uncomment the following line to require a user to be in the "wheel" group.
#auth           required        pam_wheel.so use_uid
auth            required        pam_unix.so
account         required        pam_unix.so
session            required        pam_unix.so
password        include         system-auth
pam.d/su-l is identical
Firstyear
@Firstyear
Yeah, that would be the isses, it's not including system-auth for auth/account/session, it's only using pam_unix