<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: You cannot! in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/3816705#M73458</link>
    <description>&lt;P&gt;This is not something that anyone should be doing on an ISE deployment, and it won't enable a user to access root or the linux shell. ISE leverages something called ADE-OS which sits on top of RHEL. As indicated by nspasov, you access the underlying Linux CLI via TAC and the root key/root patch. This is not something Cisco provides for end user use, it is only used by TAC during troubleshooting to fix advanced issues. So even if you edit the root password, you need the root key that expires frequently, and the root patch that will work on your version.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It's also a 5 year old thread, no need to bump this.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 09 Mar 2019 09:01:46 GMT</pubDate>
    <dc:creator>Damien Miller</dc:creator>
    <dc:date>2019-03-09T09:01:46Z</dc:date>
    <item>
      <title>How to get into linux shell on Cisco ISE 1.2 ??</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/2546891#M73447</link>
      <description>&lt;P&gt;How to get into linux shell on Cisco ISE 1.2 ???&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 04:57:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/2546891#M73447</guid>
      <dc:creator>Ambuj M</dc:creator>
      <dc:date>2019-03-11T04:57:16Z</dc:date>
    </item>
    <item>
      <title>Please follow the below steps</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/2546892#M73451</link>
      <description>&lt;P&gt;Please follow the below steps.&lt;/P&gt;&lt;P&gt;&lt;B&gt;Step 1&lt;/B&gt;&lt;IMG alt="" border="0" height="2" src="http://www.cisco.com/c/dam/en/us/td/i/templates/blank.gif" width="5" /&gt; After the Cisco ISE installation, launch a supported product, such as PuTTY, for establishing a Secure Shell (SSH) connection to a Cisco ISE appliance.&lt;/P&gt;&lt;P class="pSN_StepNext"&gt;&lt;B&gt;Step 2&lt;/B&gt;&lt;IMG alt="" border="0" height="2" src="http://www.cisco.com/c/dam/en/us/td/i/templates/blank.gif" width="5" /&gt; In the Host Name (or IP Address) field, enter the hostname (or the IP address in dotted decimal format of the Cisco ISE appliance) and click &lt;B class="cBold"&gt; Open&lt;/B&gt; .&lt;/P&gt;&lt;P class="pSN_StepNext"&gt;&lt;B&gt;Step 3&lt;/B&gt;&lt;IMG alt="" border="0" height="2" src="http://www.cisco.com/c/dam/en/us/td/i/templates/blank.gif" width="5" /&gt; At the login prompt, enter the CLI-admin username (admin is the default) that you configured during setup and press &lt;B class="cBold"&gt; Enter&lt;/B&gt; .&lt;/P&gt;&lt;P class="pSN_StepNext"&gt;&lt;B&gt;Step 4&lt;/B&gt;&lt;IMG alt="" border="0" height="2" src="http://www.cisco.com/c/dam/en/us/td/i/templates/blank.gif" width="5" /&gt; At the password prompt, enter the CLI-admin password that you configured during setup (this is user-defined and there is no default) and press &lt;B class="cBold"&gt; Enter&lt;/B&gt; .&lt;/P&gt;</description>
      <pubDate>Wed, 20 Aug 2014 23:26:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/2546892#M73451</guid>
      <dc:creator>Ravi Singh</dc:creator>
      <dc:date>2014-08-20T23:26:21Z</dc:date>
    </item>
    <item>
      <title>By default the shell is</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/2546893#M73454</link>
      <description>&lt;P&gt;By default the shell is locked down and you don't have access to it outside of a few "cisco like" commands and some ISE related commands. If you want more than that you will need to install a "root patch" that can be provided by Cisco TAC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM style="color: rgb(119, 119, 119); font-size: 14px; background-color: rgb(247, 247, 247);"&gt;Thank you for rating helpful posts!&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Aug 2014 15:57:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/2546893#M73454</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2014-08-21T15:57:41Z</dc:date>
    </item>
    <item>
      <title>You cannot!</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/2546894#M73455</link>
      <description>&lt;P&gt;You cannot!&lt;/P&gt;</description>
      <pubDate>Fri, 22 Aug 2014 00:24:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/2546894#M73455</guid>
      <dc:creator>Saurav Lodh</dc:creator>
      <dc:date>2014-08-22T00:24:12Z</dc:date>
    </item>
    <item>
      <title>No.  Not unless allowed admin</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/2546895#M73456</link>
      <description>&lt;P&gt;No.&amp;nbsp; Not unless allowed admin access and ability to install additional software.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Aug 2014 10:45:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/2546895#M73456</guid>
      <dc:creator>Venkatesh Attuluri</dc:creator>
      <dc:date>2014-08-22T10:45:30Z</dc:date>
    </item>
    <item>
      <title>Re: You cannot!</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/3815179#M73457</link>
      <description>&lt;P&gt;All you need to do is boot from a Linux disc and do the following:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*root the VM's with redhat disc*&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.rootusers.com/how-to-reset-root-user-password-in-centos-rhel-7/" target="_blank" rel="noopener"&gt;https://www.rootusers.com/how-to-reset-root-user-password-in-centos-rhel-7/&lt;/A&gt;&lt;BR /&gt;&amp;amp;&lt;BR /&gt;&lt;A href="https://www.rootusers.com/red-hat-certified-system-administrator-rhcsa-ex200-passed/" target="_blank" rel="noopener"&gt;https://www.rootusers.com/red-hat-certified-system-administrator-rhcsa-ex200-passed/&lt;/A&gt;&lt;BR /&gt;~~~&lt;BR /&gt;Boot off Centos/rhel disc&lt;BR /&gt;Press 1 for single user mode&lt;BR /&gt;# chroot /mnt/sysimage&lt;BR /&gt;# passwd root&lt;/P&gt;
