New answers tagged

0

While the question has already been answered by user @Tony, it is not clear enough about the actual reason: One day someone turned on verbose logging of Kerberos events on the server. And to disable it you should delete the following registry value: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters Registry Value: LogLevel Value ...


0

If you are using domain or ads you are out of luck: Domain member setups require winbindd Setups with "security = domain" or "security = ads" require a running 'winbindd' now. The fallback that smbd directly contacts domain controllers is gone. You will need to use winbind to join the domain in any other case.


0

It is not implemented anywhere, thus not available. However, I'd recommend against using this approach. Aside from convenience you would be losing audit of the actions performed. Going with sudo rules would still allow you to keep access to X forwarding anyway (it is pretty much a socket access to something advertised through an environmental variable). What ...


0

I am not aware of any way to share .k5login using ldap. It is however possible to derive authorized_keys like functionality using ldap. If you are using sssd have a look at sss_ssh_authorizedkeys command (sssd-common package on AlmaLinux 8.5) and AuthorizedKeysCommand sshd_config option. For plain ldap functionality have a look at ssh-ldap-helper program. It ...


2

Linux removed support for RC4-HMAC-MD5 from Kerberos in 5.10. Your client uses that encryption type as can bee seen in the server's log output: [2021/09/21 21:55:44.761282, 3] ../../source4/auth/kerberos/krb5_init_context.c:80(smb_krb5_debug_wrapper) Kerberos: Client supported enctypes: arcfour-hmac-md5, aes128-cts-hmac-sha1-96, aes256-cts-hmac-sha1-96, ...


Top 50 recent answers are included