Added various posts.
BIN
assets/codestar.ods
Normal file
BIN
assets/codestarooo.png
Normal file
After Width: | Height: | Size: 28 KiB |
BIN
assets/cskartenbildklein.gif
Normal file
After Width: | Height: | Size: 12 KiB |
BIN
assets/security_firewall.png
Normal file
After Width: | Height: | Size: 32 KiB |
BIN
assets/services_services.png
Normal file
After Width: | Height: | Size: 64 KiB |
BIN
assets/setup_advanced_routing.png
Normal file
After Width: | Height: | Size: 42 KiB |
BIN
assets/setup_basic_setup.png
Normal file
After Width: | Height: | Size: 76 KiB |
BIN
assets/setup_networking.png
Normal file
After Width: | Height: | Size: 40 KiB |
BIN
assets/wireless_advanced_settings.png
Normal file
After Width: | Height: | Size: 50 KiB |
BIN
assets/wireless_basic_settings.png
Normal file
After Width: | Height: | Size: 58 KiB |
BIN
assets/wireless_wds.png
Normal file
After Width: | Height: | Size: 34 KiB |
BIN
assets/wireless_wireless_security.png
Normal file
After Width: | Height: | Size: 50 KiB |
17
know-how/software/_posts/2008-07-15-drkaiser-pcconsole.md
Normal file
@ -0,0 +1,17 @@
|
||||
---
|
||||
title: Dr. Kaiser PcConsole
|
||||
layout: default
|
||||
created: 2008-07-15 00:22:10 +0200
|
||||
updated: 2008-07-15 22:04:16 +0200
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
---
|
||||
**Homepage:** <http://www.dr-kaiser.eu/>
|
||||
|
||||
To make locking the workstation impossible, kill `PdsLspSv.exe` in Task Manager.
|
||||
|
||||
`HKLM\SYSTEM\CurrentControlSet\Services\PdsLsp\Flags`
|
||||
|
||||
This value controls locking Internet upon bootup (only, if the LehrerConsole isn't working).
|
44
know-how/software/_posts/2009-01-04-parchive.md
Normal file
@ -0,0 +1,44 @@
|
||||
---
|
||||
title: PArchive
|
||||
layout: default
|
||||
created: 2009-01-04 01:50:40 +0100
|
||||
updated: 2009-01-04 01:50:40 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
---
|
||||
**Homepage:** [sourceforge.net](http://parchive.sourceforge.net/)
|
||||
|
||||
From the homepage:
|
||||
|
||||
> The original idea behind this project was to provide a tool to apply the data-recovery capability concepts of
|
||||
> RAID-like systems to the posting and recovery of multi-part archives on Usenet.
|
||||
|
||||
Parchive can be used to add recovery records to e.g. a DVD. How to do this is described on [Mike West's blog](http://mikewest.org/2008/01/safegarding-your-data-with-parchive).
|
||||
Basically, you will create PAR files using the command:
|
||||
|
||||
par2create -s262144 -r10 [NameOfParFile.par2] [FilesToRead]
|
||||
|
||||
You can then later recover broken files using
|
||||
|
||||
par2repair [NameOfParFile.par2]
|
||||
|
||||
|
||||
GUI Clients
|
||||
===========
|
||||
|
||||
|
||||
Windows
|
||||
-------
|
||||
|
||||
* [QuickPar](http://parchive.sourceforge.net/#clients)
|
||||
* [SmartPar](http://parchive.sourceforge.net/#clients)
|
||||
|
||||
|
||||
Linux
|
||||
-----
|
||||
|
||||
* [gpar2](http://sourceforge.net/project/showfiles.php?group_id=30568&package_id=171020)
|
||||
* [pypar2](http://pypar2.silent-blade.org/)
|
||||
* [tkpar](http://parchive.sourceforge.net/#clients)
|
44
know-how/software/_posts/2009-02-02-codestar.md
Normal file
@ -0,0 +1,44 @@
|
||||
---
|
||||
title: CodeStar
|
||||
layout: default
|
||||
created: 2009-02-02 21:59:35 +0100
|
||||
updated: 2009-02-02 21:59:35 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- encryption
|
||||
---
|
||||
**Homepage:** [codestar.de](http://www.codestar.de/)
|
||||
|
||||
There's a software called *CodeStar* which [claims to use the RSA-algorithm](http://www.codestar.de/html/menu/startseite_s2_frameset.html)
|
||||
to encrypt up to 8 of your passwords using a single password (you should remember). It then lets you print out a
|
||||
colourful card which is the size of a credit card for you to have all your important passwords at hand when you're on
|
||||
the road.
|
||||
|
||||
The bad thing: There's nothing encrypted. You just have to think of a password which consists of different letters.
|
||||
Then you type up to 8 different passwords which can be up to the length of your master password. These passwords are
|
||||
printed around the letters of your master password, e.g. the first letter of the first password is printed to the top
|
||||
left of the first letter of your master password. The 1st letter of the second password is printed to the top of the
|
||||
1st letter of the master password and so on. The unused fields are filled with random data.
|
||||
|
||||
This then looks like this:
|
||||
|
||||
![]({{ site.url }}/assets/cskartenbildklein.gif)
|
||||
|
||||
So let's say your master password is `LINUXMASTER` (no duplicate letters allowed!) and your passwords or PINs are:
|
||||
`tEsT`, `secret`, `0815`, `4711` and `windowsuser`. To get one of the passwords, you'd follow the letters of your
|
||||
master password and find this: (random data omitted!)
|
||||
|
||||
~~~
|
||||
ts0 Ee8 sc1 Tr5 e t
|
||||
L4 I7 N1 U1 X M A S T E R
|
||||
w i n d o w s u s e r
|
||||
~~~
|
||||
|
||||
Since I think 20€ for such a piece of software (which claims to use the [RSA-Alogrithm](http://en.wikipedia.org/wiki/RSA)
|
||||
when it's not) is a bit too much, I spent 20-30 minutes in OpenOffice Calc and came up with this:
|
||||
|
||||
![]({{ site.url }}/assets/codestarooo.png)
|
||||
|
||||
**Download:** [codestar.ods]({{ site.url }}/assets/codestar.ods)
|
@ -0,0 +1,61 @@
|
||||
---
|
||||
title: Microsoft IntelliPoint
|
||||
layout: default
|
||||
created: 2009-02-02 21:23:07 +0100
|
||||
updated: 2009-02-02 21:23:07 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- microsoft
|
||||
- intellipoint
|
||||
---
|
||||
**Download:** [microsoft.com](http://www.microsoft.com/hardware/download/download.aspx?category=MK)
|
||||
|
||||
|
||||
Use with other mice
|
||||
===================
|
||||
|
||||
After installation, find the file `point32.inf` in the `C:\Program Files\Microsoft IntelliPoint\` folder. Copy one of
|
||||
the `HID_Filtr_Inst`-lines and change the PnP-ID to that of your mouse. E.g. my *Logitech V400* has `Vid_046D&Pid_C518`
|
||||
and with its 2 additional buttons and the 4-way-scrollwheel it's comparable with the *Wireless Laser Mouse 6000*.
|
||||
|
||||
If you take a look at the `point32.inf`, you'll find this line near the end:
|
||||
|
||||
{% highlight ini %}
|
||||
HID\Vid_045E&Pid_00F0.DeviceDesc="Microsoft USB Laser Mouse 6000 (IntelliPoint)"
|
||||
{% endhighlight %}
|
||||
|
||||
so go back to the top and find the line:
|
||||
|
||||
{% highlight ini %}
|
||||
%HID\Vid_045E&Pid_00F0.DeviceDesc%=HID_Filtr_Inst, HID\Vid_045E&Pid_00F0
|
||||
{% endhighlight %}
|
||||
|
||||
Since the part before the equals sign is only the variable of the description from the end, you only need to change the
|
||||
part after the equals sign. So just copy this line and change the ID. For me it had to look like this:
|
||||
|
||||
{% highlight ini %}
|
||||
%HID\Vid_045E&Pid_00F0.DeviceDesc%=HID_Filtr_Inst, HID\Vid_046D&Pid_C518
|
||||
{% endhighlight %}
|
||||
|
||||
Now go to the *Device Manager* => *Mice*, right-click your mouse and choose *Update driver* => *Chose driver manually*.
|
||||
Select the IntelliPoint directory and you should see an entry "Microsoft USB Laser Mouse 6000 (IntelliPoint)". Install
|
||||
it and reboot. Done.
|
||||
|
||||
The most interesting feature is the "[Instant View](http://www.microsoft.com/hardware/mouseandkeyboard/features/instantviewer.mspx)"
|
||||
(aka. Exposé) and maybe the [zoom feature](http://www.microsoft.com/hardware/mouseandkeyboard/features/magnify.mspx).
|
||||
Logitech's [SetPoint](http://www.logitech.com/index.cfm/428/144&cl=de,de?softwareid=671&osid=1) doesn't offer these
|
||||
features. But I watched the screen flickering every few seconds which might be because of IntelliPoint updating the
|
||||
thumbnails for "Instant View".
|
||||
|
||||
Compared to *SetPoint*, the `ipoint.exe` only consumes 2,5 MiB RAM whereas SetPoint needs around 12,5 MiB. Also it
|
||||
brings the `KHALMNPR.exe` which consumes additional 6 MiB.
|
||||
|
||||
Only problem for now: Horizontal scrolling doesn't work since it seems to be handled through SetPoint and IntelliPoint
|
||||
doesn't understand the signals of the Logitech mouse. Also you have to scroll the wheel 2-3 ticks before the object on
|
||||
screen starts the actual scrolling. OTOH the "Precision Enhancer" seems really useful for editing pictures.
|
||||
|
||||
btw: For Exposé-feature, you can use [iEx](http://www.oxygen-inc.com/premium/InsaniSoft/iEx.htm) (contained in the
|
||||
*iEx Settings*-download). Or if you want to spend money, [TopDesk](http://www.otakusoftware.com/topdesk/) is a better
|
||||
alternative.
|
58
know-how/software/_posts/2009-02-08-qumana.md
Normal file
@ -0,0 +1,58 @@
|
||||
---
|
||||
title: Qumana
|
||||
layout: default
|
||||
created: 2009-02-02 23:53:17 +0100
|
||||
updated: 2009-02-08 13:34:37 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
---
|
||||
**Homepage:** [qumana.com](http://www.qumana.com/)
|
||||
|
||||
Qumana is a nice blog editor for Windows and Mac. But it is written in Java and thus should run on any platform.
|
||||
|
||||
|
||||
Running under Linux
|
||||
===================
|
||||
|
||||
Download the Mac-Version (`.zip`) and unpack it. You'll find a directory `Qumana.app` which contains a directory
|
||||
`Contents` which contains a directory `Resources` which contains a directory `Java`. There you'll find a `Qumana.jar`
|
||||
and some more libraries and configuration files.
|
||||
|
||||
Copy everything to `/opt/qumana`.
|
||||
|
||||
Starting it with
|
||||
|
||||
java -jar Qumana.jar
|
||||
|
||||
shows the splash screen and the blog-manager, where you can add your blog without problems. It even shows the last
|
||||
posts of your blog. But you'll crash it when trying to edit a posting or start a new one: The console shows several
|
||||
stack traces.
|
||||
|
||||
The thing is: The problem doesn't really lie in Qumana but more in the *GtkLookAndFeel*. This seems to request various
|
||||
properties from the system which then flood the *HashTable* which is causing a *StackOverflow*. So you need to switch
|
||||
it to e.g. the `MetalLookAndFeel`.
|
||||
|
||||
Usually you can force a Java application to a specific LAF by specifing `-Dswing.laf=com.sun.java.swing.plaf.metal.MetalLookAndFeel`
|
||||
as a parameter (might also be `swing.defaultlaf` or `swing.systemlaf`). This didn't work as Qumana queries all
|
||||
available LAFs itself and tries to make an intelligent decision. So the new task: How to get rid of the GtkLookAndFeel?
|
||||
|
||||
After some Google'ing, I found [this thread](http://forums.java.net/jive/message.jspa?messageID=188506) in the
|
||||
java.net-forums where Scott Violet writes:
|
||||
|
||||
> As you have found, we only return GTK as the system look and feel if you're running under GNOME. There's an
|
||||
> environment variable we look for that controls this.
|
||||
|
||||
So which variable might the JRE look for? After looking at the output of `env`, it was obvious. The only variable
|
||||
pointing to Gnome was `GNOME_DESKTOP_SESSION_ID`. So try the following:
|
||||
|
||||
env -u GNOME_DESKTOP_SESSION_ID java -jar Qumana.jar
|
||||
|
||||
Now Qumana starts in the MetalLookAndFeel and you can post new entries as well as edit old ones.
|
||||
|
||||
To specify another LAF, use the following:
|
||||
|
||||
env -u GNOME_DESKTOP_SESSION_ID java -Dswing.systemlaf=com.sun.java.swing.plaf.nimbus.NimbusLookAndFeel -jar /opt/qumana/Qumana.jar
|
||||
|
||||
But be warned that the NimbusLAF has display errors with Qumana.
|
63
know-how/software/_posts/2009-02-08-sony-virtual-expander.md
Normal file
@ -0,0 +1,63 @@
|
||||
---
|
||||
title: SONY Virtual Expander
|
||||
layout: default
|
||||
created: 2009-02-02 01:47:01 +0100
|
||||
updated: 2009-02-08 14:29:52 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- sony
|
||||
---
|
||||
Virtual Expander is a software which is bundled with the following models:
|
||||
|
||||
* [USM-E Plus](http://www.sony.net/Products/Media/Microvault/products/usm-ep/index.html#download) (v1.03)
|
||||
* [USM-D Plus](http://www.sony.net/Products/Media/Microvault/products/usm-dp/index.html#download) (v1.03)
|
||||
* [USM-JX](http://www.sony.net/Products/Media/Microvault/products/usm-jx/dl.html) (v2.3)
|
||||
* [USM-H](http://www.sony.net/Products/Media/Microvault/products/usm-h/dl.html) (v2.4)
|
||||
* [USM-J](http://www.sony.net/Products/Media/Microvault/products/usm-j/dl.html) (v2.4)
|
||||
* [USM-L](http://www.sony.net/Products/Media/Microvault/products/usm-l/dl.html) (v2.4)
|
||||
* [USM-LX](http://www.sony.net/Products/Media/Microvault/products/usm-lx/dl.html) (v2.4)
|
||||
|
||||
The following information is based on the 1.x version since the 2.x was not available at the time I figured this out.
|
||||
But I guess it will work on that versions also.
|
||||
|
||||
|
||||
How it works
|
||||
============
|
||||
|
||||
Basically, VE is a compression tool. It lets you manually compress files and adds the extension `.vem` to them. This
|
||||
extension is associated with the VE Decompressor. So if you double-click a `.vem`-file, it will decompress it and
|
||||
launch it right after that.
|
||||
|
||||
While this works fine for single documents, it doesn't work for a program consisting of many different files as only
|
||||
the file you click is automatically decompressed and not all together. Also it doesn't recompress a file after use so
|
||||
it's not really more comfortable than using a regular compression program.
|
||||
|
||||
The program activates itself if it detects a SONY USB drive based on its PnP-ID, like `USB\Vid_054c&Pid_0241`.
|
||||
|
||||
|
||||
Hacking the tool
|
||||
================
|
||||
|
||||
The latest version, `VirtualExpander_v24.exe` contains the following strings hardcoded in Unicode starting at position
|
||||
`0x39a2c` (VendorID `054c` = *SONY*):
|
||||
|
||||
* `USB\Vid_054c&Pid_0241`
|
||||
* `USB\Vid_054c&Pid_0242`
|
||||
* `USB\Vid_054c&Pid_0243`
|
||||
* `USB\Vid_054c&Pid_02a5`
|
||||
* `USB\Vid_054c&Pid_02a7`
|
||||
|
||||
To make it work with ANY USB drive, just get the ID of your drive:
|
||||
|
||||
1. go to *Control Panel* => *System* => *Advanced* => *Environment variables*
|
||||
1. add a new **System** variable `DevMgr_Show_Details` with the value "1"
|
||||
1. <kbd>OK</kbd> your way back to the Desktop
|
||||
1. open the Device Manager (make sure you closed the "System"-Control Panel before!)
|
||||
1. find your USB drive in the *USB* group and right-click => *Properties*
|
||||
1. find the ID on the new tab *Details*
|
||||
|
||||
Now use your favorite Hex-editor and overwrite one of the SONY IDs with the PnP-ID of *YOUR* USB drive. That's all!
|
||||
|
||||
(The v1.3 has 3 IDs starting at position `0x31950`.)
|
50
know-how/software/_posts/2009-02-15-opera.md
Normal file
@ -0,0 +1,50 @@
|
||||
---
|
||||
title: Opera
|
||||
layout: default
|
||||
created: 2009-02-12 09:17:25 +0100
|
||||
updated: 2009-02-15 23:08:00 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- opera
|
||||
---
|
||||
**Homepage:** <http://www.opera.com/browser/>
|
||||
**Development Blog:** <http://my.opera.com/desktopteam/blog/> (incl. Snapshots)
|
||||
|
||||
|
||||
Hide Trayicon
|
||||
=============
|
||||
|
||||
To save space in the systray, you can run opera with the `-notrayicon` parameter.
|
||||
|
||||
opera -notrayicon
|
||||
|
||||
|
||||
Disable Mailsystem
|
||||
==================
|
||||
|
||||
To save some memory footprint, you can disable the mail module in Opera.
|
||||
|
||||
opera -nomail
|
||||
|
||||
|
||||
Cleanup caches
|
||||
==============
|
||||
|
||||
Opera accumulates several Megabytes on caches, esp. those, who don't cleanup themselves such as the favicon cache. Use
|
||||
this little script to clean up files which haven't been read in the past 14 days from the 3 dirs: `cache4`, `images`
|
||||
and `opcache`:
|
||||
|
||||
{% highlight bash %}
|
||||
#!/bin/bash
|
||||
|
||||
OPERADIR=~/.opera
|
||||
OPERACLEANDIRS="cache4 images opcache"
|
||||
|
||||
for OPERACDIR in $OPERACLEANDIRS; do
|
||||
DIR=$OPERADIR/$OPERACDIR
|
||||
echo $DIR
|
||||
find $DIR -atime +14 -exec rm {} \;
|
||||
done
|
||||
{% endhighlight %}
|
41
know-how/software/_posts/2009-03-05-moneyplex.md
Normal file
@ -0,0 +1,41 @@
|
||||
---
|
||||
title: Moneyplex
|
||||
layout: default
|
||||
created: 2009-03-05 23:44:43 +0100
|
||||
updated: 2009-03-05 23:44:43 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- money
|
||||
---
|
||||
* **Homepage:** [matrica.de](http://www.matrica.de/)
|
||||
|
||||
Moneyplex is an online banking application especially for the German HBCI banking system.
|
||||
|
||||
|
||||
Umlauts in Ubuntu
|
||||
=================
|
||||
|
||||
Since Ubuntu is fully UTF-8 for some time now (and Moneyplex isn't), you'll see strange things when using it: Some
|
||||
umlauts are replaced by question marks while others are printed fine.
|
||||
|
||||
To get everything working, you have to generate an (old) ISO-8859-15 locale. To accomplish this, edit the file
|
||||
`/var/lib/locales/supported.d/de` and add the following line:
|
||||
|
||||
de_DE@euro ISO-8859-15
|
||||
|
||||
Now run the following command to generate the new locale:
|
||||
|
||||
{% highlight bash %}
|
||||
sudo dpkg-reconfigure locales
|
||||
{% endhighlight %}
|
||||
|
||||
Finally you have to edit the `~/moneyplex/start` script to use the new locale. Change the following two lines:
|
||||
|
||||
{% highlight bash %}
|
||||
export LC_ALL=de_DE.ISO-8859-15@euro
|
||||
export LANG=de_DE.ISO-8859-15@euro
|
||||
{% endhighlight %}
|
||||
|
||||
Now you should see all umlauts correctly.
|
61
know-how/software/_posts/2009-03-30-microsoft-office-oem.md
Normal file
@ -0,0 +1,61 @@
|
||||
---
|
||||
title: Microsoft Office OEM
|
||||
layout: default
|
||||
created: 2009-03-30 12:26:11 +0200
|
||||
updated: 2009-03-30 12:26:11 +0200
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- microsoft
|
||||
- office
|
||||
---
|
||||
Install Fujitsu-Siemens version
|
||||
===============================
|
||||
|
||||
If you want to install a *Microsoft Office* and you happen to only have an OEM version from Fujitsu-Siemens, you'll
|
||||
notice that it refuses to install on any Non-FSC-PC. But after some peeking around on the CD, you'll find a
|
||||
suspiciously large file `Install\OFF_FSC.EXE` with around 250 MiB.
|
||||
|
||||
Taking a look at it reveals something strange:
|
||||
|
||||
~~~
|
||||
00000000 47 4F 4E 49 │ C3 91 0E 8A │ 69 A9 79 79 │ 5C 36 B8 1E GONIÃ...i©yy\6¸.
|
||||
00000010 74 B0 52 C4 │ 64 20 8C C5 │ 13 A0 99 10 │ 27 7B 2E 27 t°RÄd .Å. ..'{.'
|
||||
00000020 6D 87 BF 73 │ 04 8A AC 32 │ 0A 84 03 A9 │ 46 98 BE 71 m.¿s..¬2...©F.¾q
|
||||
00000030 AC 61 32 5E │ BE 07 4C C8 │ B0 C1 95 92 │ 60 0B 08 4C ¬a2^¾.LÈ°Á..`..L
|
||||
00000040 1B 5F A5 15 │ C3 23 45 C4 │ 3F 63 78 9E │ 4C 12 8E 06 ._¥.Ã#EÄ?cx.L...
|
||||
~~~
|
||||
|
||||
This doesn't look like a normal `EXE` file, it's missing the typical `MZ` header. Also the following data looks
|
||||
encrypted, i.e. somewhat random.
|
||||
|
||||
Somewhat below you'll find some strings which have to do with unpacking - so the file seems to be a crypted
|
||||
self-extracting archive.
|
||||
|
||||
Going several pages further down, you'll find something familiar:
|
||||
|
||||
~~~
|
||||
00009FE0 00 00 00 00 │ 00 00 00 00 │ 00 00 00 00 │ 00 00 00 00 ................
|
||||
00009FF0 00 00 00 00 │ 00 00 00 00 │ 00 00 00 00 │ 00 00 00 00 ................
|
||||
0000A000 4D 53 43 46 │ 00 00 00 00 │ 12 91 43 0E │ 00 00 00 00 MSCF......C.....
|
||||
0000A010 2C 00 00 00 │ 00 00 00 00 │ 03 01 01 00 │ 7E 00 00 00 ,...........~...
|
||||
0000A020 00 00 00 00 │ 5D 11 00 00 │ 5D 1D 01 00 │ C1 00 00 00 ....]...]...Á...
|
||||
0000A030 00 00 00 00 │ 00 00 0F 2F │ 2F 79 03 00 │ 41 55 54 4F .......//y..AUTO
|
||||
0000A040 52 55 4E 2E │ 49 4E 46 00 │ 31 A8 19 00 │ C1 00 00 00 RUN.INF.1¨..Á...
|
||||
0000A050 00 00 0F 2F │ BA 58 03 00 │ 43 43 35 36 │ 31 34 30 31 .../ºX..CC561401
|
||||
0000A060 2E 43 41 42 │ 00 3A F1 04 │ 00 F2 A8 19 │ 00 00 00 0F .CAB.:ñ..ò¨.....
|
||||
0000A070 2F BC 58 03 │ 00 43 44 35 │ 36 31 34 30 │ 31 2E 43 41 /¼X..CD561401.CA
|
||||
0000A080 42 00 F3 99 │ 1F 00 2C 9A │ 1E 00 00 00 │ 0F 2F C6 58 B.ó...,....../ÆX
|
||||
0000A090 03 00 43 46 │ 35 36 31 34 │ 30 31 2E 43 │ 41 42 00 C3 ..CF561401.CAB.Ã
|
||||
0000A0A0 C6 0A 00 1F │ 34 3E 00 00 │ 00 0F 2F CA │ 58 03 00 43 Æ...4>..../ÊX..C
|
||||
0000A0B0 4C 35 36 31 │ 34 30 31 2E │ 43 41 42 00 │ 9C CC 12 00 L561401.CAB..Ì..
|
||||
~~~
|
||||
|
||||
`MSCF` stands for *MicroSoft CAB File*. It's a header for the standard `CAB` archives used to distribute software. The
|
||||
`AUTORUN.INF`, `CC561401.CAB`, etc. are also a clear sign that this seems to be the index of the archive. The letters
|
||||
`MSCF` are mentioned several times before this location but there was no file index near them. This one here is clearly
|
||||
a standard CAB file.
|
||||
|
||||
So now take your favorite Hex-Editor and cut everything up to the `MSCF` header. The new file has to begin with `MSCF`.
|
||||
Rename it to something `.cab` and use your favorite archiving tool to unpack it. Et voilà!
|
24
know-how/software/_posts/2009-04-07-lighttpd.md
Normal file
@ -0,0 +1,24 @@
|
||||
---
|
||||
title: LightTPD
|
||||
layout: default
|
||||
created: 2009-04-07 11:16:12 +0200
|
||||
updated: 2009-04-07 11:16:12 +0200
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- http
|
||||
- lighttpd
|
||||
---
|
||||
Include wildcard configuration files
|
||||
====================================
|
||||
|
||||
Lighty doesn't allow wildcarded inclusions of configuration files, but you can do a [little trick](http://redmine.lighttpd.net/issues/show/1221)
|
||||
using the `include_shell` command:
|
||||
|
||||
~~~
|
||||
include_shell "cat /etc/lighttpd/conf.d/*conf"
|
||||
|
||||
# more elegant
|
||||
include_shell "find /etc/lighttpd/conf.d -maxdepth 1 -name '*.conf' -exec cat {} \;"
|
||||
~~~
|
92
know-how/software/_posts/2009-05-17-skype-to-sip.md
Normal file
@ -0,0 +1,92 @@
|
||||
---
|
||||
title: Skype <=> SIP Interlink
|
||||
layout: default
|
||||
created: 2009-05-17 13:06:06 +0200
|
||||
updated: 2009-05-17 13:06:06 +0200
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- sip
|
||||
- skype
|
||||
- conference
|
||||
---
|
||||
To connect Skype to a SIP-PBX (e.g. Asterisk), there's only one free application available:
|
||||
|
||||
* [SipToSis](http://www.mhspot.com/sts/siptosis.html) (former *SippySkype*)
|
||||
|
||||
There are also some (Windows-)apps for money, like:
|
||||
|
||||
* [Uplink Skype to SIP](http://www.nch.com.au/skypetosip/)
|
||||
* [PSGw](http://www.rsdevs.com/psgw.shtml)
|
||||
|
||||
Since you can't integrate these apps into Asterisk, you need to add an extension for each Skype account (1 per PC).
|
||||
|
||||
If somebody calls via Skype, you can let SipToSis dial a specific number (internal/external) via the Asterisk PBX. Most
|
||||
probably you want it to dial your own SIP extension.
|
||||
|
||||
If you call the Skype extension, you can let SipToSis dial a specific Skype contact. Maybe you could add another
|
||||
virtual PBX so that you could dial `<SkypeContact>@<SipToSis-IP>` on your VoIP-phone to call a specific Skype contact -
|
||||
but your VoIP-phone then needs to be registered with this virtual PBX.
|
||||
|
||||
|
||||
SipToSis (SippySkype)
|
||||
=====================
|
||||
|
||||
Since this program is free and written in Java, it's the perfect choice for now. Configuration might be a bit tricky
|
||||
though.
|
||||
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
In this example, there are following values:
|
||||
|
||||
| Value | Description |
|
||||
|:--------------:|:---------------|
|
||||
|192.168.1.162 |IP of the PC running Skype and SipToSis|
|
||||
|192.168.1.245 |IP of the Asterisk PBX |
|
||||
|88 |SipToSis-extension on the Asterisk PBX |
|
||||
|44@192.168.1.212|Extension and IP of the VoIP-phone to use for incoming Skype calls|
|
||||
|
||||
|
||||
### siptosis.cfg (former sippyskype.cfg)
|
||||
|
||||
{% highlight ini %}
|
||||
via_addr=192.168.1.162
|
||||
host_port=5060
|
||||
contact_url=sip:88@192.168.1.245:5060
|
||||
from_url="Skype Gateway" <sip:88@192.168.1.245:5060>
|
||||
username=88
|
||||
realm=asterisk
|
||||
passwd=skype
|
||||
do_register=yes
|
||||
{% endhighlight %}
|
||||
|
||||
So this general description should work:
|
||||
|
||||
|Setting |Note |
|
||||
|:------------|:-------------|
|
||||
|`via_addr` |IP of SipToSis/SippySkype|
|
||||
|`host_port` |Desired Port of SipToSis |
|
||||
|`contact_url`|`sip:`//Asterisk-Skype-Extension//`@192.168.1.245:5060`|
|
||||
|`from_url` |some name + the `contact_url`|
|
||||
|`username` |Asterisk-Skype-Extension |
|
||||
|`realm` |might be not used |
|
||||
|`passwd` |Asterisk-Skype-Ext-Passwort |
|
||||
|`do_register`|Should SipToSis register itself in the PBX? Yes!|
|
||||
|
||||
The remaining options can be left at default values.
|
||||
|
||||
|
||||
### SkypeToSipAuth.props
|
||||
|
||||
This file defines the receivers of the calls. You can route incoming calls of different Skype contacts to different SIP
|
||||
accounts. But in most cases you want to receive all calls on one specific VoIP phone.
|
||||
|
||||
*,sip:44@192.168.1.212:5060
|
||||
|
||||
|
||||
<p><div class="noteclassic" markdown="1">
|
||||
You have to specify the IP of the **VoIP-phone** which should receive the calls. **NOT** the IP of the Asterisk PBX.
|
||||
</div></p>
|
87
know-how/software/_posts/2009-07-17-virtualbox.md
Normal file
@ -0,0 +1,87 @@
|
||||
---
|
||||
title: VirtualBox
|
||||
layout: default
|
||||
created: 2009-01-04 15:50:17 +0100
|
||||
updated: 2009-07-17 23:14:13 +0200
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- virtualisation
|
||||
- oracle
|
||||
- virtualbox
|
||||
---
|
||||
Compacting a disk image
|
||||
=======================
|
||||
|
||||
1. overwrite empty blocks on the disk with zeroes. See below for applications.
|
||||
1. run the VBoxManage tool like this:[^1]
|
||||
|
||||
VBoxManage modifyhd <NameOfVDIorVMHD> compact
|
||||
|
||||
|
||||
Applications for overwriting empty blocks
|
||||
=========================================
|
||||
|
||||
|
||||
Eraser (Windows)
|
||||
----------------
|
||||
|
||||
[ [Homepage](http://eraser.heidi.ie/) ] Install as normal. Then go to *Edit* -> *Preferences* -> *Erasing...* and
|
||||
select the second Tab *Unused disk space*. Create a new method with one pass and a pattern of only zeroes. Now go to
|
||||
the "On Demand"-Tasks and create a new one with your local harddisks as target. Run it to perform erasing.
|
||||
|
||||
|
||||
SDelete (Windows, SysInternals)
|
||||
-------------------------------
|
||||
|
||||
[ [Homepage](http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx) ] Download and unpack. Run it like:
|
||||
|
||||
sdelete -c C:\
|
||||
|
||||
|
||||
dd (Linux)
|
||||
----------
|
||||
|
||||
Use something like:
|
||||
|
||||
dd if=/dev/zero of=/junk
|
||||
sync
|
||||
rm /junk
|
||||
|
||||
This will create a large file with only zeroes and fill up the empty space on your hd.
|
||||
|
||||
|
||||
zerofree (Linux)
|
||||
----------------
|
||||
|
||||
[ [Homepage](http://intgat.tigress.co.uk/rmy/uml/index.html) ] Install the [zerofree](apt://zerofree) package. Run it
|
||||
as the man page says.
|
||||
|
||||
<p><div class="notewarning" markdown="1">
|
||||
Seems like *zerofree* only supports unmounted filesystems. For this to work you should boot into a recovery Linux
|
||||
inside your VM to clean the disk image.
|
||||
</div></p>
|
||||
|
||||
|
||||
sfill (Linux)
|
||||
-------------
|
||||
|
||||
Install the [secure-delete](apt://secure-delete) package. Run something like:
|
||||
|
||||
sfill -z -l -l /
|
||||
|
||||
|
||||
Transparency-Bug in VBox 3.0
|
||||
============================
|
||||
|
||||
If you just installed VirtualBox 3.0 and noticed that you only see parts of Windows' titlebars and the icons but no
|
||||
text or backgrounds, try the following:
|
||||
|
||||
Run VirtualBox like this: [Found here](http://webupd8.blogspot.com/2009/05/quick-tip-make-virtualbox-os-window-non.html)
|
||||
|
||||
env XLIB_SKIP_ARGB_VISUALS=1 VirtualBox
|
||||
|
||||
|
||||
|
||||
[^1]: Older versions of VirtualBox used `modifyvdi` as first parameter. Also this feature is disabled in VBox 2.1.
|
46
know-how/software/_posts/2009-11-27-network-monitoring.md
Normal file
@ -0,0 +1,46 @@
|
||||
---
|
||||
title: Network Monitoring
|
||||
layout: default
|
||||
created: 2009-11-23 10:01:08 +0100
|
||||
updated: 2009-11-27 23:50:53 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- monitoring
|
||||
- network
|
||||
---
|
||||
I tried some different products for network monitoring since the top dog *Nagios* is everything else but easy to
|
||||
maintain.
|
||||
|
||||
Tested products were:
|
||||
|
||||
* [OpenNMS](#opennms)
|
||||
* [Zenoss Core](#zenoss-core)
|
||||
* [Pandora FMS](#pandora-fms)
|
||||
|
||||
|
||||
OpenNMS
|
||||
=======
|
||||
|
||||
* **Homepage:** <http://www.opennms.org/>
|
||||
|
||||
Configurable by XML files, so suffers the same problem as Nagios - you need something to configure it comfortably or
|
||||
spend time writing the config yourself. Compatible to Nagios plugins.
|
||||
|
||||
|
||||
Pandora FMS
|
||||
===========
|
||||
|
||||
* **Homepage:** <http://www.pandorafms.org/>
|
||||
|
||||
Really great interface. Supports Nagios plugins. Easy addition of own plugins. For me, this one had the best feature
|
||||
set.
|
||||
|
||||
|
||||
Zenoss Core
|
||||
===========
|
||||
|
||||
* **Homepage:** <http://community.zenoss.org/>
|
||||
|
||||
Not really intuitive configuration. Supports Nagios plugins, offers own extension system (ZenPacks).
|
127
know-how/software/_posts/2009-12-04-dd-wrt.md
Normal file
@ -0,0 +1,127 @@
|
||||
---
|
||||
title: DD-WRT
|
||||
layout: default
|
||||
created: 2009-04-03 12:30:33 +0200
|
||||
updated: 2009-12-04 00:54:05 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- dd-wrt
|
||||
---
|
||||
DD-WRT is an alternative firmware for several WLAN routers which offers a lot of more features than the default
|
||||
firmwares of most routers, such as repeater mode, printserver, fileserver, etc.. I use it on an *ASUS WL-300g* and a
|
||||
*Linksys WRT54GL*.
|
||||
|
||||
* **Homepage:** [dd-wrt.com](http://www.dd-wrt.com/)
|
||||
|
||||
|
||||
Configure as non-WDS repeater
|
||||
=============================
|
||||
|
||||
After a lot of trial-and-error and studying [the](http://www.dd-wrt.com/wiki/index.php/Wlan_Repeater) [different](http://www.dd-wrt.com/phpBB2/viewtopic.php?t=7595)
|
||||
[HowTos](http://www.dd-wrt.com/wiki/index.php/Universal_Wireless_Repeater), I now found the best settings to make my
|
||||
former AccessPoint a repeater.
|
||||
|
||||
<p><div class="noteclassic">
|
||||
This mode will repeat the WLAN network under a different SSID. Your WLAN card won't do any roaming and you will have to
|
||||
setup port forwardings for server daemons.
|
||||
</div></p>
|
||||
|
||||
So here are the neccessary settings. Pages you don't need to change do not have an image linked.
|
||||
|
||||
* Setup
|
||||
* [Basic Setup]({{ site.url }}/assets/setup_basic_setup.png)
|
||||
* DDNS
|
||||
* MAC Address Clone
|
||||
* [Advanced Routing]({{ site.url }}/assets/setup_advanced_routing.png)
|
||||
* [Networking]({{ site.url }}/assets/setup_networking.png)
|
||||
* Wireless
|
||||
* [Basic Settings]({{ site.url }}/assets/wireless_basic_settings.png)
|
||||
* Radius
|
||||
* [Wireless Security]({{ site.url }}/assets/wireless_wireless_security.png)
|
||||
* MAC Filter
|
||||
* [Advanced Settings]({{ site.url }}/assets/wireless_advanced_settings.png)
|
||||
* [WDS]({{ site.url }}/assets/wireless_wds.png)
|
||||
* Services
|
||||
* [Services]({{ site.url }}/assets/services_services.png)
|
||||
* PPTP
|
||||
* Hotspot
|
||||
* Security
|
||||
* [Firewall]({{ site.url }}/assets/security_firewall.png)
|
||||
* VPN
|
||||
* Access Restrictions
|
||||
* WAN Access
|
||||
* NAT / QoS
|
||||
* Port Forwarding
|
||||
* Port Range Forwarding
|
||||
* Port Triggering
|
||||
* UPnP
|
||||
* DMZ
|
||||
* QoS
|
||||
* Administration
|
||||
* Management
|
||||
* Keep Alive
|
||||
* Commands
|
||||
* WOL
|
||||
* Factory Defaults
|
||||
* Firmware Upgrade
|
||||
* Backup
|
||||
* Status
|
||||
* Router
|
||||
* LAN
|
||||
* Wireless
|
||||
* Bandwidth
|
||||
* Sys-Info
|
||||
|
||||
|
||||
Notify about new IP via Prowl service
|
||||
=====================================
|
||||
|
||||
*Prowl* was originally thought as a remote notification service from MacOS *Growl* to the iPhone. But it provides a
|
||||
great web-based API so that it can be used for any other purpose.
|
||||
|
||||
The [DD-WRT Wiki](http://www.dd-wrt.com/wiki/index.php/Script_Execution) lists all the locations where you can place
|
||||
scripts for automatic execution. As we want to be notified upon IP changes, the best event is the `wanup`. So create a
|
||||
file `/tmp/etc/config/prowl.wanup`. In the [Script Examples](http://www.dd-wrt.com/wiki/index.php/Script_Examples#Use_freedns.afraid.org_as_DDNS)
|
||||
section, there's a nice DynDNS script which shows, how to get the current WAN IP and check whether it has changed.
|
||||
|
||||
With some modifications, it looks like this:
|
||||
|
||||
{% highlight bash %}
|
||||
#!/bin/sh
|
||||
IFACE=ppp0
|
||||
OLDFILE=/tmp/ipaddr.cache
|
||||
|
||||
OLD_IP=`cat $OLDFILE`
|
||||
NEW_IP=`ifconfig ${IFACE} | sed '/.*inet addr:/!d;s///;s/ .*//'`
|
||||
|
||||
# Special (private) Unicode icons for the iPhone
|
||||
PROWL_UP=""
|
||||
PROWL_DISH=""
|
||||
|
||||
if [ "$NEW_IP" != "$OLD_IP" ]; then
|
||||
/tmp/root/prowl.sh "ppp0 is $PROWL_UP" -2 "IP is $NEW_IP $PROWL_DISH"
|
||||
echo $NEW_IP > $OLDFILE
|
||||
echo Updated IP to $NEW_IP
|
||||
fi
|
||||
{% endhighlight %}
|
||||
|
||||
Put this file to `/tmp/etc/config/prowl.wanup`. The used `/tmp/root/prowl.sh` is the one you can find in the [[TODO:software:sh:http-post]] article.
|
||||
|
||||
|
||||
*[WLAN]: Wireless Local Area Network
|
||||
*[SSID]: Service Set Identifier
|
||||
*[DDNS]: Dynamic DNS
|
||||
*[MAC]: Media Access Control
|
||||
*[WDS]: Wireless Distribution System
|
||||
*[PPTP]: Point-to-Point Tunneling Protocol
|
||||
*[VPN]: Virtual Private Network
|
||||
*[NAT]: Network Address Translation
|
||||
*[QoS]: Quality of Service
|
||||
*[UPnP]: Universal Plug'n'Play
|
||||
*[DMZ]: Demilitarized Zone
|
||||
*[WOL]: Wake-on-LAN
|
||||
*[LAN]: Local Area Network
|
||||
*[API]: Application Programming Interface
|
||||
*[WAN]: Wide Area Network
|
53
know-how/software/_posts/2012-05-14-wuala.md
Normal file
@ -0,0 +1,53 @@
|
||||
---
|
||||
title: wua.la
|
||||
layout: default
|
||||
created: 2011-09-12 22:46:24 +0200
|
||||
updated: 2012-05-14 15:53:45 +0200
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- wuala
|
||||
---
|
||||
[wua.la](http://wuala.com/) is a Dropbox-like online (aka. cloud) storage.
|
||||
|
||||
|
||||
Promotion Codes
|
||||
===============
|
||||
|
||||
|Code |Add. Storage| Valid for ||
|
||||
|:---------------------|:----------:|:----------:|:---|
|
||||
|`PCWELT06` | 3 GiB | 1 year | ? |
|
||||
|`CONNECT-WITH-SUPPORT`| 1 GiB | 1 year |
|
||||
|`PC-MAGAZIN` | 2 GiB | 1 year | ? |
|
||||
|`SKYFISH-IS-COOL` | 1 GiB | 3 months |
|
||||
|`I-KNOW-DOMINIK` | 1 GiB | 3 months |
|
||||
|`I-KNOW-CAROLA` | 1 GiB | 3 months |
|
||||
|`I-KNOW-FABIUS` | 1 GiB | 3 months |
|
||||
|`I-KNOW-LUZIUS` | 1 GiB | 3 months |
|
||||
|`I-KNOW-THOMAS` | 1 GiB | 3 months |
|
||||
|`I-KNOW-JONAS` | 1 GiB | 3 months |
|
||||
|`I-KNOW-MARCEL` | 1 GiB | 3 months |
|
||||
|`I-KNOW-MARIUS` | 1 GiB | 3 months |
|
||||
|`I-KNOW-DARIO` | 1 GiB | 3 months |
|
||||
|`XMAS08` | 1 GiB | 1 year | ? |
|
||||
|`STUDISURF` | 2 GiB | 1 year | ? |
|
||||
|`PC-PRAXIS` | 2 GiB | 1 year | ? |
|
||||
|`FOUNDER_CH` | 1 GiB | 1 year | ? |
|
||||
|`H` | 10 GiB | 1 year | cancelled |
|
||||
|`I-LIKE-POLAND` | 1 GiB | 1 year |
|
||||
|`COMPUTER-HOY` | ??? | ??? | cancelled |
|
||||
|`I-READ-TOOLTIPS` | 512 MiB | ??? | cancelled? |
|
||||
|`I-KNOW-ANDY` | 1 GiB | 1 year | cancelled |
|
||||
|`C` | ??? | ??? | cancelled |
|
||||
|`G` | ??? | ??? | cancelled |
|
||||
|`K` | ??? | ??? | cancelled |
|
||||
|`M` | ??? | ??? | cancelled |
|
||||
|`N` | ??? | ??? | cancelled |
|
||||
|`R` | ??? | ??? | cancelled |
|
||||
|`X` | ??? | ??? | cancelled |
|
||||
|`WUACIE` | 10 GiB | ??? | cancelled |
|
||||
|`I-KNOW-MARKUS` | 1 GiB | 3 months |
|
||||
|`WORLD_BACKUP_DAY` | 2 GiB | ??? | cancelled |
|
||||
|`SHNET` | 2 GiB | ??? | cancelled |
|
||||
|`1000-ANSWERS` | 1 GiB | 1 year |
|
@ -0,0 +1,51 @@
|
||||
---
|
||||
title: Puppet on CentOS 7
|
||||
layout: default
|
||||
created: 2015-04-14 13:33:59 +0200
|
||||
updated: 2015-04-14 13:33:59 +0200
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- linux
|
||||
- puppet
|
||||
- centos
|
||||
---
|
||||
To install Puppet on CentOS 7, you can basically follow [these instructions](http://www.unixmen.com/install-puppet-server-centos-7/).
|
||||
|
||||
Notes:
|
||||
|
||||
1. Don't forget to open the firewall:
|
||||
|
||||
firewall-cmd --zone=public --add-port=8140/tcp --permanent
|
||||
firewall-cmd --reload
|
||||
|
||||
1. You may have to put SELinux into `permissive` mode to allow Apache read the `config.ru` owned by `puppet`.
|
||||
|
||||
To permanently switch from WEBrick to Apache, configure systemd like this:
|
||||
|
||||
systemctl disable puppetmaster
|
||||
systemctl enable httpd
|
||||
|
||||
|
||||
Install client agent on RedHat/CentOS
|
||||
=====================================
|
||||
|
||||
1. Pick the correct repository for your version from [PuppetLabs](https://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-red-hat-enterprise-linux-and-derivatives).
|
||||
1. Install it:
|
||||
|
||||
yum install puppet
|
||||
|
||||
1. If needed, configure the Puppetmaster server name in `/etc/puppet/puppet.conf`:
|
||||
|
||||
[agent]
|
||||
server = mypuppetmaster.example.org
|
||||
|
||||
1. Finally, add the cronjob[^1]:
|
||||
|
||||
puppet resource cron puppet-agent ensure=present user=root minute=30 command='/usr/bin/puppet agent --onetime --no-daemonize --splay'
|
||||
|
||||
|
||||
|
||||
[^1]: There's also a way to let the puppet agent run as a service described [here](https://docs.puppetlabs.com/guides/install_puppet/post_install.html#start-the-puppet-agent-service),
|
||||
but this can have an impact on cpu and memory usage.
|