<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ssh Archives - blog.icod.de</title>
	<atom:link href="https://blog.icod.de/tag/ssh/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.icod.de/tag/ssh/</link>
	<description>Webentwicklung und sonstiger Unsinn :) Web development and other nonsense :)</description>
	<lastBuildDate>Wed, 19 Mar 2025 13:13:40 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://blog.icod.de/wp-content/uploads/2017/04/darko-luketic-foto.256x256-150x150.jpg</url>
	<title>ssh Archives - blog.icod.de</title>
	<link>https://blog.icod.de/tag/ssh/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>gitea log configuration for fail2ban</title>
		<link>https://blog.icod.de/2025/03/19/gitea-log-configuration-for-fail2ban/</link>
					<comments>https://blog.icod.de/2025/03/19/gitea-log-configuration-for-fail2ban/#respond</comments>
		
		<dc:creator><![CDATA[Darko Luketic]]></dc:creator>
		<pubDate>Wed, 19 Mar 2025 13:10:46 +0000</pubDate>
				<category><![CDATA[Allgemein]]></category>
		<category><![CDATA[config]]></category>
		<category><![CDATA[fail2ban]]></category>
		<category><![CDATA[gitea]]></category>
		<category><![CDATA[ssh]]></category>
		<guid isPermaLink="false">https://blog.icod.de/?p=2301</guid>

					<description><![CDATA[<p>Gitea since 1.21 has a different logging configuration format. TL;DR If you want to configure fail2ban to ban those failed ssh login attempts, use this log section in app.ini [crayon-69c8a9009d70d645901515/] Sadly you can&#8217;t turn off all logging except the SSH log. You have to wear your SSD. The actual fail2ban configuration is described on their&#8230;</p>
<p>The post <a href="https://blog.icod.de/2025/03/19/gitea-log-configuration-for-fail2ban/">gitea log configuration for fail2ban</a> appeared first on <a href="https://blog.icod.de">blog.icod.de</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.icod.de/2025/03/19/gitea-log-configuration-for-fail2ban/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>sshd sftp chroot jail howto</title>
		<link>https://blog.icod.de/2023/10/05/sshd-sftp-chroot-jail-howto/</link>
					<comments>https://blog.icod.de/2023/10/05/sshd-sftp-chroot-jail-howto/#respond</comments>
		
		<dc:creator><![CDATA[Darko Luketic]]></dc:creator>
		<pubDate>Thu, 05 Oct 2023 15:00:42 +0000</pubDate>
				<category><![CDATA[Entwicklung]]></category>
		<category><![CDATA[chroot]]></category>
		<category><![CDATA[ftps]]></category>
		<category><![CDATA[jail]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[ssh]]></category>
		<category><![CDATA[sshd]]></category>
		<guid isPermaLink="false">https://blog.icod.de/?p=1960</guid>

					<description><![CDATA[<p>Problem description: You would like to jail users to their home directories and not allow shell access, only sftp access. Solution: SFTP chroot jail 1. Create a system group. Here I call it sftponly. [crayon-69c8a9009d89c856635292/] 2. edit the sshd_config file, usually residing in /etc/ssh/sshd_config (in weird opensuse it&#8217;s in /usr/etc/sshd/ ) and append (it needs&#8230;</p>
<p>The post <a href="https://blog.icod.de/2023/10/05/sshd-sftp-chroot-jail-howto/">sshd sftp chroot jail howto</a> appeared first on <a href="https://blog.icod.de">blog.icod.de</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.icod.de/2023/10/05/sshd-sftp-chroot-jail-howto/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
