<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Lilo on C&amp;CZ News</title>
    <link>https://cncz.science.ru.nl/tags/lilo/</link>
    <description>Recent content in Lilo on C&amp;CZ News</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>postmaster</managingEditor>
    <lastBuildDate>Tue, 28 Jan 2025 00:00:00 +0100</lastBuildDate><atom:link href="https://cncz.science.ru.nl/tags/lilo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>lilo access with managed SSH keys and ip range</title>
      <link>https://cncz.science.ru.nl/news/2025-01-28_lilo_access_via_ssh_pubkey_and_ip_range/</link>
      <pubDate>Tue, 28 Jan 2025 00:00:00 +0100</pubDate>
      <author>Simon Oosthoek</author>
      <guid>https://cncz.science.ru.nl/news/2025-01-28_lilo_access_via_ssh_pubkey_and_ip_range/</guid>
      <description>&lt;p&gt;We have updated the authentication process for &lt;a href=&#34;https://cncz.science.ru.nl/howto/hardware-servers/#linux-login-servers&#34;&gt;login servers&lt;/a&gt; after a succesful test we announced in &lt;a href=&#34;https://cncz.science.ru.nl/cpk/1383/&#34; target=&#34;_blank&#34;&gt;CPK#1383&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;As of now, your &lt;code&gt;~/.ssh/authorized_keys&lt;/code&gt; file on lilo is ignored!&lt;/strong&gt;, instead you can send us your public ssh key (contents of the &lt;code&gt;.pub&lt;/code&gt; file) to keep for your account. This change is designed to prevent bad actors from easily gaining persistent access. For convenience we have added the keys we have found in homedirectories that were added or modified after we restricted access to lilo, if your key is from before December 9th, you will need to send the public key to us.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