&lt;P&gt;! set a password now.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;! allow root login with ssh so you can login with ssh after rebooting.&lt;BR /&gt;# vi /etc/ssh/sshd_config - remove hash on "#PermitRootLogin yes" or if "PermitRootLogin no" make it&amp;nbsp; "PermitRootLogin yes"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;! if Cisco ACS 5.x - you can reboot now.&lt;/P&gt;
&lt;P&gt;# exit - exit chrooted env&lt;BR /&gt;# touch /.autorelabel&lt;/P&gt;
&lt;P&gt;# reboot&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;! if ISE - set /etc/shadow to read-only.&lt;/P&gt;
&lt;P&gt;# chattr +i /etc/shadow&lt;/P&gt;
&lt;P&gt;# exit - exit chrooted env&lt;BR /&gt;# touch /.autorelabel&lt;/P&gt;
&lt;P&gt;# reboot &lt;BR /&gt;~~~&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2019 19:37:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/3815179#M73457</guid>
      <dc:creator>alextomko</dc:creator>
      <dc:date>2019-03-06T19:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: You cannot!</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/3816705#M73458</link>
      <description>&lt;P&gt;This is not something that anyone should be doing on an ISE deployment, and it won't enable a user to access root or the linux shell. ISE leverages something called ADE-OS which sits on top of RHEL. As indicated by nspasov, you access the underlying Linux CLI via TAC and the root key/root patch. This is not something Cisco provides for end user use, it is only used by TAC during troubleshooting to fix advanced issues. So even if you edit the root password, you need the root key that expires frequently, and the root patch that will work on your version.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It's also a 5 year old thread, no need to bump this.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 09 Mar 2019 09:01:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/3816705#M73458</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-03-09T09:01:46Z</dc:date>
    </item>
    <item>
      <title>Re: You cannot!</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/3871983#M73459</link>
      <description>&lt;P&gt;It works fine and then you can simply ssh in as root and get into bash and or then create more usernames by un-chattering /etc/shadow with chattr -i /etc/shadow. Then edit your /etc/sudoers and allow your other user-id's to do paswordless sudo commands "newuser ALL=(ALL) NOPASSWD:ALL".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However if you reboot without setting /etc/shadow back to read-only it will reset the root so all that is required is to chattr +i /etc/shadow again if you need to make user-id changes. If Cisco would fix simple things like SSH ciphers and provide a way for SSH public key then something like this would not be required.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You are correct it should not be done in a production environment but for lab purposes there is no harm.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2019 19:49:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/3871983#M73459</guid>
      <dc:creator>alextomko</dc:creator>
      <dc:date>2019-06-12T19:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: You cannot!</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/4894906#M583125</link>
      <description>&lt;P&gt;The classical way of replacing "!!" in shadow with no characters works too. The advice/recommendation "DO NOT EMULATE AT HOME/AT WORK" still applies.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jul 2023 13:45:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-get-into-linux-shell-on-cisco-ise-1-2/m-p/4894906#M583125</guid>
      <dc:creator>Gioacchino</dc:creator>
      <dc:date>2023-07-28T13:45:32Z</dc:date>
    </item>
  </channel>
</rss>

