<?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>persistence on Rich Mirch</title>
    <link>https://blog.mirch.io/tags/persistence/</link>
    <description>Recent content in persistence on Rich Mirch</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Jan 2019 18:16:32 +0000</lastBuildDate>
    <atom:link href="https://blog.mirch.io/tags/persistence/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux persistence idea - using group passwords</title>
      <link>https://blog.mirch.io/2019/01/09/linux-persistence-idea-using-group-passwords/</link>
      <pubDate>Wed, 09 Jan 2019 18:16:32 +0000</pubDate>
      <guid>https://blog.mirch.io/2019/01/09/linux-persistence-idea-using-group-passwords/</guid>
      <description>A rarely used feature on Linux and UNIX systems is the ability to add a password to a group. The concept is similar to how users are handled. An encrypted hash is stored in the second field of the &lt;a href=&#34;http://man7.org/linux/man-pages/man5/gshadow.5.html&#34;&gt;gshadow(5)&lt;/a&gt; file. Anyone with the password can execute the &lt;a href=&#34;http://man7.org/linux/man-pages/man1/newgrp.1.html&#34;&gt;newgrp(1)&lt;/a&gt; command to temporarily change their GID without having to be a member of the group. The goal of this post is to show how this feature can be leveraged to create persistence on a server in a semi stealthy way.</description>
    </item>
  </channel>
</rss>
