<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: How to get Root access on Call Manager 5/6 Server</title>
	<atom:link href="http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/</link>
	<description>Tips and Video Tutorials - Cisco .:. Linux .:. VOIP</description>
	<lastBuildDate>Mon, 08 Mar 2010 05:48:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Cisco CUCM/Call Manager &#8211; Running on Sun&#8217;s Virtual Box &#171; Kevsters Blog</title>
		<link>http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/comment-page-1/#comment-33242</link>
		<dc:creator>Cisco CUCM/Call Manager &#8211; Running on Sun&#8217;s Virtual Box &#171; Kevsters Blog</dc:creator>
		<pubDate>Tue, 02 Feb 2010 23:08:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/#comment-33242</guid>
		<description>[...] Next follow the guide here http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/ to get root access.  Make sure you use the CentOS Disk 1 rather than the Live [...]</description>
		<content:encoded><![CDATA[<p>[...] Next follow the guide here <a href="http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/ to" rel="nofollow">http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/ to</a> get root access.  Make sure you use the CentOS Disk 1 rather than the Live [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amit</title>
		<link>http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/comment-page-1/#comment-33191</link>
		<dc:creator>Amit</dc:creator>
		<pubDate>Thu, 21 Jan 2010 16:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/#comment-33191</guid>
		<description>I am new to Linux
I am tring to edit /usr/local/bin/base_scripts/hardware_check.sh file but I am getting error saying read only file,
can any one help me with?</description>
		<content:encoded><![CDATA[<p>I am new to Linux<br />
I am tring to edit /usr/local/bin/base_scripts/hardware_check.sh file but I am getting error saying read only file,<br />
can any one help me with?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Holloway &#187; Blog Archive &#187; Unified Communications Manager 7.1(3) in VMWare</title>
		<link>http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/comment-page-1/#comment-32903</link>
		<dc:creator>Mark Holloway &#187; Blog Archive &#187; Unified Communications Manager 7.1(3) in VMWare</dc:creator>
		<pubDate>Wed, 18 Nov 2009 19:18:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/#comment-32903</guid>
		<description>[...] access its underlying Linux operating system and obtain root access.  There are known methods to bypass this.  If you have already found a way, then you may configure the virtual machine such as CUPS [...]</description>
		<content:encoded><![CDATA[<p>[...] access its underlying Linux operating system and obtain root access.  There are known methods to bypass this.  If you have already found a way, then you may configure the virtual machine such as CUPS [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Salman</title>
		<link>http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/comment-page-1/#comment-27846</link>
		<dc:creator>Salman</dc:creator>
		<pubDate>Wed, 18 Mar 2009 12:25:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/#comment-27846</guid>
		<description>Thanks Pushkar for sharing this, that worked.

salman</description>
		<content:encoded><![CDATA[<p>Thanks Pushkar for sharing this, that worked.</p>
<p>salman</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Martyn</title>
		<link>http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/comment-page-1/#comment-26990</link>
		<dc:creator>David Martyn</dc:creator>
		<pubDate>Tue, 03 Mar 2009 13:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/#comment-26990</guid>
		<description>I have tested this link and it works like a charm.

I am a big fan of Pushkar Bhatkoti&#039;s blog.

Link:  
http://pushkarbhatkoti.wordpress.com/2009/01/25/a-fun-with-cisco-call-manager-6x-how-to-root-access-to-ccm6x-box/

Topic: 
A fun with Cisco Call manager 6x - root access to CCM6x box

cut and paste:

January 25, 2009 at 3:55 am &#124; In CCM 5x 6x 7x stuffs &#124; &#124; Edit this post
Tags: hacking cisco call manager 6x, how to get root access to ccm ccm6x ccm7x, logging in as a root in cisco call manager

———————————————————————————————-
Duh… its 42 degree outside here in Sydney and it is also a long weekend - this sounds boreing… nothing to do outdoor.
My mind got crazy and then I thought to play with my new toy - CCM  version 6.x.
Note: before you read this please note, do not try to apply it on your production server.
Quite often, when we are working on the production server and we need access to call manager 5x 6x 7x root shell (penguin shell), we had to call bloody TAC and do wait for ages before we get access to the root shell.
Last week this happend to my friend and he told me that is there anyway to get access to the call manager root shell. He upgraded his CCM from v5 to 6x and the disk space got on ccm server got full. So he had to delete some files from ccm using LINUX shell. Somehow cisco has managed to lock it down so that no root access to the ccm appliance. I given my old method to my friend and he got access to the root shell [grub /lilo breakin method like we do to recover root password].

Today I got some time to do some research on this and found out a less effort method which you can safely apply to your production server without breaking anything related to Cisco’s software.

So using below method you would be able to access your call manager in the same fashion like TAC guys do. You don’t have to call them and wait…hehhe…

download fedora9, redhat linux 4 or above or centos disk1. burn it on a CD or dvd. this disk iwll be used in the step #3

STEP#1: Create remote account on your CUCM.
———————————————————–
ssh to your CUCM box. I use Ubuntu as a desktop, if you are billy fane you can use ssh or secureCRT.

frog# ssh administrator@142.2.64.254

you’ll get below prompt:

admin:

create a account and enable remote account to this box:

admin:utils remote_account create frog  100
admin:utils remote_account enable

noticed 100 in the above is number of days ‘frog’ username / account will be valid. If you want it forever, then just type 0

STEP#2: reboot the server:
———————————-
admin:utils system restart

STEP#3: create password for ‘frog’ remote user
———————————————————-

While server reboots, pop-in a linux booteble disk (downloaded centos or redhat first disk) to MCS server or your lab toy. When you see boot prompt type ‘linux rescue:

boot:linux rescue

That will give you the root shell access of root#

initblah#

Rescue disk mounts the CCM hard disk image as a /mnt/sysimage. Now chroot to this image to change in the /etc/ files or passwords:

#chroot /mnt/sysimage

[root#ccm-] #

Note1: if you dont’ see the root prompt and /etc/pass file, then you may need to mount your sysimage.

Note2: If you are Opensource folk and know how to penguinworks u can jump direct to step#4. Actually adding user here vs adding them when u get root# shell using a booteble CD, is that u don’t have to apply all admin groups to remote user.

according to the one of the hacker wesite, remote user must be a member of the following groups in CCM BOX:

disk, sys, adm, bin, wheel and root

STEP#4: change attribute of /etc files and create ‘frog’ user’s password:
—————————————————————————————
Cisco have locked the attribute to read only to all /etc/passwd /etc/group /etc/shadow and /etc/gshadow file to protect those files.

Make all of below files attribute from read only to read/write. So when you change ‘frog’ users password the system will let you change it.

root#chattr -i /etc/passwd
root#chattr -i /etc/shadow
root#chattr -i /etc/group
root#chattr -i /etc/gshadow

root#passwd frog 

Now restart the server: use reboot command

Dont’ forget to remove your DVD/CD from MCS server.
Once that is done, access to the ccm from your favourite ssh client. mine is ubuntu these days.

frog# ssh frog@142.2.64.254

Welcome to Remote Support

[root@CUCM6~]#
[root@CUCM6~]#
[root@CUCM6~]#

hehe… its your little linux box now. Do with it whatever you like. I will install freeRADIUS and some other cool tool like NMAP on this Cisco box.</description>
		<content:encoded><![CDATA[<p>I have tested this link and it works like a charm.</p>
<p>I am a big fan of Pushkar Bhatkoti&#8217;s blog.</p>
<p>Link:<br />
<a href="http://pushkarbhatkoti.wordpress.com/2009/01/25/a-fun-with-cisco-call-manager-6x-how-to-root-access-to-ccm6x-box/" rel="nofollow">http://pushkarbhatkoti.wordpress.com/2009/01/25/a-fun-with-cisco-call-manager-6x-how-to-root-access-to-ccm6x-box/</a></p>
<p>Topic:<br />
A fun with Cisco Call manager 6x &#8211; root access to CCM6x box</p>
<p>cut and paste:</p>
<p>January 25, 2009 at 3:55 am | In CCM 5x 6x 7x stuffs | | Edit this post<br />
Tags: hacking cisco call manager 6x, how to get root access to ccm ccm6x ccm7x, logging in as a root in cisco call manager</p>
<p>———————————————————————————————-<br />
Duh… its 42 degree outside here in Sydney and it is also a long weekend &#8211; this sounds boreing… nothing to do outdoor.<br />
My mind got crazy and then I thought to play with my new toy &#8211; CCM  version 6.x.<br />
Note: before you read this please note, do not try to apply it on your production server.<br />
Quite often, when we are working on the production server and we need access to call manager 5x 6x 7x root shell (penguin shell), we had to call bloody TAC and do wait for ages before we get access to the root shell.<br />
Last week this happend to my friend and he told me that is there anyway to get access to the call manager root shell. He upgraded his CCM from v5 to 6x and the disk space got on ccm server got full. So he had to delete some files from ccm using LINUX shell. Somehow cisco has managed to lock it down so that no root access to the ccm appliance. I given my old method to my friend and he got access to the root shell [grub /lilo breakin method like we do to recover root password].</p>
<p>Today I got some time to do some research on this and found out a less effort method which you can safely apply to your production server without breaking anything related to Cisco’s software.</p>
<p>So using below method you would be able to access your call manager in the same fashion like TAC guys do. You don’t have to call them and wait…hehhe…</p>
<p>download fedora9, redhat linux 4 or above or centos disk1. burn it on a CD or dvd. this disk iwll be used in the step #3</p>
<p>STEP#1: Create remote account on your CUCM.<br />
———————————————————–<br />
ssh to your CUCM box. I use Ubuntu as a desktop, if you are billy fane you can use ssh or secureCRT.</p>
<p>frog# ssh <a href="mailto:administrator@142.2.64.254">administrator@142.2.64.254</a></p>
<p>you’ll get below prompt:</p>
<p>admin:</p>
<p>create a account and enable remote account to this box:</p>
<p>admin:utils remote_account create frog  100<br />
admin:utils remote_account enable</p>
<p>noticed 100 in the above is number of days ‘frog’ username / account will be valid. If you want it forever, then just type 0</p>
<p>STEP#2: reboot the server:<br />
———————————-<br />
admin:utils system restart</p>
<p>STEP#3: create password for ‘frog’ remote user<br />
———————————————————-</p>
<p>While server reboots, pop-in a linux booteble disk (downloaded centos or redhat first disk) to MCS server or your lab toy. When you see boot prompt type ‘linux rescue:</p>
<p>boot:linux rescue</p>
<p>That will give you the root shell access of root#</p>
<p>initblah#</p>
<p>Rescue disk mounts the CCM hard disk image as a /mnt/sysimage. Now chroot to this image to change in the /etc/ files or passwords:</p>
<p>#chroot /mnt/sysimage</p>
<p>[root#ccm-] #</p>
<p>Note1: if you dont’ see the root prompt and /etc/pass file, then you may need to mount your sysimage.</p>
<p>Note2: If you are Opensource folk and know how to penguinworks u can jump direct to step#4. Actually adding user here vs adding them when u get root# shell using a booteble CD, is that u don’t have to apply all admin groups to remote user.</p>
<p>according to the one of the hacker wesite, remote user must be a member of the following groups in CCM BOX:</p>
<p>disk, sys, adm, bin, wheel and root</p>
<p>STEP#4: change attribute of /etc files and create ‘frog’ user’s password:<br />
—————————————————————————————<br />
Cisco have locked the attribute to read only to all /etc/passwd /etc/group /etc/shadow and /etc/gshadow file to protect those files.</p>
<p>Make all of below files attribute from read only to read/write. So when you change ‘frog’ users password the system will let you change it.</p>
<p>root#chattr -i /etc/passwd<br />
root#chattr -i /etc/shadow<br />
root#chattr -i /etc/group<br />
root#chattr -i /etc/gshadow</p>
<p>root#passwd frog </p>
<p>Now restart the server: use reboot command</p>
<p>Dont’ forget to remove your DVD/CD from MCS server.<br />
Once that is done, access to the ccm from your favourite ssh client. mine is ubuntu these days.</p>
<p>frog# ssh <a href="mailto:frog@142.2.64.254">frog@142.2.64.254</a></p>
<p>Welcome to Remote Support</p>
<p>[root@CUCM6~]#<br />
[root@CUCM6~]#<br />
[root@CUCM6~]#</p>
<p>hehe… its your little linux box now. Do with it whatever you like. I will install freeRADIUS and some other cool tool like NMAP on this Cisco box.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hochwald.net</title>
		<link>http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/comment-page-1/#comment-16792</link>
		<dc:creator>hochwald.net</dc:creator>
		<pubDate>Thu, 09 Oct 2008 09:12:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/#comment-16792</guid>
		<description>&lt;strong&gt;Root Access auf einem Cisco CallManager 6.x bekommen...&lt;/strong&gt;

Ich habe mir vor einiger Zeit zum testen einen Cisco CallManager 6 installiert. Da ich Blackboxen nicht leiden kann, habe ich versucht ob es nicht möglich ist einen richtigen Shell Access hinzubekommen&#8230;
......</description>
		<content:encoded><![CDATA[<p><strong>Root Access auf einem Cisco CallManager 6.x bekommen&#8230;</strong></p>
<p>Ich habe mir vor einiger Zeit zum testen einen Cisco CallManager 6 installiert. Da ich Blackboxen nicht leiden kann, habe ich versucht ob es nicht möglich ist einen richtigen Shell Access hinzubekommen&#8230;<br />
&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: keli</title>
		<link>http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/comment-page-1/#comment-16771</link>
		<dc:creator>keli</dc:creator>
		<pubDate>Wed, 08 Oct 2008 21:09:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/#comment-16771</guid>
		<description>Robert, your procedure was failing exactly because you did not chroot to the CCM partition.

Though the workaround you found is just as fine.</description>
		<content:encoded><![CDATA[<p>Robert, your procedure was failing exactly because you did not chroot to the CCM partition.</p>
<p>Though the workaround you found is just as fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/comment-page-1/#comment-13585</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Thu, 14 Aug 2008 04:34:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/#comment-13585</guid>
		<description>Robert,

Thanks for sharing your notes with us! I really enjoy seeing someone take another approach. Great job!

Please try to find the author of the above procedure. I would like to give credit.

Josh</description>
		<content:encoded><![CDATA[<p>Robert,</p>
<p>Thanks for sharing your notes with us! I really enjoy seeing someone take another approach. Great job!</p>
<p>Please try to find the author of the above procedure. I would like to give credit.</p>
<p>Josh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/comment-page-1/#comment-13584</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 14 Aug 2008 03:44:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/#comment-13584</guid>
		<description>ok...I figured this out!!!

When doing &quot;adduser&quot; I was actually adding it to the liveCD version!  in other words, I was modifying /etc/passwd, group, shadow, gshadow, etc when doing the &quot;adduser&quot; command.

So, I opened up those files in a text editor, then opened up /media/disk/etc/passwd..etc and copied/pasted the new user info.

also, when doing sudo visudo sudoers, I had to use the -f flag to look to the local command line otherwise, I was also editing /etc/sudoers (my liveCD filesystem)

i.e: ubuntu@ubuntu:/media/disk/etc$ sudo visudo -f sudoers

also, note:  I noticed that I did not have access via Konsole to /media/disk until I opened it up in Dolphin (the file manager)...not sure if I tried to quickly or not, but...if anyone else does this...there ya go.

So...thanks for pointing me in the right way..hopefully, my notes can be of assistance to someone.</description>
		<content:encoded><![CDATA[<p>ok&#8230;I figured this out!!!</p>
<p>When doing &#8220;adduser&#8221; I was actually adding it to the liveCD version!  in other words, I was modifying /etc/passwd, group, shadow, gshadow, etc when doing the &#8220;adduser&#8221; command.</p>
<p>So, I opened up those files in a text editor, then opened up /media/disk/etc/passwd..etc and copied/pasted the new user info.</p>
<p>also, when doing sudo visudo sudoers, I had to use the -f flag to look to the local command line otherwise, I was also editing /etc/sudoers (my liveCD filesystem)</p>
<p>i.e: ubuntu@ubuntu:/media/disk/etc$ sudo visudo -f sudoers</p>
<p>also, note:  I noticed that I did not have access via Konsole to /media/disk until I opened it up in Dolphin (the file manager)&#8230;not sure if I tried to quickly or not, but&#8230;if anyone else does this&#8230;there ya go.</p>
<p>So&#8230;thanks for pointing me in the right way..hopefully, my notes can be of assistance to someone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/comment-page-1/#comment-13579</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 14 Aug 2008 02:20:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.blindhog.net/how-to-get-root-access-on-call-manager-56-server/#comment-13579</guid>
		<description>ps...yes, I copied and pasted all of the instructions for the vmware stuff from another place on the net. I wish I could give credit...but..I just closed out all my browsers.

My apologies to the original poster on that!</description>
		<content:encoded><![CDATA[<p>ps&#8230;yes, I copied and pasted all of the instructions for the vmware stuff from another place on the net. I wish I could give credit&#8230;but..I just closed out all my browsers.</p>
<p>My apologies to the original poster on that!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
