So, I was doing something stupid in debian. Going with the testing branch for a few files, and had an issue.
Setting up runit (2.1.1-6) ...
dpkg: error processing runit (--configure):
subprocess installed post-installation script returned error exit status 10
Errors were encountered while processing:
runit
How to fix? Easy.
Delete /var/lib/dpkg/info/runit* and /var/cache/apt/archives/runit* and it works fine.
I actually moved the files first, just to verify it.
and to get the list I did this.
ls /var/cache/apt/archives/ |grep runit >> /root/info
ls list screen |grep (search) the files that i am looking for, >> append it to this file. So I can look thru it later.
Primarily where I write my fixes to things, that I can foresee needing again. InfoSec / Linux stuff.
Monday, November 15, 2010
Wednesday, November 03, 2010
Debian 5.0 Grub issues I was having.
Debian showed grub was installed, but I still had to use a cd to boot to it, I was a bit confused. So what I did was
fdisk /dev/sda (boot drive)
p to show a list of partitions. I could see that my only partition was non-bootable,
a added boot options,
w save and exit. Machine booted right up. Now to fix my X issues.
Debian showed grub was installed, but I still had to use a cd to boot to it, I was a bit confused. So what I did was
fdisk /dev/sda (boot drive)
p to show a list of partitions. I could see that my only partition was non-bootable,
a added boot options,
w save and exit. Machine booted right up. Now to fix my X issues.
Tuesday, September 14, 2010
I was curious with the new Blackberry 9300, what was the difference between it and the 8520, other than 3G and GPS. Found out the cpu's are different. and the 9300 supports Wifi N.
8520: 512MHz
9300: 624 MHz, Even better I have the exact chip. Marvell PXA930
I have a spare 8520 that I am supposed to send back this week. But I just got a copy of the 9300 BB os 6.0, So I am going to load it, and see.
8520: 512MHz
9300: 624 MHz, Even better I have the exact chip. Marvell PXA930
I have a spare 8520 that I am supposed to send back this week. But I just got a copy of the 9300 BB os 6.0, So I am going to load it, and see.
Wednesday, September 08, 2010
Say you are running 64 bit Windows, and you install OpenVPN, and someone gives you a script that keeps failing. You can't figure it out. I will post an example, and show you the issue I was having.
##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server. #
# #
# This configuration can be used by multiple #
# clients, however each client should have #
# its own cert and key files. #
# #
# On Windows, you might want to rename this #
# file so it has a .ovpn extension #
##############################################
client
dev tap
proto udp
remote vpn.example.com 1194
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
pkcs12 "C:\\Program Files\\OpenVPN\\config\\foo.pfx"
reneg-sec 0
comp-lzo
verb 3
mute 20
#####
Ok, Heres where the problem lies.
pkcs12 "C:\\Program Files\\OpenVPN\\config\\foo.pfx"
Needs to be changed to
pkcs12 "C:\\Program Files (x86)\\OpenVPN\\config\\foo.pfx"
The (x86) makes all the difference in the world.
##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server. #
# #
# This configuration can be used by multiple #
# clients, however each client should have #
# its own cert and key files. #
# #
# On Windows, you might want to rename this #
# file so it has a .ovpn extension #
##############################################
client
dev tap
proto udp
remote vpn.example.com 1194
resolv-retry infinite
nobind
persist-key
persist-tun
remote-cert-tls server
pkcs12 "C:\\Program Files\\OpenVPN\\config\\foo.pfx"
reneg-sec 0
comp-lzo
verb 3
mute 20
#####
Ok, Heres where the problem lies.
pkcs12 "C:\\Program Files\\OpenVPN\\config\\foo.pfx"
Needs to be changed to
pkcs12 "C:\\Program Files (x86)\\OpenVPN\\config\\foo.pfx"
The (x86) makes all the difference in the world.
Saturday, August 28, 2010
IPADDR_START=216.73.xxx.xxx
IPADDR_END=216.73.xxx.xxx
CLONENUM_START=0
NETMAST=255.255.255.0
Name file ifcfg-eth0-range0 (or whatever the nic card is)
Also The start IP address is the 2nd ip address in the list, the End is the last of them.
Yes I stole this script/borrowed from Calpop. Actually one of the most useful things I got out of there.
IPADDR_END=216.73.xxx.xxx
CLONENUM_START=0
NETMAST=255.255.255.0
Name file ifcfg-eth0-range0 (or whatever the nic card is)
Also The start IP address is the 2nd ip address in the list, the End is the last of them.
Yes I stole this script/borrowed from Calpop. Actually one of the most useful things I got out of there.
Friday, August 27, 2010
Scripts that come in handy.
Server e-mail every time someone logs in as root
To have the server e-mail you every time someone logs in as root, SSH into server and login as root.
At command prompt type: vi .bash_profile
Scroll down to the end of the file and add the following line:
echo 'ALERT - Root Shell Access on:' `date` `who` | mail -s "Alert: Root Access from `who | awk '{print $6}'`" your@email.com
Save and exit.
Install chkrootkit
To install chrootkit, SSH into server and login as root.
At command prompt type: cd /root/
At command prompt type: wget ftp://ftp.pangeia.com.br/pub/seg/pac/chkrootkit.tar.gz
At command prompt type: tar xvzf chkrootkit.tar.gz
At command prompt type: cd chkrootkit-0.44
At command prompt type: make sense
To run chkrootkit
At command prompt type: /root/chkrootkit-0.44/chkrootkit
Make sure you run it on a regular basis, perhaps including it in a cron job.
Chkrootkit is a program that scans for root kits.
To modify LogWatch, SSH into server and login as root.
At command prompt type: vi /etc/log.d/conf/logwatch.conf
Scroll down to
MailTo = root
and change to
Mailto = your@email.com
Note: Set the e-mail address to an offsite account incase you get hacked.
Now scroll down to
Detail = Low
Change that to Medium, or High...
Detail = 5 or Detail = 10
Note: High will give you more detailed logs with all actions.
Server e-mail every time someone logs in as root
To have the server e-mail you every time someone logs in as root, SSH into server and login as root.
At command prompt type: vi .bash_profile
Scroll down to the end of the file and add the following line:
echo 'ALERT - Root Shell Access on:' `date` `who` | mail -s "Alert: Root Access from `who | awk '{print $6}'`" your@email.com
Save and exit.
Install chkrootkit
To install chrootkit, SSH into server and login as root.
At command prompt type: cd /root/
At command prompt type: wget ftp://ftp.pangeia.com.br/pub/seg/pac/chkrootkit.tar.gz
At command prompt type: tar xvzf chkrootkit.tar.gz
At command prompt type: cd chkrootkit-0.44
At command prompt type: make sense
To run chkrootkit
At command prompt type: /root/chkrootkit-0.44/chkrootkit
Make sure you run it on a regular basis, perhaps including it in a cron job.
Chkrootkit is a program that scans for root kits.
To modify LogWatch, SSH into server and login as root.
At command prompt type: vi /etc/log.d/conf/logwatch.conf
Scroll down to
MailTo = root
and change to
Mailto = your@email.com
Note: Set the e-mail address to an offsite account incase you get hacked.
Now scroll down to
Detail = Low
Change that to Medium, or High...
Detail = 5 or Detail = 10
Note: High will give you more detailed logs with all actions.
Subscribe to:
Posts (Atom)