Skip to main content

Installing Cisco Secure ACS 5.3 in VirtualBox


ACS 5.3 is supported on a hardware appliance, VMWare ESX and VMWare Server. Even though not supported, it works without modification in VMWare Player. None of the above helps us if we want to test it with switches or routers in GNS3. While version 5.2 could be installed in VirtualBox, v5.3 consistently failed installation with “Unsupported hardware” error message. After trying all possible combinations of virtual hardware in VBox it still refused to install. After some hacking I eventually managed to get working.

Installation requires modification of the ISO image provided by Cisco and a bit of cheating in the kickstart file and pre-creation of partitions in the VM. We will need ISO editor (ISOpen or MagicISO), text editor (such as Notepad++) and a Linux live CD of your choice.

VBox hardware configuration:
OS Type: RedHat
RAM: 1024
CPU: PAE/NX enabled, VT-x/AMD-V disabled
Floppy: Disabled
Storage: Disk 70GB (I used dynamically expanded), Controller SCSI, SCSI Port 0
Audio: disabled
Network: Adapter Intel PRO/1000 MT
Serial Ports & USB: Disabled

All remaining settings stay at defaults.
Now we need to modify the kickstart file – ks.cfg – found in the root of the installation disk.

Red color shows old values and blue new ones. 

Change 0 to 1 on line 36

36: VM_APPLIANCE=01

Delete line 54
54:   UDI_PID=`/sbin/cars_udi_util -p`

Set variable “ret” to 0

56:   ret="$?"0

Delete lines 57 to 61 inclusive

57: if [ "$ret" -eq 0 ]; then
58:   echo "***** Cisco UDI PID: $UDI_PID " > /dev/console
59:     case $UDI_PID in
60:       Cisco-VM-SPID)
61:         VM_APPLIANCE=1

Delete –all from line 104

104:             echo "#clearpart --all --initlabel";

Delete lines 186 to 195 inlcusive

186:   else
187:       echo "***** Error: Unsupported Hardware Configuration. " > /dev/console
188:       echo "*****        This software can only be installed on Cisco " > /dev/console
189:       echo "*****        supported hardware or Virtual Machine technology " > /dev/console
190:       echo "*****        meeting the requirements specified in the installation guide." > /dev/console
191:       echo "*****        Exiting Installation..." > /dev/console
192:       sleep 5
193:       /sbin/halt -f
194:       exit 0
195:   fi

Save the file, and replace the existing ks.cfg in the ISO image.  When saving the edited ISO make sure the it is still bootable (ISOopen shows if the disk is bootable in the main UI).

Edited ks.cfg file can be downloaded here: http://www.filefactory.com/file/a322ga9ez05/n/ks.cfg

If we try the installation with our edited ISO we’ll get further than before, the install will still fail though.
Now we need to create partitions on the disk we’ll be installing ACS to.
Boot the VM to a Live Linux distro of your choice, create 2GB partition /sda1 and format it as ext3.
Now we should be able to install ACS. Simply boot the edited installation disk and follow the prompts. 

When booting ACS sits on "ip_contract" for a few minutes so be patient it will eventually boot.

Comments

Popular posts from this blog

x.509 Certificates - Critical vs non-critical extensions

Extensions are used to associate additional information with the user or the key.  Each certificate extension has three attributes - extnID, critical, extnValue extnID - Extension ID - an OID that specifies the format and definitions of the extension critical - Critical flag - Boolean value extnValue - Extension value  Criticality flag specifies whether the information in an extension is important. If an application doesn't recognize the extension marked as critical, the certificate cannot be accepted. If an extension is not marked as critical (critical value False) it can be ignored by an application. In Windows, critical extensions are marked with a yellow exclamation mark,  View certificate extensions using OpenSSL: # openssl x509 -inform pem -in cert.pem -text -noout (output abbreviated)         X509v3 extensions:             X509v3 Key Usage: critical                 Digital Signature, Key Encipherment             X509v3 Subject Key Identifier

DNS response and error types

In this post we explore common DNS response codes. We will cover the following responses: NOERROR SERVFAIL NXDOMAIN NODATA REFUSED Throughout article we’ll refer to the following RFCs: RFC 1034 - DOMAIN NAMES - CONCEPTS AND FACILITIES RFC 2308 - Negative Caching of DNS Queries (DNS NCACHE) RFC 2136 - Dynamic Updates in the Domain Name System (DNS UPDATE) RFC 8914 - Extended DNS Errors Response Codes - RCODEs The DNS RCODES are best defined in RFC2316 .  They signify what type of response was sent by the server. “RCODE   Response code - this four bit field is undefined in requests and set in responses.”   The table below shows the summary of the currently defined RCODEs. Mnemonic Val Description NOERROR 0 No error condition.

DNS blocking in Indonesia

DNS based censorship and domain blocking in Indonesia is very inconsistent among ISPs. There’s a government mandated black list which the ISPs operating in the country should enforce. However, Indonesia lacks centralised internet infrastructure and has many separate ISPs. In addition, the Indonesian government granted ISPs the authority to block content at their own discretion. All of this leads to a very inconsistent DNS blocking in Indonesia. Official DNS domain blacklist in Indonesia The Government mandated DNS blacklist is published in a redacted form and can be downloaded here: https://trustpositif.kominfo.go.id/ . This is where the blocked domains get redirected to. We can search the database and check if a domain is blocked. In the screenshot below we can see that a popular cryptocurrency exchange is blocked (Ada) and that wikipedia.org is not (Tidak Ada) - thanks to Google Translate. Examples of blocked DNS queries dig binance.com @182.253.45.122 ;; global options: +cmd ;; Got