skinnypup.com

So, your company has been acquired. If climbing inside an escape pod and jettisoning your self into deep space is not an option, here is a list of things to expect:

• An order will be made to lower your firewalls and surrender your servers.
• You will be assimilated.  Resistance will only slow the process down.
• Assimilation is a means of adding or replacing spent drones.
• The Borg have no feeling, no emotion, no individual thought.
• Each Borg is part of a giant subspace communications network called Exchange Server.
• All communication is transmitted to the entire Collective via a process entitled Carbon Copy.
• Your present function and title is irrelevant.
• Strength is irrelevant.
• Negotiation is irrelevant.
• Freedom is irrelevant.
• Self-determination is irrelevant.
• Your life as it had been is over.
• From this time forward, you will service them.
• Your culture will adapt to service them.
• They will add your biological and technological distinctiveness to their own.
• Resistance is, and always has been, futile.
• You will become one with the Borg.

UNIX Administrators: Saving servers from nefarious end-users since 1969.

Make sure kernel modules are present:
modprobe aes
modprobe dm-crypt
Create a 256 bit key file containing random data:
dd if=/dev/random of=/etc/key bs=1 count=256
chown root:root /etc/key
chmod 600 /etc/key
Initialize device:
cryptsetup –verbose -c aes-cbc-essiv:sha256 luksFormat /dev/sdb1 /etc/key
answer “YES” if you would like to overwrite data on /dev/sdb1 irrevocably
Create device mapping in /dev/mapper:
cryptsetup –key-file /etc/key luksOpen /dev/sdb1 sftpusers
Format partition:
mkfs.ext3 /dev/mapper/sftpusers
Add partition to /etc/fstab:
/dev/mapper/sftpusers /sftpusers ext3 defaults 0 0
Create/update /etc/crypttab with device info:
sftpusers /dev/sdb1 /etc/key

Reboot to verify that volume is mounted automatically. This configuration has been tested on Red Hat Enterprise Linux 5.

Done in order to satisfy a PCI compliance issue with VMware volume files. Files should be encrypted when not in use. Of course, this only ensures an encrypted virtual disk file at the ESX file system level. Credit card data inside the virtual drive still needs to be encrypted so that it is not accessible when the system is live.

Note: Exclude the key parts if you want an encrypted partion with prompt for password at boot.

Certificate is good for 1 year. 

1. switch to the same account that the SAProuter server runs as
2. stop the router service
3. backup the router folder
example: cp -rp saprouter saprouter.bak
4. change to the router home directory
5. rename certreq, srcert, local.pse, and cred_v2 to file.yyyymmdd
6. generate the certificate request (new certreq) using the following command:
sapgenpse get_pse –v –r certreq –p local.pse “CN=saprouter1, OU=0000350309, OU=SAProuter, O=SAP, C=DE”
do not enter a PIN (just press enter)
7. copy the contents of certreq to the clipboard
8. browse to http://www.service.sap.com/saprouter-sncadd
9. paste the contents of the clipboard into the form
10. step through form to generate new certificate information
11. copy and paste new certificate data into a file called srcert
11. import the certificate using the following command
./sapgenpse import_own_cert –c srcert –p local.pse
do not enter a PIN (press enter)
12. setup the login using the following command
sapgenpse seclogin –p local.pse
this will create a final file called cred_V2
13. check if the certificate has been loaded correctly by using the following command:
sapgenpse get_my_name –v –n Issuer
14. start the router service
15. delete backup router directory made in step 3 if it is no longer needed

CN and OU information will be different and based on the configuration for your company.

Procedure for Reseting IBM xSeries 445 RSA II Card:

• Connect loopback cable from RSAII to ETH1 on server. (RSA port is directly to the left of ETH1)
• Bring up ETH1:
  eth1 inet addr:192.168.70.120 Bcast:192.168.70.255 Mask:255.255.255.0
  DO NOT SET A GATEWAY
• telnet 192.168.70.125
• username: USERID password: PASSW0RD (0 = zero, not letter)
• enter “resetsp” at command prompt to reset controller
• controller will disconnect session and reset

Known problem with the x445 and the (42B)1.15 BIOS. Supposed to be fixed in the (45A) 1.17 BIOS update. Server will lockup every 76 days without updated BIOS, or controller reset.