OpenSSH - Ignore user's .ssh/authorized_keys and pull them from FreeIPA instead

This will likely only be interesting to you if you have your users stored centrally using some form of centralized identity management such as OpenLDAP, 389ds, or FreeIPA which again uses 389ds in the background.

I'll configure SSHD to ignore each user's .ssh/authorized_keys file with the only exception being root. SSH-Keys for users will be stored in FreeIPA which can be managed using the 'freeipa.ansible_freeipa' modules and git for example.

First, make sure your host is enrolled in FreeIPA

 [root@host ~]# ipa-client-install --mkhomedir --enable-dns-updates

Now that your client is enrolled, let's try querying a user that exists in the ldap tree

 [root@host ~]# $ executor

 uid=10007(executor) gid=10007(executor) groups=10007(executor),10011(ansible-users)

The ipa-client will automatically configure the 'AuthorizedKeysCommand' and 'AuthorizedKeysCommandUser' options which you could change to some self-written helper script if absolutely required.

 [root@host ~]# grep -i -e '^authorizedkeyscommand' /etc/ssh/sshd_config

 AuthorizedKeysCommand /usr/bin/sss_ssh_authorizedkeys  
 AuthorizedKeysCommandUser nobody

Since the client is enrolled, we can disable the local .ssh/authorized_keys for all users except root and restart the ssh daemon to make changes take effect.

 [root@host ~]# sed -i 's/^AuthorizedKeysFile\ \.ssh\/authorized_keys/AuthorizedKeysFile\ \/dev\/null/g' /etc/ssh/sshd_config  
 [root@host ~]# echo -e 'Match user root\n\tAuthorizedKeysFile .ssh/authorized_keys' >> /etc/ssh/sshd_config  
 [root@host ~]# systemctl restart sshd.service

Now that sshd is restarted and the config changes are live, create a ssh-key for a user and test it out.

NOTE: this will not set a password for the key which is not recommended for production use. I will only do this for demonstration purposes.

 [root@host ~]# ssh-keygen -a 64 -t ecdsa -b 521 -f userkey -C "$(date +%F)" -N ""  
 [root@host ~]# ipa user-mod executor --sshpubkey "$(cat userkey.pub)"

Check using the helper program that sshd is going to use for fetching keys if everything has been applied as expected. As I left the default, I will test using 'sss_ssh_authorizedkeys'

 [root@host ~]# sss_ssh_authorizedkeys executor

 ecdsa-sha2-nistp521 AAAAE00...

As you can see, the key-data is stored centrally and we should be able to log in as the executor user, assuming the required hbac rules are in place allowing sshd.

 [root@host ~]# ssh -i userkey executor@$(hostname -f)  
 [executor@host ~]$

You can also check what key has been used by having a look at the '/var/log/secure' file filtering for the user

 [root@host ~]# sudo grep -i -A 1 -e 'publickey' /var/log/secure | grep -i -e 'executor'

Edits to any local .ssh/authorized_keys file will be ignored (except root) and keys will be pulled from a centrally managed user directory.

Feel free to comment and / or suggest a topic.

Comments

Dynamic DNS with BIND and ISC-DHCP

I personally prefer to work with hostnames instead of ip-addresses. If you have anything like freeipa or active directory, it will do that for you by registering the client you added to your realm to the managed dns and edit the records dynamically. We can achieve the same goal with just bind and isc-dhcp. I'll use a raspberry pi with raspbian 9 for this setup. So here is a quick tutorial on how to configure the isc-dhcp-server to dynamically update bind. First set a static ip to your server. [archy@ddns ~]$ sudo vim /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto eth0 iface eth0 inet static address 172.31.30.5 network 172.31.30.0 broadcast 172.31.30.255 netmask 255.255.255.0 ...

LACP-Teaming on CentOS 7 / RHEL 7

What is teaming? Teaming or LACP (802.3ad) is a technique used to bond together multiple interfaces to achieve higher combined bandwith. NOTE: every clients speed can only be as high as the single link speed of one of the members. That means, if the interfaces I use in the bond have 1 Gigabit, every client will only have a maximum speed of 1 Gigabit. The advantage of teaming is, that it can handle multiple connections with 1 Gigabit. How many connections depends on the amount of your network cards. I'm using 2 network cards for this team on my server. That means I can handle 2 Gigabit connections at full rate on my server provided the rest of the hardware can deliver that speed. There also exists 'Bonding' in the Linux world. They both do the same in theory but for a detailed comparison check out this article about teaming in RHEL7 . To create a teaming-interface, we will first have to remove all the interface configurations we've done on the (soon to be) sla...

Push logs and data into elasticsearch - Part 2 Mikrotik Logs

This is only about the setup of different logging, one being done with Filebeat and the other being done with sending logging to a dedicated port opened in Logstash using the TCP / UDP Inputs. Prerequesites: You'll need a working Elasticsearch Cluster with Logstash and Kibana. Start by getting the Log Data you want to structure parsed correctly. Mikrotik Logs are a bit difficult since they show you Data in the interface which is already enriched with Time / Date. That means a message that the remote logging will send to Logstash will look like this: firewall,info forward: in:lan out:wan, src-mac aa:bb:cc:dd:ee:ff, proto UDP, 172.31.100.154:57061->109.164.113.231:443, len 76 You can check them in the grok debugger and create your own filters and mapping. The following is my example which might not fit your needs. Here are some custom patterns I wrote for my pattern matching: MIKROTIK_DATE \b(?:jan(?:uary)?|feb(?:ruary)?|mar(?:ch)?|apr(?:il)?|may|jun(?:e)?|jul(?...

FreeIPA - Integrating your DHCPD dynamic Updates into IPA

I recently went over my network configuration and noticed that the dhcp-leases were not pushed into the IPA-DNS yet. So I thought, why not do it now. The setup is very similar to setting it up on a single bind instance not managed by IPA (I've already written a guide about this here ). My setup is done with the following hosts: ipa01.archyslife.lan - 172.31.0.1 inf01.archyslife.lan - 172.31.0.5 First of all, create a rndc-key: [archy@ipa01 ~]$ sudo rndc-confgen -a -b 512 This will create the following file '/etc/rndc-key' [archy@ipa01 ~]$ sudo cat /etc/rndc.key key "rndc-key" { algorithm hmac-md5; secret "secret_key_here=="; }; We also need to make named aware of the rndc-key and allow our remote dhcp server to write dns entries: [archy@ipa01 ~]$ sudo vim /etc/named.conf ... include "/etc/rndc-key"; controls { inet 172.31.0.1 port 953 allow { 172.31.0.5; } keys ...

SSSD - Debugging PAM permission denied

Sometimes there's weird errors in IT that occur on random chance. I've had such an encounter with SSSD in combination with IPA(+AD-Trust) recently, where only sometimes, a connection to one of the IPA-Servers would fail with this error: Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: pam_sss(sshd:account): Access denied for user runner: 4 (System error) Jul 13 13:36:42 ipa02.archyslife.lan sshd[3478]: fatal: Access denied for user runner by PAM account configuration [preauth] In my case, it was only happening sometimes when running a basic system setup role using ansible on every host in the entire environment. This way, there was no consistent pattern besides being the same host every time if it failed. First up, add the 'debug_level=X' to every section required in the /etc/sssd/sssd.conf where X is a number from 1 to 10 with 10 being the most verbose. Afterward, restart sssd and check the logs for any obvious problems. 1) If you are using local users, check the...

Archy's Blog

Search This Blog