Just my Blog

Luckely I am not the only one facing troubles with Windows Vista:

During looking for the Knoppixremaster howto... I read somewhere about QEMU. So I start playing around with QEMU... and guess what... at a certain moment I had running:

• Gentoo (Host-system)
• Knoppix 5.1.1
• FreeBSD 6.1
• Windows XP SP2 installations

So this is really cool

Herakles is currently running for 6 days... so it is time to get a review of the bandwith consuming of the script. Down here you find the upstream graph with the total amount of gigabytes a day.

The yellow bars are the days when we still used the old script.
The Blue bar is the day that Herakles started with it's first initialisation.
The green bar indicates the days when Herakles did the normal rsync operations

So it works!

Yesterday evening I added some new features, so version 0.0.2 is born (still beta):

• STDIN output 1 & 2 are put into the $LOG_FILE
  
• Register the PID of the script in $LOCKFILE
  
• When script started, check if it is not already running by checking the existing of $LOCKFILE
  
• Use logger to log starting/stopping backup procedures in the system-log-files

But... there is more to come... some planned features:

• In the mainbackup-list $SRC_LIST semicolon seperated values for excluding information for that entry
  
• User specified backup policies, by reading .herakles-backup files in their home-dir.
  
• building every day a tar-file for retention (executed from the src-host).
  
• an installation script which installs stuff on the src and dst-host.

And far more fun to come!

The last time I am working on another way of making my backups. The current procedure is time-consuming and bandwith-eating.

Today I wrote the first version of the script. From this point it is a proof of concept using Rsync over SSH.

When I have some script for the big public, I will publish it at the Herakles site.

NOTE: The code is totally beta!!! So use it on your own risk!

There are different tools to make a forensic copy of a harddrive. So you have RDD, LinEn. LinEn is a tool written by Guidance to make images on a Linux system using EnCase. But to compare the stuff I did some testing stuff with a USB Memorystick of 512Meg. The results are shown below:

So as you can see... RDD is the fastest one!

Note:RDD is on a BSD-license... LinEn not!

On one of the networks I maintain, I had to roll-out a new SSL-certificate for the IMAP-SSL Services. The old certificate would expire within a few days. On this network the most users, uses MS Windows XP in combination with a samba-fileserver.

Some time ago, I roll-out the logon.bat stuff. Every user on the network has in his 'Startup' folder an LNK-file who calls a netlogon script on the server which take care of the next stuff:

• Remove all existing network-shares
• Connect the H-drive to their personal share on the server
• Connect the P-drive to the public-share on the server
• Resets, by injecting registry data, the Proxy-settings for IE

So I want to use this script to roll-out the new certificate... but it is not so easy on a Windows system
I needed a tool who was able to add a certificate from the commandline to the certificate-store.
After some search, I found the tool certutil.exe.

But getting certutil.exe was not so easy... it is part of the Windows 2k3 servers, but a 2k3 server isn't the problem So I copied the file and a dll out and placed it on the Samba server... added a line to the logon.bat

p:\network\bin\certutil.exe -addstore -f -user root p:\network\cert\new.cer

The users receive only the first time a security warning, with the question if they want to install the certificate...

and if they don't want to install the certificate... they won't have e-mail

Today I was working on a Windows system and on that windows system I wanted to connect via a SSH-tunnel to a RDP-server (another Windows system at my parents place). So I started putty with the command:

putty -L 3389:10.0.0.113:3389 username@remotehost.example.org

And after that... I want to 'Start' -> 'Run...' -> 'mstsc.exe' -> 'OK' Connect to 127.0.0.1 And guess what... the client refuses:


So after some Google work I found that I have to change the 'Compatibility mode' for mstsc.exe into 'Windows 98 / Windows ME'.

So I went to c:\windows\system32\mstsc.exe and guess what:


But after some other search work, I found that you have to copy mstsc.exe and mstscax.dll to some other path, after that you can change the compatibility modus: