|
ru.cisco- RU.CISCO --------------------------------------------------------------------- From : Slawa Olhovchenkov 2:5030/500 09 Jul 2007 14:27:24 To : All Subject : pix/asa 8.0 & linux -------------------------------------------------------------------------------- Open Source Software Licenses for ASA and PIX Security Appliances http://www.cisco.com/en/US/products/ps6120/prod_release_note09186a008086944e.htm l === the 8.0.2 release is linux based (2.6 kernel) on the ASA platform. On the PIX platform 8.0.2 is still finesse baesd. === This is from a Cisco presentation "There are many features and applications that Linux can provide which are difficult for us to take advantage of running the current Finesse OS on the ASA platform. For that reason we have decided to pursue running on top of a Linux kernal on ASA and future hardware." === Hello, I decided to register here after discovering that Cisco's ASA 8.0 code is Linux based. I did some investigating last week and confirmed that the ASA 8.0(2) image is running on top of a Linux kernel. A google search revealed this forum and not much else. My goal is to ensure that Cisco complies with the GNU GPL and releases it's source code modifications. Scanning through the ASA image file with hexdump I found many strings showing that the ASA is clearly Linux based. Running 'show kernel process' on the ASA confirms this. I requested that Cisco provide me with modifications to the source code as they are obligated to by the GPL. Cisco replied to me that they have not made any modifications on any open source GPL software. I found this a bit hard to believe so I decided to experiment with extracting the kernel and file system to look for proof that they have indeed modified GPL code. After playing around with the image for a couple of hours this morning I found a few gzip headers [1F 8B 08] embedded within it. The first one begins at offset 1228A8+8. I extracted this with dd if=asa802-k8.bin of=extract.gz bs=1 skip=1190064 and gunzip'd it. The extracted file appears to be a CPIO archive. I then proceed to extract the cpio archive which contains the a root file system and kernel. Code: # ls -la total 1664 drwxr-xr-x 14 root root 1024 Jul 6 16:23 . drwxr-xr-x 24 root root 4096 Jun 11 08:47 .. drwxr-xr-x 4 root root 1024 Jul 6 16:10 asa drwxr-xr-x 2 root root 1024 Jul 6 16:23 bin drwxr-xr-x 3 root root 1024 Jul 6 16:23 dev drwxr-xr-x 3 root root 1024 Jul 6 16:23 etc lrwxrwxrwx 1 root root 7 Jul 6 16:23 init -> linuxrc drwxr-xr-x 3 root root 1024 Jul 6 16:23 lib drwx------ 3 root root 1024 Jul 6 16:10 lina-data lrwxrwxrwx 1 root root 11 Jul 6 16:23 linuxrc -> bin/busybox drwx------ 2 root root 12288 Jul 6 16:10 lost+found drwxr-xr-x 4 root root 1024 Jul 6 16:10 mnt drwxr-xr-x 2 root root 1024 Jul 6 16:10 proc drwxr-xr-x 2 root root 1024 Jul 6 16:23 sbin drwxr-xr-x 2 root root 1024 Jul 6 16:10 sys -rw-r--r-- 1 root root 563896 Jul 6 16:23 System.map drwxr-xr-x 3 root root 1024 Jul 6 16:10 usr -rw-r--r-- 1 root root 1095856 Jul 6 16:23 vmlinuz I then created a disk image and a partition to extract these files to. I was able to successfully load the kernel in qemu where it began executing the init scripts followed quickly by a stack trace and restart. This is about as far as I am at the moment. I am not too interested in running the ASA in an emulated environment or virtual machine, however it is an interesting process dissecting the code. I hope the above helps you guys. Sorry for being so brief with the technical details, I can post more details later. Interestingly, the ASA appears to detect that it is not running on it's native hardware platform, here is a snapshot of the boot messages after the kernel has finished loading: Code: Processor memory 120926208, Reserved memory: 20971520 (DSOs: 0 + kernel: 20971520) Guest RAM start: 0xd7800080 Guest RAM end: 0xdd400000 LINA unit number: 1 Guest RAM brk: 0xd7801000 MKDIR failed No such file or directory for /var/log/ Welcome to LINA - ( F1-on-Linux platform ) desktop version! ******************************************************************** * WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING * * * * This product is for Cisco internal use ONLY!!! * * * * WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING * ******************************************************************** i2c_read_byte_w_wait() error, slot = 0x4, device = 0xb0, address = 0 byte count = 1. Reason: I2C_SMBUS_UNSUPPORT Total SSMs found: 0 Ignoring PCI card in slot:0 (vendor:0x0 deviceid:0x0) Ignoring PCI card in slot:1 (vendor:0x0 deviceid:0x0) Ignoring PCI card in slot:2 (vendor:0x0 deviceid:0x0) Ignoring PCI card in slot:3 (vendor:0x0 deviceid:0x0) Ignoring PCI card in slot:4 (vendor:0x0 deviceid:0x0) Ignoring PCI card in slot:5 (vendor:0x0 deviceid:0x0) Ignoring PCI card in slot:6 (vendor:0x0 deviceid:0x0) Total NICs found: 6 setup_irq: irq handler mismatch <de12e376> <de12eaa0> <de12e40a> <de12edb6> <de12eaa0> <de12ed40> <de148db3> <de149027> <de148984> <de14906e> <de149126> <de102a97> Unable to open /proc/irq/15/irq error: Device or resource busy Panic: kernel - intr_establish: open interupt descriptor irq 15 ==== ... Даже маленькая практика стоит большой теории --- GoldED+/BSD 1.1.5 * Origin: (2:5030/500) Вернуться к списку тем, сортированных по: возрастание даты уменьшение даты тема автор
Архивное /ru.cisco/222146920f1c.html, оценка из 5, голосов 10
|