Found a privilege escalation vulnerability in my i6000, version 617G.GS01001. Also figured out how to generate license keys. Notified them and have posts ready for in a month or so.
The config files and such in /usr/local/amc/app are all publicly accessible.
The HTML, JARs, and other web resources are hosted from /usr/local/amc/app.
Quick pointer: If you're using this for anything other than lab testing, well, you really shouldn't. If you've got to have someone tell you that such things are ethically and legally problematic, you're probably not a very good person anyway. Or just not thinking. Either way, think before you use this info.
Turns out that Quantum/ADIC helpfully includes the binary for generating license keys!
# IOB lookups, do not modify anything after this in the file
ilinkacc: $ cat /etc/exports
# See exports(5) for a description.
# This file contains a list of all directories exported to other computers.
# It is used by rpc.nfsd and rpc.mountd.
ilinkacc: $ cat /proc/cpuinfo
processor : 0
cpu : 440GP Rev. C
revision : 4.129 (pvr 4012 0481)
bogomips : 593.92
vendor : ADIC
machine : MCB
While looking through extaccess.conf I found this:
## Engineering mode, enable everything
Might be worth checking out.
After being powered off and unplugged for a few weeks the CAN issue that I'd been having with the i6000 seems to have resolved itself. However the LTO-6 tape drive/sled I have isn't powering up at all. IDK what's going on with that. The error is that the barcode on the drive isn't recognized. This is caused by the system not having the drive registered via the system bus. Which in this case is caused by the sled not powering up.