http://niki.hammler.net/w/api.php?action=feedcontributions&user=Niki&feedformat=atomNOBAQ - Benutzerbeiträge [de-at]2024-03-29T06:48:56ZBenutzerbeiträgeMediaWiki 1.35.13http://niki.hammler.net/w/index.php?title=Server&diff=1677Server2021-09-11T07:01:15Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>25.02.2005</td><td>hislog, to log command history to /var/log/history</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>28.09.2007</td><td>Spamassassin etc.</td><br />
</tr><br />
<tr><br />
<td>03.01.2008</td><td>Move system accounts into LDAP. Connect Samba mit LDAP</td><br />
</tr><br />
<tr><br />
<td>08.11.2008</td><td>Split mail system von nobaq zu neuem mail VServer</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020-09.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis/nobaq from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
<tr><br />
<td>24.09.2020</td><td>USV tot. Rmote replacement.</td><br />
</tr><br />
<tr><br />
<td>March 2021</td><td>ZFS pool upgrade 3TB mirror to 12TB mirror; Upgrade vicar as well; Migrate zetta from FreeNAS to Ubuntu; get rid of iSCSI</td><br />
</tr><br />
<tr><br />
<td>July 2021</td><td>Added 4G WWAN emergency uplink</td><br />
</tr><br />
<tr><br />
<td>Aug 2021</td><td>Logger cross-grade i384 to amd64</td><br />
</tr><br />
<tr><br />
<td>Sep 2021</td><td>Upgrade all servers to Debian bullseye completed</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1676Server2021-09-11T06:59:53Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>25.02.2005</td><td>hislog, to log command history to /var/log/history</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>28.09.2007</td><td>Spamassassin etc.</td><br />
</tr><br />
<tr><br />
<td>03.01.2008</td><td>Move system accounts into LDAP. Connect Samba mit LDAP</td><br />
</tr><br />
<tr><br />
<td>08.11.2008</td><td>Split mail system von nobaq zu neuem mail VServer</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020-09.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis/nobaq from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
<tr><br />
<td>March 2021</td><td>ZFS pool upgrade 3TB mirror to 12TB mirror; Upgrade vicar as well; Migrate zetta from FreeNAS to Ubuntu; get rid of iSCSI</td><br />
</tr><br />
<tr><br />
<td>July 2021</td><td>Added 4G WWAN emergency uplink</td><br />
</tr><br />
<tr><br />
<td>Aug 2021</td><td>Logger cross-grade i384 to amd64</td><br />
</tr><br />
<tr><br />
<td>Sep 2021</td><td>Upgrade all servers to Debian bullseye completed</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1675Server2021-09-10T20:58:03Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>25.02.2005</td><td>hislog, to log command history to /var/log/history</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>28.09.2007</td><td>Spamassassin etc.</td><br />
</tr><br />
<tr><br />
<td>03.01.2008</td><td>Move system accounts into LDAP. Connect Samba mit LDAP</td><br />
</tr><br />
<tr><br />
<td>08.11.2008</td><td>Split mail system von nobaq zu neuem mail VServer</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020-09.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis/nobaq from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
<tr><br />
<td>March 2021</td><td>ZFS pool upgrade 3TB mirror to 12TB mirror; Upgrade zetta & vicar as well</td><br />
</tr><br />
<tr><br />
<td>July 2021</td><td>Added 4G WWAN emergency uplink</td><br />
</tr><br />
<tr><br />
<td>Aug 2021</td><td>Logger cross-grade i384 to amd64</td><br />
</tr><br />
<tr><br />
<td>Sep 2021</td><td>Upgrade all servers to Debian bullseye completed</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1674Server2021-09-10T20:51:13Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>28.09.2007</td><td>Spamassassin etc.</td><br />
</tr><br />
<tr><br />
<td>03.01.2008</td><td>Move system accounts into LDAP. Connect Samba mit LDAP</td><br />
</tr><br />
<tr><br />
<td>08.11.2008</td><td>Split mail system von nobaq zu neuem mail VServer</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020-09.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis/nobaq from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
<tr><br />
<td>March 2021</td><td>ZFS pool upgrade 3TB mirror to 12TB mirror; Upgrade zetta & vicar as well</td><br />
</tr><br />
<tr><br />
<td>July 2021</td><td>Added 4G WWAN emergency uplink</td><br />
</tr><br />
<tr><br />
<td>Aug 2021</td><td>Logger cross-grade i384 to amd64</td><br />
</tr><br />
<tr><br />
<td>Sep 2021</td><td>Upgrade all servers to Debian bullseye completed</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1673Server2021-09-10T20:50:16Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>28.09.2007</td><td>Spamassassin etc.</td><br />
</tr><br />
<tr><br />
<td>03.01.2008</td><td>Connect Samba mit LDAP</td><br />
</tr><br />
<tr><br />
<td>08.11.2008</td><td>Split mail system von nobaq zu neuem mail VServer</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020-09.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis/nobaq from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
<tr><br />
<td>March 2021</td><td>ZFS pool upgrade 3TB mirror to 12TB mirror; Upgrade zetta & vicar as well</td><br />
</tr><br />
<tr><br />
<td>July 2021</td><td>Added 4G WWAN emergency uplink</td><br />
</tr><br />
<tr><br />
<td>Aug 2021</td><td>Logger cross-grade i384 to amd64</td><br />
</tr><br />
<tr><br />
<td>Sep 2021</td><td>Upgrade all servers to Debian bullseye completed</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1672Server2021-09-10T20:47:35Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>03.01.2008</td><td>Connect Samba mit LDAP</td><br />
</tr><br />
<tr><br />
<td>08.11.2008</td><td>Split mail system von nobaq zu neuem mail VServer</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020-09.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis/nobaq from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
<tr><br />
<td>March 2021</td><td>ZFS pool upgrade 3TB mirror to 12TB mirror; Upgrade zetta & vicar as well</td><br />
</tr><br />
<tr><br />
<td>July 2021</td><td>Added 4G WWAN emergency uplink</td><br />
</tr><br />
<tr><br />
<td>Aug 2021</td><td>Logger cross-grade i384 to amd64</td><br />
</tr><br />
<tr><br />
<td>Sep 2021</td><td>Upgrade all servers to Debian bullseye completed</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1671Server2021-09-10T20:46:18Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>08.11.2008</td><td>Split mail system von nobaq zu neuem mail VServer</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020-09.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis/nobaq from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
<tr><br />
<td>March 2021</td><td>ZFS pool upgrade 3TB mirror to 12TB mirror; Upgrade zetta & vicar as well</td><br />
</tr><br />
<tr><br />
<td>July 2021</td><td>Added 4G WWAN emergency uplink</td><br />
</tr><br />
<tr><br />
<td>Aug 2021</td><td>Logger cross-grade i384 to amd64</td><br />
</tr><br />
<tr><br />
<td>Sep 2021</td><td>Upgrade all servers to Debian bullseye completed</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1670Server2021-09-09T02:03:09Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020-09.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis/nobaq from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
<tr><br />
<td>March 2021</td><td>ZFS pool upgrade 3TB mirror to 12TB mirror; Upgrade zetta & vicar as well</td><br />
</tr><br />
<tr><br />
<td>July 2021</td><td>Added 4G WWAN emergency uplink</td><br />
</tr><br />
<tr><br />
<td>Aug 2021</td><td>Logger cross-grade i384 to amd64</td><br />
</tr><br />
<tr><br />
<td>Sep 2021</td><td>Upgrade all servers to Debian bullseye completed</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1669Server2021-09-08T23:38:30Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020-09.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis/nobaq from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
<tr><br />
<td>March 2021</td><td>ZFS pool upgrade 3TB mirror to 12TB mirror; Upgrade zetta & vicar as well</td><br />
</tr><br />
<tr><br />
<td>July 2021</td><td>Added 4G WWAN emergency uplink</td><br />
</tr><br />
<tr><br />
<td>Aug 2021</td><td>Logger cross-grade i384 to amd64</td><br />
</tr><br />
<tr><br />
<td>Sep 2021</td><td>Upgrade all servers to Debian bullseye completed (except mail)</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1667Server2021-08-18T07:31:24Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020-09.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis/nobaq from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
<tr><br />
<td>March 2021</td><td>ZFS pool upgrade 3TB mirror to 12TB mirror; Upgrade zetta & vicar as well</td><br />
</tr><br />
<tr><br />
<td>July 2021</td><td>Added 4G WWAN emergency uplink</td><br />
</tr><br />
<tr><br />
<td>Aug 2021</td><td>Logger cross-grade i384 to amd64</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1666Server2021-08-18T07:30:31Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020-09.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis/nobaq from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
<tr><br />
<td>March 2021</td><td>ZFS pool upgrade 3TB mirror to 12TB mirror; Upgrade zetta & vicar as well</td><br />
</tr><br />
<tr><br />
<td>Aug 2021</td><td>Logger cross-grade i384 to amd64</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=KeePass&diff=1665KeePass2020-10-20T02:40:09Z<p>Niki: /* TAN Placeholder */</p>
<hr />
<div>[http://keepass.info KeePass] is a password manager and one of my op "must-have" applications. Instead of either having the same password for all your stuff or having to remember many different passwords, you can use one single, secure password to store all others in a secure, encrypted way. Integrations such as autotype makes it easy to handle these passwords in Windows and KeePass is available for multiple platforms.<br />
<br />
= KeePass 1 =<br />
<br />
KeePass 1.x is a very light variant for KeePass. I have extended it using various plugins. Related articles:<br />
<br />
* [[LockExtensions for KeePass]]<br />
* [[More extensions for KeePass]]<br />
* [[GPG: WinPT + KeePass = KeePT]]<br />
* [[PuttyAgent now supports openssh/cygwin/msys]]<br />
<br />
= KeePass 2 =<br />
<br />
KeePass 2 can be regarded as the "full version" which contains many more features. Downside is that it is slower and uses more memory because it is written in C# .NET instead of pure C++/MFC (as KeePass 1).<br />
After many years, I switched to KeePass 2 in March 2015 due to the much richer feature set.<br />
Also the Android version of Keepass2Android is much better.<br />
<br />
I created the following plugins for KeePass 2:<br />
<br />
== TCATO Placeholder ==<br />
<br />
[http://keepass.info/help/v2/autotype_obfuscation.html Two-Channel Auto-Type Obfuscation (TCATO)] is a very powerful new feature of KeePass 2. Instead of just auto-typing the information, TCATO splits the information and transfers parts of it via the clipboard. This makes it much harder for keyloggers to capture the information. TCATO can be enabled/disabled on a '''per-entry''' basis.<br />
<br />
Unfortunately, TCATO does not work for all windows, for example PuTTY. Hence, often you want to enable/disable TCATO '''per auto-type sequence'''. Example: Some stupid online banking systems (e.g. BAWAK PSK has this stupid "feature") prevent usage of the clipboard in some input fields, for example when changing the password. In this case you can selectively disable TCATO for this sequence.<br />
<br />
Example:<br />
Auto-Type-Window: BAWAG P.S.K. eBanking - ebanking.bawagpsk.com*<br />
Auto-Type-Sequence: {C:Login}{DELAY 200}{USERNAME}{TAB}{PASSWORD}{ENTER}<br />
Auto-Type-Sequence: {C:change password}{TCATO:false}{PASSWORD}{TAB}{NEWPASSWORD:/PSK/}{TAB}{NEWPASSWORD:/PSK/}<br />
<br />
* [[Datei:TCATO_Placeholder_v1.2.zip|Download Plugin]]<br />
* [[Datei:TCATO_Placeholder_v1.2-src.zip|Download Source Code]]<br />
<br />
== TAN Placeholder ==<br />
<br />
This plugin provides a placeholder {USETAN:...} for use in auto typing. It can be used for logins where a TAN is required.<br />
<br />
=== Example application ===<br />
<br />
Cisco AnnyConnect Secure Client can be automated when one-way passwords as required.<br />
I create a printed list of password and safe them as TAN entires in a group called "VPN TANs". Then I have the following auto-type sequence:<br />
<br />
Auto-Type-Window: Cisco AnyConnect | su-vpn.stanford.edu<br />
Auto-Type-Sequence: {C:with TAN}{DELAY 1000}{PASSWORD}{ENTER}{DELAY 2000}{USETAN:T:VPN TANs}{ENTER}{DELAY 2000}{ENTER}<br />
<br />
=== How to use ===<br />
<br />
The placeholder has one of the following forms:<br />
<br />
{USETAN:I:group-uuid}<br />
{USETAN:T:group-name}<br />
<br />
Here, "I" references the group with the TANs using its UUID: group-uuid must be UUID of the group, as a hex string.<br />
"T" references the group with the group title. If there are multiple groups with the same name, the first one is taken!<br />
<br />
It is strongly advised to use the group UUID since it allows for uniquely referencing a TAN group. Since KeePass 2.45, the group UUID can be found in the group properties.<br />
(For KeePass before 2.45, one way is to export the TAN group to "KeePass XML (2.x)" and look for the tag <UUID>.<br />
Important: The UUID from this tag is in BASE64. You need to convert it to a hex string manually, for example on http://tomeko.net/online_tools/base64.php?lang=en ).<br />
<br />
Use the T-version if you update your TANs frequently in different groups. Take care that the group is unique!<br />
<br />
Optionally, if your TAN entries are numbered, a specific TAN number can be provided as last argument:<br />
<br />
{USETAN:I:group-uuid:tan nr}<br />
{USETAN:T:group-name:tan nr}<br />
<br />
=== Examples ===<br />
<br />
Enter Username, the next available TAN and then password. First, the group is identified by its title, second by its UUID.<br />
<br />
{USERNAME}{TAB}{USETAN:T:My TAN List}{PASSWORD}{ENTER}<br />
{USERNAME}{TAB}{USETAN:I:2A5FF84677A91D49B4227D564B7698AF}{PASSWORD}{ENTER}<br />
<br />
Additionally, request than the TAN with number 6 is entered:<br />
<br />
{USERNAME}{TAB}{USETAN:T:My TAN List:6}{PASSWORD}{ENTER}<br />
{USERNAME}{TAB}{USETAN:I:2A5FF84677A91D49B4227D564B7698AF:6}{PASSWORD}{ENTER}<br />
<br />
<br />
=== Error messages ===<br />
<br />
"The following auto-type placeholder or special key code is unknown/unsupported: {USETAN...}".<br />
<br />
Make sure the placeholder has exactly the forms described above with the first argument either T or I.<br />
If you use an UUID, make sure that it has the right form, i.e. it is 32 bytes<br />
long and consists only of A-F, 0-9. Example: 2A5FF84677A91D49B4227D564B7698AF<br />
<br />
<br />
"{USETAN}: Supplied group was not found"<br />
<br />
Make sure you use the correct UUID. When referencing using the title, make sure you use the right case (case matters).<br />
<br />
"{USETAN}: Either TAN entry was not found or no TAN available"<br />
If you supplied an ID for the TAN, the TAN entry was either not found or has been used. If you did not supply a specific ID, there are no more free TANs available in the group. If you receive this message but you have free TANs in the group, make sure the group name is unique when referencing it by its title!<br />
<br />
=== Download ===<br />
<br />
* [[Datei:TAN_Placeholder-v1.1.zip]]<br />
* [[Datei:TAN_Placeholder-v1.1-src.zip]]<br />
<br />
= Comments =<br />
<br />
<comments />{{:{{TALKSPACE}}:{{PAGENAME}}}}</div>Nikihttp://niki.hammler.net/w/index.php?title=Notes&diff=1664Notes2020-04-01T04:04:21Z<p>Niki: </p>
<hr />
<div>Some notes on IT problems (not worth a weblog article):<br />
<br />
* [[Lenovo Auto-Rotate Patch rotates internal screen]]<br />
* [[Stanford farmshare with NX]]<br />
* [[OpenWRT abets holes in firewall]]<br />
* [[Enter tyan BIOS]]<br />
* [[Zarafa ntlm auth problems]]<br />
* [[Debian fails to boot: libm.so.6 is missing in initrd]]<br />
* [[Lenovo X230t and Win8]]<br />
* [[Windows Userprofile Migration]]<br />
* [[Linux Hotplugging]]<br />
<br />
* [[git-annex]]<br />
<br />
* [[Android Device Encryption]]<br />
* [[Samsung Galaxy S3 low-level stuff]]<br />
<br />
* [[Printer driver was not installed. Operation could not be completed (error 0x00000002)]]<br />
<br />
* [[MyPhoneExplorer: Lock Workstation|MyPhoneExplorer: Lock Workstation Plugin]]<br />
* [[MyPhoneExplorer: Reconnect USB Plugin]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Lenovo_Auto-Rotate_Patch_rotates_internal_screen&diff=1663Lenovo Auto-Rotate Patch rotates internal screen2020-04-01T04:03:08Z<p>Niki: /* Comments */</p>
<hr />
<div><section begin="head"/><br />
Lenovo tablets (X220t, X230t, possibly others) have the nice feature of automatically rotating the screen orientation between laptop mode and tablet mode using the inertia sensor for the HDD.<br />
<br />
Unfortunately this does not work with multiple monitors as it always rotates the primary monitor. For example, when the laptop is docked and connected to an external monitor, a switch between tablet mode and laptop mode would rotate the external monitor and not the internal screen, as it should. This happens only when the external monitor is configured as primary display but more often than not, this is the case.<br />
<br />
This small patch fixes this issue.<br />
<section end="head"/><br />
<br />
Lenovos "ThinkPad Tablet Shortcut Menu" always rotates the primary display, independent if it is the internal tablet display or not. This is super annoying because it messes up screen rotation completely.<br />
<br />
Generally, to make auto rotation work, the following software must be installed:<br />
<br />
* Lenovo Active Protection System<br />
* ThinkPad Tablet Shortcut Menu<br />
<br />
To always rotate the internal screen (and not the primary display) when you turn your laptop screen, follow these instructions:<br />
<br />
* Download LenovoAutoRotatorPatch.zip below<br />
* Go to c:\Program Files (x86)\ThinkPad\Tablet Shortcut\<br />
* Rename ScreenRotation.exe to ScreenRotation.exe.orig<br />
* Copy the ScreenRotation.exe from the zip to this directory<br />
<br />
<br />
= Download=<br />
<br />
<br />
[[Media:LenovoAutoRotatorPatch.zip]]<br />
<br />
= Keywords =<br />
<br />
* Lenovo<br />
* Thinkpad<br />
* auto-rotate<br />
* Tablet Shortcut Menu<br />
* ThinkVantage<br />
* tablet mode<br />
* Lenovo Active Protection System<br />
* X220t, X230t, ...<br />
<br />
<br />
<br />
[[Kategorie:Weblog]]<br />
[[Category:Weblog]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Lenovo_Auto-Rotate_Patch_rotates_internal_screen&diff=1662Lenovo Auto-Rotate Patch rotates internal screen2020-04-01T04:02:54Z<p>Niki: </p>
<hr />
<div><section begin="head"/><br />
Lenovo tablets (X220t, X230t, possibly others) have the nice feature of automatically rotating the screen orientation between laptop mode and tablet mode using the inertia sensor for the HDD.<br />
<br />
Unfortunately this does not work with multiple monitors as it always rotates the primary monitor. For example, when the laptop is docked and connected to an external monitor, a switch between tablet mode and laptop mode would rotate the external monitor and not the internal screen, as it should. This happens only when the external monitor is configured as primary display but more often than not, this is the case.<br />
<br />
This small patch fixes this issue.<br />
<section end="head"/><br />
<br />
Lenovos "ThinkPad Tablet Shortcut Menu" always rotates the primary display, independent if it is the internal tablet display or not. This is super annoying because it messes up screen rotation completely.<br />
<br />
Generally, to make auto rotation work, the following software must be installed:<br />
<br />
* Lenovo Active Protection System<br />
* ThinkPad Tablet Shortcut Menu<br />
<br />
To always rotate the internal screen (and not the primary display) when you turn your laptop screen, follow these instructions:<br />
<br />
* Download LenovoAutoRotatorPatch.zip below<br />
* Go to c:\Program Files (x86)\ThinkPad\Tablet Shortcut\<br />
* Rename ScreenRotation.exe to ScreenRotation.exe.orig<br />
* Copy the ScreenRotation.exe from the zip to this directory<br />
<br />
<br />
= Download=<br />
<br />
<br />
[[Media:LenovoAutoRotatorPatch.zip]]<br />
<br />
= Keywords =<br />
<br />
* Lenovo<br />
* Thinkpad<br />
* auto-rotate<br />
* Tablet Shortcut Menu<br />
* ThinkVantage<br />
* tablet mode<br />
* Lenovo Active Protection System<br />
* X220t, X230t, ...<br />
<br />
= Comments =<br />
<br />
<comments />{{:{{TALKSPACE}}:{{PAGENAME}}}}<br />
<br />
[[Kategorie:Weblog]]<br />
[[Category:Weblog]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Lenovo_Auto-Rotate_Patch_rotates_internal_screen&diff=1661Lenovo Auto-Rotate Patch rotates internal screen2020-04-01T04:01:16Z<p>Niki: /* Download */</p>
<hr />
<div><section begin="head"/><br />
Lenovo tablets (X220t, X230t, possibly others) have the nice feature of automatically rotating the screen orientation between laptop mode and tablet mode using the inertia sensor for the HDD.<br />
<br />
Unfortunately this does not work with multiple monitors as it always rotates the primary monitor. For example, when the laptop is docked and connected to an external monitor, a switch between tablet mode and laptop mode would rotate the external monitor and not the internal screen, as it should. This happens only when the external monitor is configured as primary display but more often than not, this is the case.<br />
<br />
This small patch fixes this issue.<br />
<section end="head"/><br />
<br />
Lenovos "ThinkPad Tablet Shortcut Menu" always rotates the primary display, independent if it is the internal tablet display or not. This is super annoying because it messes up screen rotation completely.<br />
<br />
Generally, to make auto rotation work, the following software must be installed:<br />
<br />
* Lenovo Active Protection System<br />
* ThinkPad Tablet Shortcut Menu<br />
<br />
To always rotate the internal screen (and not the primary display) when you turn your laptop screen, follow these instructions:<br />
<br />
* Download LenovoAutoRotatorPatch.zip below<br />
* Go to c:\Program Files (x86)\ThinkPad\Tablet Shortcut\<br />
* Rename ScreenRotation.exe to ScreenRotation.exe.orig<br />
* Copy the ScreenRotation.exe from the zip to this directory<br />
<br />
<br />
= Download=<br />
<br />
<br />
[[Media:LenovoAutoRotatorPatch.zip]]<br />
<br />
= Keywords =<br />
<br />
* Lenovo<br />
* Thinkpad<br />
* auto-rotate<br />
* Tablet Shortcut Menu<br />
* ThinkVantage<br />
* tablet mode<br />
* Lenovo Active Protection System<br />
* X220t, X230t, ...<br />
<br />
= Comments =<br />
<br />
<comments />{{:{{TALKSPACE}}:{{PAGENAME}}}}<br />
<br />
[[Kategorie:Weblog]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Datei:LenovoAutoRotatorPatch.zip&diff=1660Datei:LenovoAutoRotatorPatch.zip2020-04-01T03:58:24Z<p>Niki: </p>
<hr />
<div></div>Nikihttp://niki.hammler.net/w/index.php?title=Lenovo_Auto-Rotate_Patch_rotates_internal_screen&diff=1659Lenovo Auto-Rotate Patch rotates internal screen2020-04-01T03:38:25Z<p>Niki: Die Seite wurde neu angelegt: „<section begin="head"/> Lenovo tablets (X220t, X230t, possibly others) have the nice feature of automatically rotating the screen orientation between laptop mo…“</p>
<hr />
<div><section begin="head"/><br />
Lenovo tablets (X220t, X230t, possibly others) have the nice feature of automatically rotating the screen orientation between laptop mode and tablet mode using the inertia sensor for the HDD.<br />
<br />
Unfortunately this does not work with multiple monitors as it always rotates the primary monitor. For example, when the laptop is docked and connected to an external monitor, a switch between tablet mode and laptop mode would rotate the external monitor and not the internal screen, as it should. This happens only when the external monitor is configured as primary display but more often than not, this is the case.<br />
<br />
This small patch fixes this issue.<br />
<section end="head"/><br />
<br />
Lenovos "ThinkPad Tablet Shortcut Menu" always rotates the primary display, independent if it is the internal tablet display or not. This is super annoying because it messes up screen rotation completely.<br />
<br />
Generally, to make auto rotation work, the following software must be installed:<br />
<br />
* Lenovo Active Protection System<br />
* ThinkPad Tablet Shortcut Menu<br />
<br />
To always rotate the internal screen (and not the primary display) when you turn your laptop screen, follow these instructions:<br />
<br />
* Download LenovoAutoRotatorPatch.zip below<br />
* Go to c:\Program Files (x86)\ThinkPad\Tablet Shortcut\<br />
* Rename ScreenRotation.exe to ScreenRotation.exe.orig<br />
* Copy the ScreenRotation.exe from the zip to this directory<br />
<br />
<br />
= Download=<br />
<br />
[[Datei:LenovoAutoRotatorPatch.zip]]<br />
<br />
= Keywords =<br />
<br />
* Lenovo<br />
* Thinkpad<br />
* auto-rotate<br />
* Tablet Shortcut Menu<br />
* ThinkVantage<br />
* tablet mode<br />
* Lenovo Active Protection System<br />
* X220t, X230t, ...<br />
<br />
= Comments =<br />
<br />
<comments />{{:{{TALKSPACE}}:{{PAGENAME}}}}<br />
<br />
[[Kategorie:Weblog]]</div>Nikihttp://niki.hammler.net/w/index.php?title=GPG:_WinPT_%2B_KeePass_%3D_KeePT&diff=1658GPG: WinPT + KeePass = KeePT2020-03-25T15:04:36Z<p>Niki: </p>
<hr />
<div><section begin="head"/><br />
'''KeePT''' is my new plugin for KeePass which allows to use WinPT from KeePass. There is no need to start both KeePass and WinPT at the same time. KeePT allows to access all functions from WinPT from KeePT's tray menu. Furthermore, the plugin registers WinPT's hot keys and allows to pass the GPG passphrase to WinPT.<br />
But what was my intention? I can just use KeePass's hot key functionality to pass the GPG password. However, I hate to startup up dozens of application which all occupy an icon in the system tray. This is even more true when I do not use the applications regularly. This was already the reason for my PuttyAgent plugin: No need to start both KeePass and pageant.exe. The same is true for KeePT: The main and unspectacular purpose of this plugin is to<br />
start WinPT (and hence GPG) from within KeePass. The minor purpose is to pass the GPG password from KeePass to WinPT.<br />
This plugin ''requires'' WinPT. At first, I wanted to compile WinPT into a DLL, just as I did it for PuttyAgent. But after spending hours in trying to compile<br />
the old WinPT code I gave up and decided to control the pre-compiled binary. This has another advantage: The plugin occupies only 80kB (written purely in<br />
C++ with WinAPI) whereas the whole WinPT (occupying 1-2MB!) is only loaded when needed.<br />
<section end="head"/><br />
<br />
= How does the plugin work? =<br />
<br />
Basically, it displays WinPT's tray menu in the tray menu of KeePass ("KeePT...") and in the Tools menu. The menu is directly read form WinPT.exe.<br />
After selecting a menu entry, the plugin creates a new thread in which WinPT is started and the specific action launched.<br />
<br />
[[Datei:KeePT_Tray.png|center]]<br />
<br />
== Starting and exiting WinPT ==<br />
<br />
The plugin searches for an existing WinPT instance and sends the commands to this instance first. If no instance is running, the plugin uses CreateProcess to execute WinPT. The path to WinPT.exe can be set in the plugin settings:<br />
<br />
[[Datei:KeePT_Settings.png|center]]<br />
<br />
If the plugin started WinPT, there are two options: Either WinPT keeps running or the plugin waits until all dialogs from WinPT are closed and terminates the application again. This (default) behavior can be set in the settings (see screenshot) by: '''Close WinPT.exe if it was started by us'''.<br />
<br />
<br />
== Using WinPT hot keys ==<br />
<br />
WinPT provides the option to set hot keys in the settings menu. KeePT can try to register these hot keys in the plugin settings with '''Try to register WinPT's global hot keys''' (see screenshot).<br />
<br />
When this option is set, the plugin will read out the hot key configuration by WinPT from the registry, register the hot keys and pass them to WinPT (the same <br />
way as the action would be selected from the tray menu). Before starting WinPT, the hot keys are unregistered, such that they are registered by WinPT. This <br />
means: As soon as WinPT.exe is started by the plugin, the hot keys are processed by WinPT itself.<br />
<br />
'''Note 1''': When the option "Close WinPT.exe if it was started by us" is not used, this option should be avoided as well, since both WinPT and KeePT will try to register the hot keys. KeePT will display an error message in that the keys are already registered in this case.<br />
<br />
'''Note 2''': This option does not work with the portable version of GnuPT since the hot keys are not permanently stored in the registry in this case.<br />
<br />
'''Note 3''': The CTRL + ALT + F key (flushing the passphrase) is not supported by KeePT since WinPT does not provide a WM_COMMAND for that.<br />
<br />
== Passing the passphrase from KeePass to WinPT ==<br />
<br />
In order to support passing the passphrase, the plugin injects itself into the running WinPT instance and overwrites the DialogBox API function which is used by WinPT to display the password dialog. In this case, a request is sent to the plugin and the plugin searches the KeePass database for an entry matching the<br />
key id. If it is found, the password is passed to WinPT. If there is an error, the default password dialog is displayed.<br />
<br />
When the database is locked, the plugin attempts to unlock the workspace by displaying the master password dialog.<br />
<br />
There might be cases when injecting the DLL into WinPT does not work. In this case, the plugin works except for passing the passphrase and an error message is displayed.<br />
<br />
The GPG passphrase is found in the database by looking at the Notes-entry and finding a matching<br />
<br />
[[Datei:KeePT_Entry.png|center]]<br />
<br />
entry where 0x022F21C2 represents the key id for the private key. The key id can be found in WinPT using the key manager column 'Key-ID or by decrypting a message with WinPT. WinPT then displays the key id which is used to decrypt this message.<br />
<br />
[[Datei:WinPT_Decrypt.png|center]]<br />
<br />
== Notes on Security ==<br />
<br />
The plugin takes care of secure handling of the GPG password. The passphrase is not passed by WM_COPYDATA or any window message but rather by using shared memory. In order to avoid simple memory readouts, the shared memory is created using CreateFileMapping and MapViewOfFile rather than using "pragma data_seg" in the DLL. The principle is borrowed from PuTTY's Pageant: The injected WinPT first creates a FileMapping where the owner is explicitely set to the current SID and no further ACLs are set. This means that only processes of the same user can access the shared memory. WinPT then writes the key ID into this memory region and sends the name of the file mapping via WM_COPYDATA to KeePT. KeePT explicitely checks if the owner of the file mapping and the SID of the KeePass match. Afterwards the password is written into this region by KeePT. The memory for the passphrase is memset to 0x00 as soon as the password is not needed any more and in case of any errors.<br />
<br />
Additionally, the plugin forces the page containing the password to reside in RAM by using VirtualLock (i.e., the page is never swapped out to disk).<br />
<br />
Finally, the original password dialog of WinPT is used to allocate memory for the password. Basically, the WM_INITDIALOG is hooked, the password field is set by SetDlgItemText, which sends WM_SETTEXT and finally the OK button is pressed. The basic variant would send the password directly with SetDlgItemText. However, this trivially would reveal the password by Spy+. Instead, the memory is allocated by writing 0xFF spaces with SetDlgItemText and afterwards it is overwritten by the real password using memcpy.<br />
<br />
= Installation=<br />
<br />
Just copy the files to the program directory of KeePass and restart KeePass. The plugin can be configured in the plugin settings.<br />
<br />
= Download =<br />
<br />
Please download the plugin from http://keepass.info/plugins.html.<br />
<br />
= Comments =<br />
<br />
<br />
(Comments are disabled)<br />
<!-- <comments />{{:{{TALKSPACE}}:{{PAGENAME}}}} --><br />
<br />
<br />
<br />
[[Kategorie:Weblog]]</div>Nikihttp://niki.hammler.net/w/index.php?title=GPG:_WinPT_%2B_KeePass_%3D_KeePT&diff=1657GPG: WinPT + KeePass = KeePT2020-03-25T15:04:18Z<p>Niki: </p>
<hr />
<div><section begin="head"/><br />
'''KeePT''' is my new plugin for KeePass which allows to use WinPT from KeePass. There is no need to start both KeePass and WinPT at the same time. KeePT allows to access all functions from WinPT from KeePT's tray menu. Furthermore, the plugin registers WinPT's hot keys and allows to pass the GPG passphrase to WinPT.<br />
But what was my intention? I can just use KeePass's hot key functionality to pass the GPG password. However, I hate to startup up dozens of application which all occupy an icon in the system tray. This is even more true when I do not use the applications regularly. This was already the reason for my PuttyAgent plugin: No need to start both KeePass and pageant.exe. The same is true for KeePT: The main and unspectacular purpose of this plugin is to<br />
start WinPT (and hence GPG) from within KeePass. The minor purpose is to pass the GPG password from KeePass to WinPT.<br />
This plugin ''requires'' WinPT. At first, I wanted to compile WinPT into a DLL, just as I did it for PuttyAgent. But after spending hours in trying to compile<br />
the old WinPT code I gave up and decided to control the pre-compiled binary. This has another advantage: The plugin occupies only 80kB (written purely in<br />
C++ with WinAPI) whereas the whole WinPT (occupying 1-2MB!) is only loaded when needed.<br />
<section end="head"/><br />
<br />
= How does the plugin work? =<br />
<br />
Basically, it displays WinPT's tray menu in the tray menu of KeePass ("KeePT...") and in the Tools menu. The menu is directly read form WinPT.exe.<br />
After selecting a menu entry, the plugin creates a new thread in which WinPT is started and the specific action launched.<br />
<br />
[[Datei:KeePT_Tray.png|center]]<br />
<br />
== Starting and exiting WinPT ==<br />
<br />
The plugin searches for an existing WinPT instance and sends the commands to this instance first. If no instance is running, the plugin uses CreateProcess to execute WinPT. The path to WinPT.exe can be set in the plugin settings:<br />
<br />
[[Datei:KeePT_Settings.png|center]]<br />
<br />
If the plugin started WinPT, there are two options: Either WinPT keeps running or the plugin waits until all dialogs from WinPT are closed and terminates the application again. This (default) behavior can be set in the settings (see screenshot) by: '''Close WinPT.exe if it was started by us'''.<br />
<br />
<br />
== Using WinPT hot keys ==<br />
<br />
WinPT provides the option to set hot keys in the settings menu. KeePT can try to register these hot keys in the plugin settings with '''Try to register WinPT's global hot keys''' (see screenshot).<br />
<br />
When this option is set, the plugin will read out the hot key configuration by WinPT from the registry, register the hot keys and pass them to WinPT (the same <br />
way as the action would be selected from the tray menu). Before starting WinPT, the hot keys are unregistered, such that they are registered by WinPT. This <br />
means: As soon as WinPT.exe is started by the plugin, the hot keys are processed by WinPT itself.<br />
<br />
'''Note 1''': When the option "Close WinPT.exe if it was started by us" is not used, this option should be avoided as well, since both WinPT and KeePT will try to register the hot keys. KeePT will display an error message in that the keys are already registered in this case.<br />
<br />
'''Note 2''': This option does not work with the portable version of GnuPT since the hot keys are not permanently stored in the registry in this case.<br />
<br />
'''Note 3''': The CTRL + ALT + F key (flushing the passphrase) is not supported by KeePT since WinPT does not provide a WM_COMMAND for that.<br />
<br />
== Passing the passphrase from KeePass to WinPT ==<br />
<br />
In order to support passing the passphrase, the plugin injects itself into the running WinPT instance and overwrites the DialogBox API function which is used by WinPT to display the password dialog. In this case, a request is sent to the plugin and the plugin searches the KeePass database for an entry matching the<br />
key id. If it is found, the password is passed to WinPT. If there is an error, the default password dialog is displayed.<br />
<br />
When the database is locked, the plugin attempts to unlock the workspace by displaying the master password dialog.<br />
<br />
There might be cases when injecting the DLL into WinPT does not work. In this case, the plugin works except for passing the passphrase and an error message is displayed.<br />
<br />
The GPG passphrase is found in the database by looking at the Notes-entry and finding a matching<br />
<br />
[[Datei:KeePT_Entry.png|center]]<br />
<br />
entry where 0x022F21C2 represents the key id for the private key. The key id can be found in WinPT using the key manager column 'Key-ID or by decrypting a message with WinPT. WinPT then displays the key id which is used to decrypt this message.<br />
<br />
[[Datei:WinPT_Decrypt.png|center]]<br />
<br />
== Notes on Security ==<br />
<br />
The plugin takes care of secure handling of the GPG password. The passphrase is not passed by WM_COPYDATA or any window message but rather by using shared memory. In order to avoid simple memory readouts, the shared memory is created using CreateFileMapping and MapViewOfFile rather than using "pragma data_seg" in the DLL. The principle is borrowed from PuTTY's Pageant: The injected WinPT first creates a FileMapping where the owner is explicitely set to the current SID and no further ACLs are set. This means that only processes of the same user can access the shared memory. WinPT then writes the key ID into this memory region and sends the name of the file mapping via WM_COPYDATA to KeePT. KeePT explicitely checks if the owner of the file mapping and the SID of the KeePass match. Afterwards the password is written into this region by KeePT. The memory for the passphrase is memset to 0x00 as soon as the password is not needed any more and in case of any errors.<br />
<br />
Additionally, the plugin forces the page containing the password to reside in RAM by using VirtualLock (i.e., the page is never swapped out to disk).<br />
<br />
Finally, the original password dialog of WinPT is used to allocate memory for the password. Basically, the WM_INITDIALOG is hooked, the password field is set by SetDlgItemText, which sends WM_SETTEXT and finally the OK button is pressed. The basic variant would send the password directly with SetDlgItemText. However, this trivially would reveal the password by Spy+. Instead, the memory is allocated by writing 0xFF spaces with SetDlgItemText and afterwards it is overwritten by the real password using memcpy.<br />
<br />
= Installation=<br />
<br />
Just copy the files to the program directory of KeePass and restart KeePass. The plugin can be configured in the plugin settings.<br />
<br />
= Download =<br />
<br />
Please download the plugin from http://keepass.info/plugins.html.<br />
<br />
= Comments =<br />
<br />
<br />
<!-- <comments />{{:{{TALKSPACE}}:{{PAGENAME}}}} --><br />
<br />
<br />
<br />
[[Kategorie:Weblog]]</div>Nikihttp://niki.hammler.net/w/index.php?title=GPG:_WinPT_%2B_KeePass_%3D_KeePT&diff=1656GPG: WinPT + KeePass = KeePT2020-03-25T15:03:01Z<p>Niki: </p>
<hr />
<div><section begin="head"/><br />
'''KeePT''' is my new plugin for KeePass which allows to use WinPT from KeePass. There is no need to start both KeePass and WinPT at the same time. KeePT allows to access all functions from WinPT from KeePT's tray menu. Furthermore, the plugin registers WinPT's hot keys and allows to pass the GPG passphrase to WinPT.<br />
But what was my intention? I can just use KeePass's hot key functionality to pass the GPG password. However, I hate to startup up dozens of application which all occupy an icon in the system tray. This is even more true when I do not use the applications regularly. This was already the reason for my PuttyAgent plugin: No need to start both KeePass and pageant.exe. The same is true for KeePT: The main and unspectacular purpose of this plugin is to<br />
start WinPT (and hence GPG) from within KeePass. The minor purpose is to pass the GPG password from KeePass to WinPT.<br />
This plugin ''requires'' WinPT. At first, I wanted to compile WinPT into a DLL, just as I did it for PuttyAgent. But after spending hours in trying to compile<br />
the old WinPT code I gave up and decided to control the pre-compiled binary. This has another advantage: The plugin occupies only 80kB (written purely in<br />
C++ with WinAPI) whereas the whole WinPT (occupying 1-2MB!) is only loaded when needed.<br />
<section end="head"/><br />
<br />
= How does the plugin work? =<br />
<br />
Basically, it displays WinPT's tray menu in the tray menu of KeePass ("KeePT...") and in the Tools menu. The menu is directly read form WinPT.exe.<br />
After selecting a menu entry, the plugin creates a new thread in which WinPT is started and the specific action launched.<br />
<br />
[[Datei:KeePT_Tray.png|center]]<br />
<br />
== Starting and exiting WinPT ==<br />
<br />
The plugin searches for an existing WinPT instance and sends the commands to this instance first. If no instance is running, the plugin uses CreateProcess to execute WinPT. The path to WinPT.exe can be set in the plugin settings:<br />
<br />
[[Datei:KeePT_Settings.png|center]]<br />
<br />
If the plugin started WinPT, there are two options: Either WinPT keeps running or the plugin waits until all dialogs from WinPT are closed and terminates the application again. This (default) behavior can be set in the settings (see screenshot) by: '''Close WinPT.exe if it was started by us'''.<br />
<br />
<br />
== Using WinPT hot keys ==<br />
<br />
WinPT provides the option to set hot keys in the settings menu. KeePT can try to register these hot keys in the plugin settings with '''Try to register WinPT's global hot keys''' (see screenshot).<br />
<br />
When this option is set, the plugin will read out the hot key configuration by WinPT from the registry, register the hot keys and pass them to WinPT (the same <br />
way as the action would be selected from the tray menu). Before starting WinPT, the hot keys are unregistered, such that they are registered by WinPT. This <br />
means: As soon as WinPT.exe is started by the plugin, the hot keys are processed by WinPT itself.<br />
<br />
'''Note 1''': When the option "Close WinPT.exe if it was started by us" is not used, this option should be avoided as well, since both WinPT and KeePT will try to register the hot keys. KeePT will display an error message in that the keys are already registered in this case.<br />
<br />
'''Note 2''': This option does not work with the portable version of GnuPT since the hot keys are not permanently stored in the registry in this case.<br />
<br />
'''Note 3''': The CTRL + ALT + F key (flushing the passphrase) is not supported by KeePT since WinPT does not provide a WM_COMMAND for that.<br />
<br />
== Passing the passphrase from KeePass to WinPT ==<br />
<br />
In order to support passing the passphrase, the plugin injects itself into the running WinPT instance and overwrites the DialogBox API function which is used by WinPT to display the password dialog. In this case, a request is sent to the plugin and the plugin searches the KeePass database for an entry matching the<br />
key id. If it is found, the password is passed to WinPT. If there is an error, the default password dialog is displayed.<br />
<br />
When the database is locked, the plugin attempts to unlock the workspace by displaying the master password dialog.<br />
<br />
There might be cases when injecting the DLL into WinPT does not work. In this case, the plugin works except for passing the passphrase and an error message is displayed.<br />
<br />
The GPG passphrase is found in the database by looking at the Notes-entry and finding a matching<br />
<br />
[[Datei:KeePT_Entry.png|center]]<br />
<br />
entry where 0x022F21C2 represents the key id for the private key. The key id can be found in WinPT using the key manager column 'Key-ID or by decrypting a message with WinPT. WinPT then displays the key id which is used to decrypt this message.<br />
<br />
[[Datei:WinPT_Decrypt.png|center]]<br />
<br />
== Notes on Security ==<br />
<br />
The plugin takes care of secure handling of the GPG password. The passphrase is not passed by WM_COPYDATA or any window message but rather by using shared memory. In order to avoid simple memory readouts, the shared memory is created using CreateFileMapping and MapViewOfFile rather than using "pragma data_seg" in the DLL. The principle is borrowed from PuTTY's Pageant: The injected WinPT first creates a FileMapping where the owner is explicitely set to the current SID and no further ACLs are set. This means that only processes of the same user can access the shared memory. WinPT then writes the key ID into this memory region and sends the name of the file mapping via WM_COPYDATA to KeePT. KeePT explicitely checks if the owner of the file mapping and the SID of the KeePass match. Afterwards the password is written into this region by KeePT. The memory for the passphrase is memset to 0x00 as soon as the password is not needed any more and in case of any errors.<br />
<br />
Additionally, the plugin forces the page containing the password to reside in RAM by using VirtualLock (i.e., the page is never swapped out to disk).<br />
<br />
Finally, the original password dialog of WinPT is used to allocate memory for the password. Basically, the WM_INITDIALOG is hooked, the password field is set by SetDlgItemText, which sends WM_SETTEXT and finally the OK button is pressed. The basic variant would send the password directly with SetDlgItemText. However, this trivially would reveal the password by Spy+. Instead, the memory is allocated by writing 0xFF spaces with SetDlgItemText and afterwards it is overwritten by the real password using memcpy.<br />
<br />
= Installation=<br />
<br />
Just copy the files to the program directory of KeePass and restart KeePass. The plugin can be configured in the plugin settings.<br />
<br />
= Download =<br />
<br />
Please download the plugin from http://keepass.info/plugins.html.<br />
<br />
= Comments =<br />
<br />
<br />
<br />
[[Kategorie:Weblog]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1655Server2020-03-09T16:16:26Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020-09.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis/nobaq from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1654Server2020-03-07T05:10:26Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis from i386 to amd64. Upgrade mail lenny->jessie</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1653Server2020-03-06T02:59:01Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis. Crossgrade(!) retis from i386 to amd64</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1651Server2020-03-05T05:32:10Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix (+nobaq)</td><br />
</tr><br />
<tr><br />
<td>05.03.2020</td><td>Upgrade (over Debian 8) to Debian 10 (buster) on retis</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1650Server2019-10-22T04:19:33Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster) on radix</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1649Server2019-08-26T10:29:49Z<p>Niki: </p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
<tr><br />
<td>26.08.2019</td><td>Upgrade (over Debian 9) to Debian 10 (buster)</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Server&diff=1643Server2017-01-15T05:48:59Z<p>Niki: /* Software */</p>
<hr />
<div><table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>CPU(s)</td><td>2x Intel(R) Xeon(TM) CPU 3.40GHz with HT (4 virtual cores), 64 bit</td><br />
</tr><br />
<tr><br />
<td>RAM</td><td>8 GB</Td><br />
</tr><br />
<tr><br />
<td>Hard drives</td><td>2x1TB in RAID1 (md), SATA<br/>3TB Multimedia, SATA</Td><br />
</tr><br />
</table><br />
<br />
This hardware node is called "radix" and holds a bunch of virtual machines.<br />
An idential hardware node [[vicari]] is used as a backup server and acts as a failover.<br />
Thanks to Ovvi for the hardware :-)<br />
<br />
The following systems run on this server:<br />
<br />
* [[retis|retis.nobaq.net]]<br />
* ...<br />
<br />
== Software ==<br />
<br />
[[Bild:Powered by Linux.png|right]]<br />
<br />
[[Bild:Powered by Debian.png|right]]<br />
<br />
[[Bild:Powered by OpenVZ.png|right]]<br />
<br />
[[Bild:Powered by Apache.png|right]]<br />
<br />
[[Bild:Powered by PHP.gif|right]]<br />
<br />
[[Bild:goPHP5.png|right]]<br />
<br />
[[Bild:Powered by mySQL.png|right]]<br />
<br />
Als Server verwende ich Debian GNU/Linux mit VServer. [...]<br />
<br />
Linux ist für mich das Serverbetriebssystem der Wahl. Kein anderes System hat bei mir so lange überlebt und gute Dienste geleistet. Für Windows User mag sich das sehr unglaubwürdig anhören, aber meine Debian Installation läuft bereits seit 2001! In der folgenden Tabelle hab ich ein paar Daten die mir noch bekannt sind festgehalten. Zum ersten Mal hab ich das System am 15.08.2001 installiert. Davor habe ich längere Zeit SuSE verwendet, davor kurzzeitig RedHat.<br />
<br />
<br />
<table align="center" border="1" cellspacing="0" cellpadding="3"><br />
<tr><br />
<td>15.08.2001</td><td>Erstinstallation meines Systems</td><br />
</tr><br />
<tr><br />
<td>03.04.2003</td><td>Upgrade auf woody (?)</td><br />
</tr><br />
<tr><br />
<td>05.07.2004</td><td>"Black Monday" ;-) http://www.nobaq.net/~niki/historic/2004/old.php</td><br />
</tr><br />
<tr><br />
<td>10.10.2004</td><td>Grobe Systemwiderherstellung abgeschlossen</td><br />
</tr><br />
<tr><br />
<td>12.06.2005</td><td>Upgrade auf sarge</td><br />
</tr><br />
<tr><br />
<td>19.04.2007</td><td>Upgrade auf etch</td><br />
</tr><br />
<tr><br />
<td>07.09.2007</td><td>Migration auf Linux VServer. Derzeitiges System wird host-System (radix) und die Configs auf neue VServer kopiert. Die meisten Aufgaben übernimmt der neue VServer "nobaq"</td><br />
</tr><br />
<tr><br />
<td>06.04.2009</td><td>Upgrade auf lenny</td><br />
</tr><br />
<tr><br />
<td>07.04.2009</td><td>Migration von Linux VServer auf OpenVZ</td><br />
</tr><br />
<tr><br />
<td>21.04.2009</td><td>Installation eines Software RAIDs (level 1 auf 2 1TB Platten)</td><br />
</tr><br />
<tr><br />
<td>09.02.2011</td><td>Upgrade auf squeeze (auf virtuellen Servern mail, ns, logger)</td><br />
</tr><br />
<tr><br />
<td>10.03.2011</td><td>Upgrade auf squeeze auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>15.03.2011</td><td>Upgrade auf squeeze auf retis</td><br />
</tr><br />
<tr><br />
<td>22./23.04.2011</td><td>Upgrade nobaq auf squeeze</td><br />
</tr><br />
<tr><br />
<td>26.04.2011</td><td>New hardware: 2 Xeon 3.4 Ghz on Tyan S5350, 8GB RAM. Thanks Ovvi :-)</td><br />
</tr><br />
<tr><br />
<td>24./26.07.2013</td><td>Upgrade auf wheezy auf radix (vormals nobaq)</td><br />
</tr><br />
<tr><br />
<td>27.07.2013</td><td>Upgrade auf wheezy auf ns, logger, core, mail, rialto, retis, slave, vicari</td><br />
</tr><br />
<tr><br />
<td>19.04.2014</td><td>Upgrade auf wheezy auf nobaq</td><br />
</tr><br />
<tr><br />
<td>24.12.2014</td><td>Both servers upgraded to 16GB ECC Ram. Upgraded to ZFS!</td><br />
</tr><br />
<tr><br />
<td>Christmas 2016/17</td><td>Upgrade all systems to jessie. Replaced WRT54GL with Mikrotik Routerboard.</td><br />
</tr><br />
</table><br />
<br />
Wie ich zu Linux gekommen bin, beschreibe ich in meiner kleinen [[Linux Geschichte]].<br />
<br />
Irgendwann im Sommer 2006 war es soweit dass ich mir Virtualisierungskonzepte genauer angeschaut habe, da einfach schon viel zu viel auf meinem Debian Server lief (gemischt private und öffentliche Sachen). Nachdem ich nach längerem Experimentieren mit Xen festgestellt habe dass es eigentlich nichts für mich ist, habe ich seit Sommer 2007 [http://linux-vserver.org Linux VServer] eingesetzt. Im April 2009 habe ich von Linux VServer auf [http://www.openvz.org OpenVZ] migriert.<br />
<br />
== Hardware ==<br />
<br />
Mein Server ist in den [[Rack|Serverschrank]] eingebaut und mittels Teleskopschienen befestigt. So kann der Server waehrend dem Betrieb herausgezogen und gewartet werden (soviel eben im Betrieb moeglich ist). Die folgenden Fotos sind leider veraltert und zeigen noch das alte Gehaeuse auf Schwerlastgleitschienen:<br />
<br />
[[Bild:server_vorne.jpg|thumb|600px|center|Vorderansicht im Rack]]<br />
<br />
[[Bild:server_vorne_offen.jpg|thumb|600px|center|Vorderansicht im Rack (offen)]]<br />
<br />
[[Bild:server_hinten.jpg|thumb|600px|center|Hinteransicht im Rack]]<br />
<br />
Auf dem letzten Photo erkennt man unter anderem die 2 ISDN Karten für meine [[Asterisk: Die mächtigste Nebenstellenanlage der Welt|Asterisk Telephonanlage]]: eine AVM Fritz! Card für den ISDN Anschluss der Telekom und eine HFC Karte für den internen S0-Bus.<br />
<br />
== Altes Gehäuse ==<br />
<br />
Vor dem Rackeinbau war der Server in einem Towerservergehäuse eingebaut. Vor allem dem redundantem Netzteil in diesem Gehäuse trauere ich nach...<br />
<br />
Hier sind noch Photos davon zu sehen:<br />
<br />
[[Bild:server1.jpg|thumb|200px|center|Aussenansicht]]<br />
<br />
[[Bild:server2.jpg|thumb|400px|center|Innenansicht Server]]<br />
<br />
[[Kategorie:Linux]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Diskussion:PuttyAgent_now_supports_openssh/cygwin/msys&diff=1642Diskussion:PuttyAgent now supports openssh/cygwin/msys2017-01-08T22:47:10Z<p>Niki: Ein Kommentar wurde von Niki über die Programmerweiterung ArticleComments abgegeben.</p>
<hr />
<div><noinclude>Kommentare zur Seite „[[PuttyAgent now supports openssh/cygwin/msys]]“<br />
<comments /><br />
----- __NOEDITSECTION__</noinclude><br />
== asmus meinte … ==<br />
<br />
<comment date="2015-02-25T20:53:50Z" name="asmus"><br />
Danke schoen!!<br />
</comment><br />
== Michael meinte … ==<br />
<br />
<comment date="2015-07-25T10:03:42Z" name="Michael"><br />
Gibts das auch mit KeePass 2.x Kompatibilität?<br />
</comment><br />
== Niki meinte … ==<br />
<br />
<comment date="2015-07-25T10:28:39Z" name="Niki"><br />
Ja: http://lechnology.com/software/keeagent/<br />
<br />
</comment><br />
== Niki meinte … ==<br />
<br />
<comment date="2015-07-25T10:30:24Z" name="Niki"><br />
More specifically: http://lechnology.com/software/keeagent/usage/tips-and-tricks/#client-mode-with-pageant<br />
<br />
I migrated to KP2 on my own ...<br />
</comment><br />
== Michael meinte … ==<br />
<br />
<comment date="2015-07-25T10:34:09Z" name="Michael"><br />
*wow* That's what I call a very fast answer! Thanks! :)<br />
<br />
Yeah, saw that plugin a few minutes after asking here. Got it working already. Thanks again, I appreciate your help.<br />
</comment><br />
== Niki meinte … ==<br />
<br />
<comment date="2017-01-08T22:47:10Z" name="Niki" signature="[[Benutzer:Niki|Niki]] ([[Benutzer Diskussion:Niki|Diskussion]])"><br />
Test<br />
</comment></div>Nikihttp://niki.hammler.net/w/index.php?title=Diskussion:GPG:_WinPT_%2B_KeePass_%3D_KeePT&diff=1641Diskussion:GPG: WinPT + KeePass = KeePT2015-08-01T09:18:21Z<p>Niki: Änderungen von 96.44.147.66 (Diskussion) wurden auf die letzte Version von 37.160.150.11 zurückgesetzt</p>
<hr />
<div><noinclude>Kommentare zur Seite „[[GPG: WinPT + KeePass = KeePT]]“<br />
<comments /><br />
----- __NOEDITSECTION__</noinclude><br />
== r04r meinte … ==<br />
<br />
<comment date="2012-01-10T23:31:42Z" name="r04r" url="http://minichan.org"><br />
Would it be possible to get this plugin for KeePass 2.x?<br />
</comment><br />
== Niki meinte … ==<br />
<br />
<comment date="2012-01-11T08:44:27Z" name="Niki"><br />
Hi r04r,<br />
<br />
Unfortunately the plugin is only available for KeePass 1 since I am only using KP1.<br />
<br />
The plugin interface for KP2 is fundamentally different (based in C#/managed code) and provides different APIs, so it is a hard task to port the plugin. Maybe I will switch to KP2 myself one time, then I will probably port the plugin. Also when there are many inquiries for KP2, I may consider porting it.<br />
<br />
Regards,<br />
Niki<br />
<br />
</comment><br />
== r04r meinte … ==<br />
<br />
<comment date="2012-01-11T10:45:19Z" name="r04r" url="http://minichan.org"><br />
Hello Niki,<br />
<br />
Thank you for the input and I was afraid that might be the case. This plugin and the SSH Agent one look really useful so that's too bad. May I ask why you're sticking with KP1? <br />
</comment><br />
== Niki meinte … ==<br />
<br />
<comment date="2012-01-11T13:29:24Z" name="Niki"><br />
Hi,<br />
<br />
In general, KP2 is more "bloat" because it is based on .NET, C# and is slower. The features in KP2 are great but I can life without them.<br />
<br />
My main reason is that for KP1 I have a port for my mobile phone (Windows Mobile) which is a main requirement for me.<br />
Ironically, KP1 seems to be more future-proof for me (personally) because there is a Linux port (KeePassX) and an Android port, should I buy a new phone.<br />
<br />
The final decision for me to use KP1 gave me the author himself where he assured multiple times that KP1 is not being discontinued and there are no plans to do so. KP1 is just a kind of "KP lite". KP2 was made because of all these new requested features which required a complete redesign. As the author told me, he even is using KP1 for himself!<br />
<br />
Last but not least, KP1 seems to be used in enterprise environments and it is also used in my company (a well known IC manufacturer with 40k employees worldwide).<br />
<br />
Regards,<br />
Niki<br />
<br />
<br />
<br />
</comment><br />
== pete meinte … ==<br />
<br />
<comment date="2012-12-10T14:49:13Z" name="pete"><br />
We use KP2 at work, due to its ability to handle multiple users accessing 1 database<br />
</comment><br />
== Josch meinte … ==<br />
<br />
<comment date="2015-07-21T14:45:26Z" name="Josch"><br />
Hi ro4r, <br />
any changes on the KP1-Policy with you :) <br />
<br />
Regards, Josch<br />
</comment><br />
== Niki meinte … ==<br />
<br />
<comment date="2015-07-21T20:17:59Z" name="Niki"><br />
Hi Josh,<br />
<br />
Indeed, there are changes (for me at least, don't know for ro4r ;-) ).<br />
<br />
I switched to KP2 some time ago and and even created some (actually simple) plugins already: http://niki.hammler.net/wiki/KeePass (more of them started but unfinished).<br />
<br />
I also wanted to port the KeePT plugin already (and started) but it seems to be non-trivial because I need to load a 32 bit DLL into a possibly 64 bit process (.NET). Also my time is rather limited.<br />
<br />
But if I see that other people would also use it this would motivate me to put more emphasis on it ;-)<br />
<br />
Niki<br />
<br />
</comment></div>Nikihttp://niki.hammler.net/w/index.php?title=KeePass&diff=1633KeePass2015-04-18T19:50:24Z<p>Niki: </p>
<hr />
<div>[http://keepass.info KeePass] is a password manager and one of my op "must-have" applications. Instead of either having the same password for all your stuff or having to remember many different passwords, you can use one single, secure password to store all others in a secure, encrypted way. Integrations such as autotype makes it easy to handle these passwords in Windows and KeePass is available for multiple platforms.<br />
<br />
= KeePass 1 =<br />
<br />
KeePass 1.x is a very light variant for KeePass. I have extended it using various plugins. Related articles:<br />
<br />
* [[LockExtensions for KeePass]]<br />
* [[More extensions for KeePass]]<br />
* [[GPG: WinPT + KeePass = KeePT]]<br />
* [[PuttyAgent now supports openssh/cygwin/msys]]<br />
<br />
= KeePass 2 =<br />
<br />
KeePass 2 can be regarded as the "full version" which contains many more features. Downside is that it is slower and uses more memory because it is written in C# .NET instead of pure C++/MFC (as KeePass 1).<br />
After many years, I switched to KeePass 2 in March 2015 due to the much richer feature set.<br />
Also the Android version of Keepass2Android is much better.<br />
<br />
I created the following plugins for KeePass 2:<br />
<br />
== TCATO Placeholder ==<br />
<br />
[http://keepass.info/help/v2/autotype_obfuscation.html Two-Channel Auto-Type Obfuscation (TCATO)] is a very powerful new feature of KeePass 2. Instead of just auto-typing the information, TCATO splits the information and transfers parts of it via the clipboard. This makes it much harder for keyloggers to capture the information. TCATO can be enabled/disabled on a '''per-entry''' basis.<br />
<br />
Unfortunately, TCATO does not work for all windows, for example PuTTY. Hence, often you want to enable/disable TCATO '''per auto-type sequence'''. Example: Some stupid online banking systems (e.g. BAWAK PSK has this stupid "feature") prevent usage of the clipboard in some input fields, for example when changing the password. In this case you can selectively disable TCATO for this sequence.<br />
<br />
Example:<br />
Auto-Type-Window: BAWAG P.S.K. eBanking - ebanking.bawagpsk.com*<br />
Auto-Type-Sequence: {C:Login}{DELAY 200}{USERNAME}{TAB}{PASSWORD}{ENTER}<br />
Auto-Type-Sequence: {C:change password}{TCATO:false}{PASSWORD}{TAB}{NEWPASSWORD:/PSK/}{TAB}{NEWPASSWORD:/PSK/}<br />
<br />
* [[Datei:TCATO_Placeholder_v1.2.zip|Download Plugin]]<br />
* [[Datei:TCATO_Placeholder_v1.2-src.zip|Download Source Code]]<br />
<br />
== TAN Placeholder ==<br />
<br />
This plugin provides a placeholder {USETAN:...} for use in auto typing. It can be used for logins where a TAN is required.<br />
<br />
=== Example application ===<br />
<br />
Cisco AnnyConnect Secure Client can be automated when one-way passwords as required.<br />
I create a printed list of password and safe them as TAN entires in a group called "VPN TANs". Then I have the following auto-type sequence:<br />
<br />
Auto-Type-Window: Cisco AnyConnect | su-vpn.stanford.edu<br />
Auto-Type-Sequence: {C:with TAN}{DELAY 1000}{PASSWORD}{ENTER}{DELAY 2000}{USETAN:T:VPN TANs}{ENTER}{DELAY 2000}{ENTER}<br />
<br />
=== How to use ===<br />
<br />
The placeholder has one of the following forms:<br />
<br />
{USETAN:I:group-uuid}<br />
{USETAN:T:group-name}<br />
<br />
Here, "I" references the group with the TANs using its UUID: group-uuid must be UUID of the group, as a hex string.<br />
"T" references the group with the group title. If there are multiple groups with the same name, the first one is taken!<br />
<br />
Use the I-version to uniquely reference a TAN group. There is no builtin way to obtain the UUID of a group. One way is to export the TAN group to "KeePass XML (2.x)" and look for the tag <UUID>.<br />
Important: The UUID from this tag is in BASE64. You need to convert it to a hex string manually, for example on http://tomeko.net/online_tools/base64.php?lang=en .<br />
<br />
Use the T-version if you update your TANs frequently in different groups. Take care that the group is unique!<br />
<br />
Optionally, if your TAN entries are numbered, a specific TAN number can be provided as last argument:<br />
<br />
{USETAN:I:group-uuid:tan nr}<br />
{USETAN:T:group-name:tan nr}<br />
<br />
=== Examples ===<br />
<br />
Enter Username, the next available TAN and then password. First, the group is identified by its title, second by its UUID.<br />
<br />
{USERNAME}{TAB}{USETAN:T:My TAN List}{PASSWORD}{ENTER}<br />
{USERNAME}{TAB}{USETAN:I:2A5FF84677A91D49B4227D564B7698AF}{PASSWORD}{ENTER}<br />
<br />
Additionally, request than the TAN with number 6 is entered:<br />
<br />
{USERNAME}{TAB}{USETAN:T:My TAN List:6}{PASSWORD}{ENTER}<br />
{USERNAME}{TAB}{USETAN:I:2A5FF84677A91D49B4227D564B7698AF:6}{PASSWORD}{ENTER}<br />
<br />
<br />
=== Error messages ===<br />
<br />
"The following auto-type placeholder or special key code is unknown/unsupported: {USETAN...}".<br />
<br />
Make sure the placeholder has exactly the forms described above with the first argument either T or I.<br />
If you use an UUID, make sure that it has the right form, i.e. it is 32 bytes<br />
long and consists only of A-F, 0-9. Example: 2A5FF84677A91D49B4227D564B7698AF<br />
<br />
<br />
"{USETAN}: Supplied group was not found"<br />
<br />
Make sure you use the correct UUID. When referencing using the title, make sure you use the right case (case matters).<br />
<br />
"{USETAN}: Either TAN entry was not found or no TAN available"<br />
If you supplied an ID for the TAN, the TAN entry was either not found or has been used. If you did not supply a specific ID, there are no more free TANs available in the group. If you receive this message but you have free TANs in the group, make sure the group name is unique when referencing it by its title!<br />
<br />
=== Download ===<br />
<br />
* [[Datei:TAN_Placeholder-v1.1.zip]]<br />
* [[Datei:TAN_Placeholder-v1.1-src.zip]]<br />
<br />
<br />
= Comments =<br />
<br />
<comments />{{:{{TALKSPACE}}:{{PAGENAME}}}}</div>Nikihttp://niki.hammler.net/w/index.php?title=KeePass&diff=1632KeePass2015-04-18T19:49:22Z<p>Niki: /* TCATO Placeholder */</p>
<hr />
<div>[http://keepass.info KeePass] is a password manager and one of my op "must-have" applications. Instead of either having the same password for all your stuff or having to remember many different passwords, you can use one single, secure password to store all others in a secure, encrypted way. Integrations such as autotype makes it easy to handle these passwords in Windows and KeePass is available for multiple platforms.<br />
<br />
= KeePass 1 =<br />
<br />
KeePass 1.x is a very light variant for KeePass. I have extended it using various plugins. Related articles:<br />
<br />
* [[LockExtensions for KeePass]]<br />
* [[More extensions for KeePass]]<br />
* [[GPG: WinPT + KeePass = KeePT]]<br />
* [[PuttyAgent now supports openssh/cygwin/msys]]<br />
<br />
= KeePass 2 =<br />
<br />
KeePass 2 can be regarded as the "full version" which contains many more features. Downside is that it is slower and uses more memory because it is written in C# .NET instead of pure C++/MFC (as KeePass 1).<br />
After many years, I switched to KeePass 2 in March 2015 due to the much richer feature set.<br />
Also the Android version of Keepass2Android is much better.<br />
<br />
I created the following plugins for KeePass 2:<br />
<br />
== TCATO Placeholder ==<br />
<br />
[http://keepass.info/help/v2/autotype_obfuscation.html Two-Channel Auto-Type Obfuscation (TCATO)] is a very powerful new feature of KeePass 2. Instead of just auto-typing the information, TCATO splits the information and transfers parts of it via the clipboard. This makes it much harder for keyloggers to capture the information. TCATO can be enabled/disabled on a '''per-entry''' basis.<br />
<br />
Unfortunately, TCATO does not work for all windows, for example PuTTY. Hence, often you want to enable/disable TCATO '''per auto-type sequence'''. Example: Some stupid online banking systems (e.g. BAWAK PSK has this stupid "feature") prevent usage of the clipboard in some input fields, for example when changing the password. In this case you can selectively disable TCATO for this sequence.<br />
<br />
Example:<br />
Auto-Type-Window: BAWAG P.S.K. eBanking - ebanking.bawagpsk.com*<br />
Auto-Type-Sequence: {C:Login}{DELAY 200}{USERNAME}{TAB}{PASSWORD}{ENTER}<br />
Auto-Type-Sequence: {C:change password}{TCATO:false}{PASSWORD}{TAB}{NEWPASSWORD:/PSK/}{TAB}{NEWPASSWORD:/PSK/}<br />
<br />
* [[Datei:TCATO_Placeholder_v1.2.zip|Download Plugin]]<br />
* [[Datei:TCATO_Placeholder_v1.2-src.zip|Download Source Code]]<br />
<br />
== TAN Placeholder ==<br />
<br />
This plugin provides a placeholder {USETAN:...} for use in auto typing. It can be used for logins where a TAN is required.<br />
<br />
=== Example application ===<br />
<br />
Cisco AnnyConnect Secure Client can be automated when one-way passwords as required.<br />
I create a printed list of password and safe them as TAN entires in a group called "VPN TANs". Then I have the following auto-type sequence:<br />
<br />
Auto-Type-Window: Cisco AnyConnect | su-vpn.stanford.edu<br />
Auto-Type-Sequence: {C:with TAN}{DELAY 1000}{PASSWORD}{ENTER}{DELAY 2000}{USETAN:T:VPN TANs}{ENTER}{DELAY 2000}{ENTER}<br />
<br />
=== How to use ===<br />
<br />
The placeholder has one of the following forms:<br />
<br />
{USETAN:I:group-uuid}<br />
{USETAN:T:group-name}<br />
<br />
Here, "I" references the group with the TANs using its UUID: group-uuid must be UUID of the group, as a hex string.<br />
"T" references the group with the group title. If there are multiple groups with the same name, the first one is taken!<br />
<br />
Use the I-version to uniquely reference a TAN group. There is no builtin way to obtain the UUID of a group. One way is to export the TAN group to "KeePass XML (2.x)" and look for the tag <UUID>.<br />
Important: The UUID from this tag is in BASE64. You need to convert it to a hex string manually, for example on http://tomeko.net/online_tools/base64.php?lang=en .<br />
<br />
Use the T-version if you update your TANs frequently in different groups. Take care that the group is unique!<br />
<br />
Optionally, if your TAN entries are numbered, a specific TAN number can be provided as last argument:<br />
<br />
{USETAN:I:group-uuid:tan nr}<br />
{USETAN:T:group-name:tan nr}<br />
<br />
=== Examples ===<br />
<br />
Enter Username, the next available TAN and then password. First, the group is identified by its title, second by its UUID.<br />
<br />
{USERNAME}{TAB}{USETAN:T:My TAN List}{PASSWORD}{ENTER}<br />
{USERNAME}{TAB}{USETAN:I:2A5FF84677A91D49B4227D564B7698AF}{PASSWORD}{ENTER}<br />
<br />
Additionally, request than the TAN with number 6 is entered:<br />
<br />
{USERNAME}{TAB}{USETAN:T:My TAN List:6}{PASSWORD}{ENTER}<br />
{USERNAME}{TAB}{USETAN:I:2A5FF84677A91D49B4227D564B7698AF:6}{PASSWORD}{ENTER}<br />
<br />
<br />
=== Error messages ===<br />
<br />
"The following auto-type placeholder or special key code is unknown/unsupported: {USETAN...}".<br />
<br />
Make sure the placeholder has exactly the forms described above with the first argument either T or I.<br />
If you use an UUID, make sure that it has the right form, i.e. it is 32 bytes<br />
long and consists only of A-F, 0-9. Example: 2A5FF84677A91D49B4227D564B7698AF<br />
<br />
<br />
"{USETAN}: Supplied group was not found"<br />
<br />
Make sure you use the correct UUID. When referencing using the title, make sure you use the right case (case matters).<br />
<br />
"{USETAN}: Either TAN entry was not found or no TAN available"<br />
If you supplied an ID for the TAN, the TAN entry was either not found or has been used. If you did not supply a specific ID, there are no more free TANs available in the group. If you receive this message but you have free TANs in the group, make sure the group name is unique when referencing it by its title!<br />
<br />
=== Download ===<br />
<br />
* [[Datei:TAN_Placeholder-v1.1.zip]]<br />
* [[Datei:TAN_Placeholder-v1.1-src.zip]]</div>Nikihttp://niki.hammler.net/w/index.php?title=Datei:TAN_Placeholder-v1.1-src.zip&diff=1631Datei:TAN Placeholder-v1.1-src.zip2015-04-18T19:47:18Z<p>Niki: </p>
<hr />
<div></div>Nikihttp://niki.hammler.net/w/index.php?title=Datei:TAN_Placeholder-v1.1.zip&diff=1630Datei:TAN Placeholder-v1.1.zip2015-04-18T19:47:03Z<p>Niki: </p>
<hr />
<div></div>Nikihttp://niki.hammler.net/w/index.php?title=KeePass&diff=1629KeePass2015-04-18T19:46:48Z<p>Niki: /* Download */</p>
<hr />
<div>[http://keepass.info KeePass] is a password manager and one of my op "must-have" applications. Instead of either having the same password for all your stuff or having to remember many different passwords, you can use one single, secure password to store all others in a secure, encrypted way. Integrations such as autotype makes it easy to handle these passwords in Windows and KeePass is available for multiple platforms.<br />
<br />
= KeePass 1 =<br />
<br />
KeePass 1.x is a very light variant for KeePass. I have extended it using various plugins. Related articles:<br />
<br />
* [[LockExtensions for KeePass]]<br />
* [[More extensions for KeePass]]<br />
* [[GPG: WinPT + KeePass = KeePT]]<br />
* [[PuttyAgent now supports openssh/cygwin/msys]]<br />
<br />
= KeePass 2 =<br />
<br />
KeePass 2 can be regarded as the "full version" which contains many more features. Downside is that it is slower and uses more memory because it is written in C# .NET instead of pure C++/MFC (as KeePass 1).<br />
After many years, I switched to KeePass 2 in March 2015 due to the much richer feature set.<br />
Also the Android version of Keepass2Android is much better.<br />
<br />
I created the following plugins for KeePass 2:<br />
<br />
== TCATO Placeholder ==<br />
<br />
[http://keepass.info/help/v2/autotype_obfuscation.html Two-Channel Auto-Type Obfuscation (TCATO)] is a very powerful new feature of KeePass 2. Instead of just auto-typing the information, TCATO splits the information and transfers parts of it via the clipboard. This makes it much harder for keyloggers to capture the information. TCATO can be enabled/disabled on a '''per-entry''' basis.<br />
<br />
Unfortunately, TCATO does not work for all windows, for example PuTTY. Hence, often you want to enable/disable TCATO per auto-type sequence. Example: Some stupid online banking systems (e.g. BAWAK PSK has this stupid "feature") prevent usage of the clipboard in some input fields, for example when changing the password. In this case you can selectively disable TCATO for this sequence.<br />
<br />
Example:<br />
Auto-Type-Window: BAWAG P.S.K. eBanking - ebanking.bawagpsk.com*<br />
Auto-Type-Sequence: {C:Login}{DELAY 200}{USERNAME}{TAB}{PASSWORD}{ENTER}<br />
Auto-Type-Sequence: {C:change password}{TCATO:false}{PASSWORD}{TAB}{NEWPASSWORD:/PSK/}{TAB}{NEWPASSWORD:/PSK/}<br />
<br />
* [[Datei:TCATO_Placeholder_v1.2.zip|Download Plugin]]<br />
* [[Datei:TCATO_Placeholder_v1.2-src.zip|Download Source Code]]<br />
<br />
== TAN Placeholder ==<br />
<br />
This plugin provides a placeholder {USETAN:...} for use in auto typing. It can be used for logins where a TAN is required.<br />
<br />
=== Example application ===<br />
<br />
Cisco AnnyConnect Secure Client can be automated when one-way passwords as required.<br />
I create a printed list of password and safe them as TAN entires in a group called "VPN TANs". Then I have the following auto-type sequence:<br />
<br />
Auto-Type-Window: Cisco AnyConnect | su-vpn.stanford.edu<br />
Auto-Type-Sequence: {C:with TAN}{DELAY 1000}{PASSWORD}{ENTER}{DELAY 2000}{USETAN:T:VPN TANs}{ENTER}{DELAY 2000}{ENTER}<br />
<br />
=== How to use ===<br />
<br />
The placeholder has one of the following forms:<br />
<br />
{USETAN:I:group-uuid}<br />
{USETAN:T:group-name}<br />
<br />
Here, "I" references the group with the TANs using its UUID: group-uuid must be UUID of the group, as a hex string.<br />
"T" references the group with the group title. If there are multiple groups with the same name, the first one is taken!<br />
<br />
Use the I-version to uniquely reference a TAN group. There is no builtin way to obtain the UUID of a group. One way is to export the TAN group to "KeePass XML (2.x)" and look for the tag <UUID>.<br />
Important: The UUID from this tag is in BASE64. You need to convert it to a hex string manually, for example on http://tomeko.net/online_tools/base64.php?lang=en .<br />
<br />
Use the T-version if you update your TANs frequently in different groups. Take care that the group is unique!<br />
<br />
Optionally, if your TAN entries are numbered, a specific TAN number can be provided as last argument:<br />
<br />
{USETAN:I:group-uuid:tan nr}<br />
{USETAN:T:group-name:tan nr}<br />
<br />
=== Examples ===<br />
<br />
Enter Username, the next available TAN and then password. First, the group is identified by its title, second by its UUID.<br />
<br />
{USERNAME}{TAB}{USETAN:T:My TAN List}{PASSWORD}{ENTER}<br />
{USERNAME}{TAB}{USETAN:I:2A5FF84677A91D49B4227D564B7698AF}{PASSWORD}{ENTER}<br />
<br />
Additionally, request than the TAN with number 6 is entered:<br />
<br />
{USERNAME}{TAB}{USETAN:T:My TAN List:6}{PASSWORD}{ENTER}<br />
{USERNAME}{TAB}{USETAN:I:2A5FF84677A91D49B4227D564B7698AF:6}{PASSWORD}{ENTER}<br />
<br />
<br />
=== Error messages ===<br />
<br />
"The following auto-type placeholder or special key code is unknown/unsupported: {USETAN...}".<br />
<br />
Make sure the placeholder has exactly the forms described above with the first argument either T or I.<br />
If you use an UUID, make sure that it has the right form, i.e. it is 32 bytes<br />
long and consists only of A-F, 0-9. Example: 2A5FF84677A91D49B4227D564B7698AF<br />
<br />
<br />
"{USETAN}: Supplied group was not found"<br />
<br />
Make sure you use the correct UUID. When referencing using the title, make sure you use the right case (case matters).<br />
<br />
"{USETAN}: Either TAN entry was not found or no TAN available"<br />
If you supplied an ID for the TAN, the TAN entry was either not found or has been used. If you did not supply a specific ID, there are no more free TANs available in the group. If you receive this message but you have free TANs in the group, make sure the group name is unique when referencing it by its title!<br />
<br />
=== Download ===<br />
<br />
* [[Datei:TAN_Placeholder-v1.1.zip]]<br />
* [[Datei:TAN_Placeholder-v1.1-src.zip]]</div>Nikihttp://niki.hammler.net/w/index.php?title=KeePass&diff=1628KeePass2015-04-18T19:46:34Z<p>Niki: /* Download */</p>
<hr />
<div>[http://keepass.info KeePass] is a password manager and one of my op "must-have" applications. Instead of either having the same password for all your stuff or having to remember many different passwords, you can use one single, secure password to store all others in a secure, encrypted way. Integrations such as autotype makes it easy to handle these passwords in Windows and KeePass is available for multiple platforms.<br />
<br />
= KeePass 1 =<br />
<br />
KeePass 1.x is a very light variant for KeePass. I have extended it using various plugins. Related articles:<br />
<br />
* [[LockExtensions for KeePass]]<br />
* [[More extensions for KeePass]]<br />
* [[GPG: WinPT + KeePass = KeePT]]<br />
* [[PuttyAgent now supports openssh/cygwin/msys]]<br />
<br />
= KeePass 2 =<br />
<br />
KeePass 2 can be regarded as the "full version" which contains many more features. Downside is that it is slower and uses more memory because it is written in C# .NET instead of pure C++/MFC (as KeePass 1).<br />
After many years, I switched to KeePass 2 in March 2015 due to the much richer feature set.<br />
Also the Android version of Keepass2Android is much better.<br />
<br />
I created the following plugins for KeePass 2:<br />
<br />
== TCATO Placeholder ==<br />
<br />
[http://keepass.info/help/v2/autotype_obfuscation.html Two-Channel Auto-Type Obfuscation (TCATO)] is a very powerful new feature of KeePass 2. Instead of just auto-typing the information, TCATO splits the information and transfers parts of it via the clipboard. This makes it much harder for keyloggers to capture the information. TCATO can be enabled/disabled on a '''per-entry''' basis.<br />
<br />
Unfortunately, TCATO does not work for all windows, for example PuTTY. Hence, often you want to enable/disable TCATO per auto-type sequence. Example: Some stupid online banking systems (e.g. BAWAK PSK has this stupid "feature") prevent usage of the clipboard in some input fields, for example when changing the password. In this case you can selectively disable TCATO for this sequence.<br />
<br />
Example:<br />
Auto-Type-Window: BAWAG P.S.K. eBanking - ebanking.bawagpsk.com*<br />
Auto-Type-Sequence: {C:Login}{DELAY 200}{USERNAME}{TAB}{PASSWORD}{ENTER}<br />
Auto-Type-Sequence: {C:change password}{TCATO:false}{PASSWORD}{TAB}{NEWPASSWORD:/PSK/}{TAB}{NEWPASSWORD:/PSK/}<br />
<br />
* [[Datei:TCATO_Placeholder_v1.2.zip|Download Plugin]]<br />
* [[Datei:TCATO_Placeholder_v1.2-src.zip|Download Source Code]]<br />
<br />
== TAN Placeholder ==<br />
<br />
This plugin provides a placeholder {USETAN:...} for use in auto typing. It can be used for logins where a TAN is required.<br />
<br />
=== Example application ===<br />
<br />
Cisco AnnyConnect Secure Client can be automated when one-way passwords as required.<br />
I create a printed list of password and safe them as TAN entires in a group called "VPN TANs". Then I have the following auto-type sequence:<br />
<br />
Auto-Type-Window: Cisco AnyConnect | su-vpn.stanford.edu<br />
Auto-Type-Sequence: {C:with TAN}{DELAY 1000}{PASSWORD}{ENTER}{DELAY 2000}{USETAN:T:VPN TANs}{ENTER}{DELAY 2000}{ENTER}<br />
<br />
=== How to use ===<br />
<br />
The placeholder has one of the following forms:<br />
<br />
{USETAN:I:group-uuid}<br />
{USETAN:T:group-name}<br />
<br />
Here, "I" references the group with the TANs using its UUID: group-uuid must be UUID of the group, as a hex string.<br />
"T" references the group with the group title. If there are multiple groups with the same name, the first one is taken!<br />
<br />
Use the I-version to uniquely reference a TAN group. There is no builtin way to obtain the UUID of a group. One way is to export the TAN group to "KeePass XML (2.x)" and look for the tag <UUID>.<br />
Important: The UUID from this tag is in BASE64. You need to convert it to a hex string manually, for example on http://tomeko.net/online_tools/base64.php?lang=en .<br />
<br />
Use the T-version if you update your TANs frequently in different groups. Take care that the group is unique!<br />
<br />
Optionally, if your TAN entries are numbered, a specific TAN number can be provided as last argument:<br />
<br />
{USETAN:I:group-uuid:tan nr}<br />
{USETAN:T:group-name:tan nr}<br />
<br />
=== Examples ===<br />
<br />
Enter Username, the next available TAN and then password. First, the group is identified by its title, second by its UUID.<br />
<br />
{USERNAME}{TAB}{USETAN:T:My TAN List}{PASSWORD}{ENTER}<br />
{USERNAME}{TAB}{USETAN:I:2A5FF84677A91D49B4227D564B7698AF}{PASSWORD}{ENTER}<br />
<br />
Additionally, request than the TAN with number 6 is entered:<br />
<br />
{USERNAME}{TAB}{USETAN:T:My TAN List:6}{PASSWORD}{ENTER}<br />
{USERNAME}{TAB}{USETAN:I:2A5FF84677A91D49B4227D564B7698AF:6}{PASSWORD}{ENTER}<br />
<br />
<br />
=== Error messages ===<br />
<br />
"The following auto-type placeholder or special key code is unknown/unsupported: {USETAN...}".<br />
<br />
Make sure the placeholder has exactly the forms described above with the first argument either T or I.<br />
If you use an UUID, make sure that it has the right form, i.e. it is 32 bytes<br />
long and consists only of A-F, 0-9. Example: 2A5FF84677A91D49B4227D564B7698AF<br />
<br />
<br />
"{USETAN}: Supplied group was not found"<br />
<br />
Make sure you use the correct UUID. When referencing using the title, make sure you use the right case (case matters).<br />
<br />
"{USETAN}: Either TAN entry was not found or no TAN available"<br />
If you supplied an ID for the TAN, the TAN entry was either not found or has been used. If you did not supply a specific ID, there are no more free TANs available in the group. If you receive this message but you have free TANs in the group, make sure the group name is unique when referencing it by its title!<br />
<br />
=== Download ===<br />
<br />
[[Datei:TAN_Placeholder-v1.1.zip]]<br />
[[Datei:TAN_Placeholder-v1.1-src.zip]]</div>Nikihttp://niki.hammler.net/w/index.php?title=KeePass&diff=1627KeePass2015-04-18T19:41:24Z<p>Niki: /* TAN Placeholder */</p>
<hr />
<div>[http://keepass.info KeePass] is a password manager and one of my op "must-have" applications. Instead of either having the same password for all your stuff or having to remember many different passwords, you can use one single, secure password to store all others in a secure, encrypted way. Integrations such as autotype makes it easy to handle these passwords in Windows and KeePass is available for multiple platforms.<br />
<br />
= KeePass 1 =<br />
<br />
KeePass 1.x is a very light variant for KeePass. I have extended it using various plugins. Related articles:<br />
<br />
* [[LockExtensions for KeePass]]<br />
* [[More extensions for KeePass]]<br />
* [[GPG: WinPT + KeePass = KeePT]]<br />
* [[PuttyAgent now supports openssh/cygwin/msys]]<br />
<br />
= KeePass 2 =<br />
<br />
KeePass 2 can be regarded as the "full version" which contains many more features. Downside is that it is slower and uses more memory because it is written in C# .NET instead of pure C++/MFC (as KeePass 1).<br />
After many years, I switched to KeePass 2 in March 2015 due to the much richer feature set.<br />
Also the Android version of Keepass2Android is much better.<br />
<br />
I created the following plugins for KeePass 2:<br />
<br />
== TCATO Placeholder ==<br />
<br />
[http://keepass.info/help/v2/autotype_obfuscation.html Two-Channel Auto-Type Obfuscation (TCATO)] is a very powerful new feature of KeePass 2. Instead of just auto-typing the information, TCATO splits the information and transfers parts of it via the clipboard. This makes it much harder for keyloggers to capture the information. TCATO can be enabled/disabled on a '''per-entry''' basis.<br />
<br />
Unfortunately, TCATO does not work for all windows, for example PuTTY. Hence, often you want to enable/disable TCATO per auto-type sequence. Example: Some stupid online banking systems (e.g. BAWAK PSK has this stupid "feature") prevent usage of the clipboard in some input fields, for example when changing the password. In this case you can selectively disable TCATO for this sequence.<br />
<br />
Example:<br />
Auto-Type-Window: BAWAG P.S.K. eBanking - ebanking.bawagpsk.com*<br />
Auto-Type-Sequence: {C:Login}{DELAY 200}{USERNAME}{TAB}{PASSWORD}{ENTER}<br />
Auto-Type-Sequence: {C:change password}{TCATO:false}{PASSWORD}{TAB}{NEWPASSWORD:/PSK/}{TAB}{NEWPASSWORD:/PSK/}<br />
<br />
* [[Datei:TCATO_Placeholder_v1.2.zip|Download Plugin]]<br />
* [[Datei:TCATO_Placeholder_v1.2-src.zip|Download Source Code]]<br />
<br />
== TAN Placeholder ==<br />
<br />
This plugin provides a placeholder {USETAN:...} for use in auto typing. It can be used for logins where a TAN is required.<br />
<br />
=== Example application ===<br />
<br />
Cisco AnnyConnect Secure Client can be automated when one-way passwords as required.<br />
I create a printed list of password and safe them as TAN entires in a group called "VPN TANs". Then I have the following auto-type sequence:<br />
<br />
Auto-Type-Window: Cisco AnyConnect | su-vpn.stanford.edu<br />
Auto-Type-Sequence: {C:with TAN}{DELAY 1000}{PASSWORD}{ENTER}{DELAY 2000}{USETAN:T:VPN TANs}{ENTER}{DELAY 2000}{ENTER}<br />
<br />
=== How to use ===<br />
<br />
The placeholder has one of the following forms:<br />
<br />
{USETAN:I:group-uuid}<br />
{USETAN:T:group-name}<br />
<br />
Here, "I" references the group with the TANs using its UUID: group-uuid must be UUID of the group, as a hex string.<br />
"T" references the group with the group title. If there are multiple groups with the same name, the first one is taken!<br />
<br />
Use the I-version to uniquely reference a TAN group. There is no builtin way to obtain the UUID of a group. One way is to export the TAN group to "KeePass XML (2.x)" and look for the tag <UUID>.<br />
Important: The UUID from this tag is in BASE64. You need to convert it to a hex string manually, for example on http://tomeko.net/online_tools/base64.php?lang=en .<br />
<br />
Use the T-version if you update your TANs frequently in different groups. Take care that the group is unique!<br />
<br />
Optionally, if your TAN entries are numbered, a specific TAN number can be provided as last argument:<br />
<br />
{USETAN:I:group-uuid:tan nr}<br />
{USETAN:T:group-name:tan nr}<br />
<br />
=== Examples ===<br />
<br />
Enter Username, the next available TAN and then password. First, the group is identified by its title, second by its UUID.<br />
<br />
{USERNAME}{TAB}{USETAN:T:My TAN List}{PASSWORD}{ENTER}<br />
{USERNAME}{TAB}{USETAN:I:2A5FF84677A91D49B4227D564B7698AF}{PASSWORD}{ENTER}<br />
<br />
Additionally, request than the TAN with number 6 is entered:<br />
<br />
{USERNAME}{TAB}{USETAN:T:My TAN List:6}{PASSWORD}{ENTER}<br />
{USERNAME}{TAB}{USETAN:I:2A5FF84677A91D49B4227D564B7698AF:6}{PASSWORD}{ENTER}<br />
<br />
<br />
=== Error messages ===<br />
<br />
"The following auto-type placeholder or special key code is unknown/unsupported: {USETAN...}".<br />
<br />
Make sure the placeholder has exactly the forms described above with the first argument either T or I.<br />
If you use an UUID, make sure that it has the right form, i.e. it is 32 bytes<br />
long and consists only of A-F, 0-9. Example: 2A5FF84677A91D49B4227D564B7698AF<br />
<br />
<br />
"{USETAN}: Supplied group was not found"<br />
<br />
Make sure you use the correct UUID. When referencing using the title, make sure you use the right case (case matters).<br />
<br />
"{USETAN}: Either TAN entry was not found or no TAN available"<br />
If you supplied an ID for the TAN, the TAN entry was either not found or has been used. If you did not supply a specific ID, there are no more free TANs available in the group. If you receive this message but you have free TANs in the group, make sure the group name is unique when referencing it by its title!<br />
<br />
=== Download ===</div>Nikihttp://niki.hammler.net/w/index.php?title=Datei:TCATO_Placeholder_v1.2-src.zip&diff=1626Datei:TCATO Placeholder v1.2-src.zip2015-04-18T19:33:43Z<p>Niki: </p>
<hr />
<div></div>Nikihttp://niki.hammler.net/w/index.php?title=Datei:TCATO_Placeholder_v1.2.zip&diff=1625Datei:TCATO Placeholder v1.2.zip2015-04-18T19:33:29Z<p>Niki: </p>
<hr />
<div></div>Nikihttp://niki.hammler.net/w/index.php?title=KeePass&diff=1624KeePass2015-04-18T19:33:14Z<p>Niki: </p>
<hr />
<div>[http://keepass.info KeePass] is a password manager and one of my op "must-have" applications. Instead of either having the same password for all your stuff or having to remember many different passwords, you can use one single, secure password to store all others in a secure, encrypted way. Integrations such as autotype makes it easy to handle these passwords in Windows and KeePass is available for multiple platforms.<br />
<br />
= KeePass 1 =<br />
<br />
KeePass 1.x is a very light variant for KeePass. I have extended it using various plugins. Related articles:<br />
<br />
* [[LockExtensions for KeePass]]<br />
* [[More extensions for KeePass]]<br />
* [[GPG: WinPT + KeePass = KeePT]]<br />
* [[PuttyAgent now supports openssh/cygwin/msys]]<br />
<br />
= KeePass 2 =<br />
<br />
KeePass 2 can be regarded as the "full version" which contains many more features. Downside is that it is slower and uses more memory because it is written in C# .NET instead of pure C++/MFC (as KeePass 1).<br />
After many years, I switched to KeePass 2 in March 2015 due to the much richer feature set.<br />
Also the Android version of Keepass2Android is much better.<br />
<br />
I created the following plugins for KeePass 2:<br />
<br />
== TCATO Placeholder ==<br />
<br />
[http://keepass.info/help/v2/autotype_obfuscation.html Two-Channel Auto-Type Obfuscation (TCATO)] is a very powerful new feature of KeePass 2. Instead of just auto-typing the information, TCATO splits the information and transfers parts of it via the clipboard. This makes it much harder for keyloggers to capture the information. TCATO can be enabled/disabled on a '''per-entry''' basis.<br />
<br />
Unfortunately, TCATO does not work for all windows, for example PuTTY. Hence, often you want to enable/disable TCATO per auto-type sequence. Example: Some stupid online banking systems (e.g. BAWAK PSK has this stupid "feature") prevent usage of the clipboard in some input fields, for example when changing the password. In this case you can selectively disable TCATO for this sequence.<br />
<br />
Example:<br />
Auto-Type-Window: BAWAG P.S.K. eBanking - ebanking.bawagpsk.com*<br />
Auto-Type-Sequence: {C:Login}{DELAY 200}{USERNAME}{TAB}{PASSWORD}{ENTER}<br />
Auto-Type-Sequence: {C:change password}{TCATO:false}{PASSWORD}{TAB}{NEWPASSWORD:/PSK/}{TAB}{NEWPASSWORD:/PSK/}<br />
<br />
* [[Datei:TCATO_Placeholder_v1.2.zip|Download Plugin]]<br />
* [[Datei:TCATO_Placeholder_v1.2-src.zip|Download Source Code]]<br />
<br />
== TAN Placeholder ==</div>Nikihttp://niki.hammler.net/w/index.php?title=Datei:TCATO_Placeholder_v1.1-src.zip&diff=1623Datei:TCATO Placeholder v1.1-src.zip2015-04-18T19:19:56Z<p>Niki: lud eine neue Version von „Datei:TCATO Placeholder v1.1-src.zip“ hoch</p>
<hr />
<div></div>Nikihttp://niki.hammler.net/w/index.php?title=Datei:TCATO_Placeholder_v1.1-src.zip&diff=1622Datei:TCATO Placeholder v1.1-src.zip2015-04-18T19:13:03Z<p>Niki: lud eine neue Version von „Datei:TCATO Placeholder v1.1-src.zip“ hoch</p>
<hr />
<div></div>Nikihttp://niki.hammler.net/w/index.php?title=Datei:TCATO_Placeholder_v1.1-src.zip&diff=1621Datei:TCATO Placeholder v1.1-src.zip2015-04-18T19:12:40Z<p>Niki: </p>
<hr />
<div></div>Nikihttp://niki.hammler.net/w/index.php?title=Datei:TCATO_Placeholder_v1.1.zip&diff=1620Datei:TCATO Placeholder v1.1.zip2015-04-18T19:12:24Z<p>Niki: </p>
<hr />
<div></div>Nikihttp://niki.hammler.net/w/index.php?title=KeePass&diff=1619KeePass2015-04-18T19:11:01Z<p>Niki: /* TCATO Placeholder */</p>
<hr />
<div>[http://keepass.info KeePass] is a password manager and one of my op "must-have" applications. Instead of either having the same password for all your stuff or having to remember many different passwords, you can use one single, secure password to store all others in a secure, encrypted way. Integrations such as autotype makes it easy to handle these passwords in Windows and KeePass is available for multiple platforms.<br />
<br />
= KeePass 1 =<br />
<br />
KeePass 1.x is a very light variant for KeePass. I have extended it using various plugins. Related articles:<br />
<br />
* [[LockExtensions for KeePass]]<br />
* [[More extensions for KeePass]]<br />
* [[GPG: WinPT + KeePass = KeePT]]<br />
* [[PuttyAgent now supports openssh/cygwin/msys]]<br />
<br />
= KeePass 2 =<br />
<br />
KeePass 2 can be regarded as the "full version" which contains many more features. Downside is that it is slower and uses more memory because it is written in C# .NET instead of pure C++/MFC (as KeePass 1).<br />
After many years, I switched to KeePass 2 in March 2015 due to the much richer feature set.<br />
Also the Android version of Keepass2Android is much better.<br />
<br />
I created the following plugins for KeePass 2:<br />
<br />
== TCATO Placeholder ==<br />
<br />
[http://keepass.info/help/v2/autotype_obfuscation.html Two-Channel Auto-Type Obfuscation (TCATO)] is a very powerful new feature of KeePass 2. Instead of just auto-typing the information, TCATO splits the information and transfers parts of it via the clipboard. This makes it much harder for keyloggers to capture the information. TCATO can be enabled/disabled on a '''per-entry''' basis.<br />
<br />
Unfortunately, TCATO does not work for all windows, for example PuTTY. Hence, often you want to enable/disable TCATO per auto-type sequence. Example: Some stupid online banking systems (e.g. BAWAK PSK has this stupid "feature") prevent usage of the clipboard in some input fields, for example when changing the password. In this case you can selectively disable TCATO for this sequence.<br />
<br />
Example:<br />
Auto-Type-Window: BAWAG P.S.K. eBanking - ebanking.bawagpsk.com*<br />
Auto-Type-Sequence: {C:Login}{DELAY 200}{USERNAME}{TAB}{PASSWORD}{ENTER}<br />
Auto-Type-Sequence: {C:change password}{TCATO:false}{PASSWORD}{TAB}{NEWPASSWORD:/PSK/}{TAB}{NEWPASSWORD:/PSK/}<br />
<br />
* [[Datei:TCATO_Placeholder_v1.1.zip|Download Plugin]]<br />
* [[Datei:TCATO_Placeholder_v1.1-src.zip|Download Source Code]]<br />
<br />
== TAN Placeholder ==</div>Nikihttp://niki.hammler.net/w/index.php?title=KeePass&diff=1618KeePass2015-04-18T19:09:57Z<p>Niki: </p>
<hr />
<div>[http://keepass.info KeePass] is a password manager and one of my op "must-have" applications. Instead of either having the same password for all your stuff or having to remember many different passwords, you can use one single, secure password to store all others in a secure, encrypted way. Integrations such as autotype makes it easy to handle these passwords in Windows and KeePass is available for multiple platforms.<br />
<br />
= KeePass 1 =<br />
<br />
KeePass 1.x is a very light variant for KeePass. I have extended it using various plugins. Related articles:<br />
<br />
* [[LockExtensions for KeePass]]<br />
* [[More extensions for KeePass]]<br />
* [[GPG: WinPT + KeePass = KeePT]]<br />
* [[PuttyAgent now supports openssh/cygwin/msys]]<br />
<br />
= KeePass 2 =<br />
<br />
KeePass 2 can be regarded as the "full version" which contains many more features. Downside is that it is slower and uses more memory because it is written in C# .NET instead of pure C++/MFC (as KeePass 1).<br />
After many years, I switched to KeePass 2 in March 2015 due to the much richer feature set.<br />
Also the Android version of Keepass2Android is much better.<br />
<br />
I created the following plugins for KeePass 2:<br />
<br />
== TCATO Placeholder ==<br />
<br />
[http://keepass.info/help/v2/autotype_obfuscation.html Two-Channel Auto-Type Obfuscation (TCATO)] is a very powerful new feature of KeePass 2. Instead of just auto-typing the information, TCATO splits the information and transfers parts of it via the clipboard. This makes it much harder for keyloggers to capture the information. TCATO can be enabled/disabled on a '''per-entry''' basis.<br />
<br />
Unfortunately, TCATO does not work for all windows, for example PuTTY. Hence, often you want to enable/disable TCATO per auto-type sequence. Example: Some stupid online banking systems (e.g. BAWAK PSK has this stupid "feature") prevent usage of the clipboard in some input fields, for example when changing the password. In this case you can selectively disable TCATO for this sequence.<br />
<br />
Example:<br />
Auto-Type-Window: BAWAG P.S.K. eBanking - ebanking.bawagpsk.com*<br />
Auto-Type-Sequence: {C:Login}{DELAY 200}{USERNAME}{TAB}{PASSWORD}{ENTER}<br />
Auto-Type-Sequence: {C:change password}{TCATO:false}{PASSWORD}{TAB}{NEWPASSWORD:/PSK/}{TAB}{NEWPASSWORD:/PSK/}<br />
<br />
* [[Datei:Download Plugin]]<br />
* [[Datei:Download Source Code]]<br />
<br />
<br />
== TAN Placeholder ==</div>Nikihttp://niki.hammler.net/w/index.php?title=KeePass&diff=1617KeePass2015-04-18T19:09:25Z<p>Niki: Die Seite wurde neu angelegt: „[http://keepass.info KeePass] is a password manager and one of my op "must-have" applications. Instead of either having the same password for all your stuff or ha…“</p>
<hr />
<div>[http://keepass.info KeePass] is a password manager and one of my op "must-have" applications. Instead of either having the same password for all your stuff or having to remember many different passwords, you can use one single, secure password to store all others in a secure, encrypted way. Integrations such as autotype makes it easy to handle these passwords in Windows and KeePass is available for multiple platforms.<br />
<br />
= KeePass 1 =<br />
<br />
KeePass 1.x is a very light variant for KeePass. I have extended it using various plugins. Related articles:<br />
<br />
* [[LockExtensions for KeePass]]<br />
* [[More extensions for KeePass]]<br />
* [[GPG: WinPT + KeePass = KeePT]]<br />
* [[PuttyAgent now supports openssh/cygwin/msys]]<br />
<br />
= KeePass 2 =<br />
<br />
KeePass 2 can be regarded as the "full version" which contains many more features. Downside is that it is slower and uses more memory because it is written in C# .NET instead of pure C++/MFC (as KeePass 1).<br />
After many years, I switched to KeePass 2 in March 2015 due to the much richer feature set.<br />
Also the Android version of Keepass2Android is much better.<br />
<br />
I created the following plugins for KeePass 2:<br />
<br />
== TCATO Placeholder ==<br />
<br />
[http://keepass.info/help/v2/autotype_obfuscation.html Two-Channel Auto-Type Obfuscation (TCATO)] is a very powerful new feature of KeePass 2. Instead of just auto-typing the information, TCATO splits the information and transfers parts of it via the clipboard. This makes it much harder for keyloggers to capture the information. TCATO can be enabled/disabled on a '''per-entry''' basis.<br />
<br />
Unfortunately, TCATO does not work for all windows, for example PuTTY. Hence, often you want to enable/disable TCATO per auto-type sequence. Example: Some stupid online banking systems (e.g. BAWAK PSK has this stupid "feature") prevent usage of the clipboard in some input fields, for example when changing the password. In this case you can selectively disable TCATO for this sequence.<br />
<br />
Example:<br />
Auto-Type-Window: BAWAG P.S.K. eBanking - ebanking.bawagpsk.com*<br />
Auto-Type-Sequence: {C:Login}{DELAY 200}{USERNAME}{TAB}{PASSWORD}{ENTER}<br />
Auto-Type-Sequence: {C:change password}{TCATO:false}{PASSWORD}{TAB}{NEWPASSWORD:/PSK/}{TAB}{NEWPASSWORD:/PSK/}<br />
<br />
[[Datei:Download Plugin]]<br />
[[Datei:Download Source Code]]</div>Nikihttp://niki.hammler.net/w/index.php?title=MyPhoneExplorer:_Reconnect_USB_Plugin&diff=1616MyPhoneExplorer: Reconnect USB Plugin2015-03-19T22:03:52Z<p>Niki: /* Internals */</p>
<hr />
<div>[http://www.fjsoft.at MyPhoneExplorer] (MPE) is a great tool for synchronizing and controlling an Android phone over ADB with Windows.<br />
<br />
My use case is as follows: I usually have turned on Bluetooth and connect to MPE over Bluetooth. However, in my office I use a dockingstation. Not only for charching the battery but also for providing a high-speed connection for synchronizing my files.<br />
<br />
I would like MPE to automatically use USB connection (and drop Bluetooth) when I insert the phone into the dockingstation. This is where "MPE Reconnect" comes into play: It is a very light footprint (13k) exe that just resides in background once called. It waits for an Android ADB device over USB. And once such a device is identified, it makes MPE do a disconnect, followed by a reconnect, effectively dropping Bluetooth connection and using USB connection.<br />
<br />
This however requires that the connection type is set to "Automatic" in the settings.<br />
<br />
If MPE_Reconnect.exe is started ''after'' MPE, it displays a short startup greeting via a balloon over the MPE tray icon.<br />
<br />
Whenever an ADB device has been plugged it, it isses a reconnect command and displays a balloon over the MPE tray icon.<br />
<br />
<br />
== Screenshot ==<br />
<br />
<br />
The "screenshot" looks as follows:<br />
<br />
[[Datei:MPE_Reconnect.png]]<br />
<br />
<br />
== Installation ==<br />
<br />
<br />
Installation: Just copy MPE_Reconnect.exe to the MPE installation directory (where MyPhoneExplorer.exe resides). '''The executeable must be in the same directory!''' Call MPE_Reconnect.exe manually. It will reside in background and use essentially no resources (just a few kB RAM and only wakes up when a device is attached).<br />
<br />
== Download ==<br />
<br />
<br />
[[Datei:MPE_Reconnect_v1.0.zip]]<br />
<br />
<br />
<br />
== Internals ==<br />
<br />
The exe generates a small, invisible window and registers for device notification via RegisterDeviceNotification. It then waits for WM_DEVICECHANGE (it does nothing more). When a device of type DBT_DEVTYP_DEVICEINTERFACE connects, the first part of the device path for the compound device is extracted (the compound device is usually the smartphone device itself and has modem ports, file access or ADB as children). For example, for my phone:<br />
<br />
\\?\USB#VID_04E8&PID_6860#1a02869f#{a5dcbf10-6530-11d2-901f-00c04fb951ed}<br />
<br />
becomes<br />
<br />
\\?\USB#VID_04E8&PID_6860<br />
<br />
Using AdbWinApi.dll from the MPE DLL subdirectory, it is checked if there is an active ADB device matching this compound device. For this purpose, AdbEnumInterfaces, together with AdbNextInterface is used to iterate over all available ADB interfaces. The appropriate ADB device in my case looks like:<br />
<br />
\\?\usb#vid_04e8&pid_6860&adb#7&232e4fec&0&0003#{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}<br />
<br />
so the check reduces to a simple substring search.<br />
If there is a match, the program uses ShellExecute to execute:<br />
<br />
MyPhoneExplorer.exe action=disconnect<br />
// sleep for 3 seconds<br />
MyPhoneExplorer.exe action=connect<br />
<br />
It also displays a balloon over the MPE tray icon. Unfortunately the the HWND which handles the tray icon in MPE is just arbitrary! A window without caption and non-unique WNDCLASS. For this reason I decided to use a not very clean ''shotgun technique'' (yeah, I just invented this term): First, any window that starts with "MyPhoneExplorer" is found using EnumWindows. For each of those, all child windows are enumerated using EnumChildWindows and a Shell_NotifyIcon is issued for these HWND. This is not clean at all but it does not harm either.<br />
<br />
== Discussion ==<br />
<br />
<br />
<comments />{{:{{TALKSPACE}}:{{PAGENAME}}}}</div>Nikihttp://niki.hammler.net/w/index.php?title=MyPhoneExplorer:_Reconnect_USB_Plugin&diff=1615MyPhoneExplorer: Reconnect USB Plugin2015-03-19T22:03:10Z<p>Niki: /* Internals */</p>
<hr />
<div>[http://www.fjsoft.at MyPhoneExplorer] (MPE) is a great tool for synchronizing and controlling an Android phone over ADB with Windows.<br />
<br />
My use case is as follows: I usually have turned on Bluetooth and connect to MPE over Bluetooth. However, in my office I use a dockingstation. Not only for charching the battery but also for providing a high-speed connection for synchronizing my files.<br />
<br />
I would like MPE to automatically use USB connection (and drop Bluetooth) when I insert the phone into the dockingstation. This is where "MPE Reconnect" comes into play: It is a very light footprint (13k) exe that just resides in background once called. It waits for an Android ADB device over USB. And once such a device is identified, it makes MPE do a disconnect, followed by a reconnect, effectively dropping Bluetooth connection and using USB connection.<br />
<br />
This however requires that the connection type is set to "Automatic" in the settings.<br />
<br />
If MPE_Reconnect.exe is started ''after'' MPE, it displays a short startup greeting via a balloon over the MPE tray icon.<br />
<br />
Whenever an ADB device has been plugged it, it isses a reconnect command and displays a balloon over the MPE tray icon.<br />
<br />
<br />
== Screenshot ==<br />
<br />
<br />
The "screenshot" looks as follows:<br />
<br />
[[Datei:MPE_Reconnect.png]]<br />
<br />
<br />
== Installation ==<br />
<br />
<br />
Installation: Just copy MPE_Reconnect.exe to the MPE installation directory (where MyPhoneExplorer.exe resides). '''The executeable must be in the same directory!''' Call MPE_Reconnect.exe manually. It will reside in background and use essentially no resources (just a few kB RAM and only wakes up when a device is attached).<br />
<br />
== Download ==<br />
<br />
<br />
[[Datei:MPE_Reconnect_v1.0.zip]]<br />
<br />
<br />
<br />
== Internals ==<br />
<br />
The exe generates a small, invisible window and registers for device notification via RegisterDeviceNotification. It then waits for WM_DEVICECHANGE (it does nothing more). When a device of type DBT_DEVTYP_DEVICEINTERFACE connects, the first part of the device path for the compound device is extracted (the compound device is usually the smartphone device itself and has modem ports, file access or ADB as children). For example, for my phone:<br />
<br />
\\?\USB#VID_04E8&PID_6860#1a02869f#{a5dcbf10-6530-11d2-901f-00c04fb951ed}<br />
<br />
becomes<br />
<br />
\\?\USB#VID_04E8&PID_6860<br />
<br />
Using AdbWinApi.dll from the MPE DLL subdirectory, it is checked if there is an active ADB device matching this compound device. For this purpose, AdbEnumInterfaces, together with AdbNextInterface is used to iterative over all available ADB interfaces. The appropriate ADB device in my case looks like:<br />
<br />
\\?\usb#vid_04e8&pid_6860&adb#7&232e4fec&0&0003#{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}<br />
<br />
so the check reduces to a simple substring search.<br />
If there is a match, the program uses ShellExecute to execute:<br />
<br />
MyPhoneExplorer.exe action=disconnect<br />
// sleep for 3 seconds<br />
MyPhoneExplorer.exe action=connect<br />
<br />
It also displays a balloon over the MPE tray icon. Unfortunately the the HWND which handles the tray icon in MPE is just arbitrary! A window without caption and non-unique WNDCLASS. For this reason I decided to use a not very clean ''shotgun technique'' (yeah, I just invented this term): First, any window that starts with "MyPhoneExplorer" is found using EnumWindows. For each of those, all child windows are enumerated using EnumChildWindows and a Shell_NotifyIcon is issued for these HWND. This is not clean at all but it does not harm either.<br />
<br />
== Discussion ==<br />
<br />
<br />
<comments />{{:{{TALKSPACE}}:{{PAGENAME}}}}</div>Nikihttp://niki.hammler.net/w/index.php?title=MyPhoneExplorer:_Reconnect_USB_Plugin&diff=1614MyPhoneExplorer: Reconnect USB Plugin2015-03-19T22:01:09Z<p>Niki: /* Installation */</p>
<hr />
<div>[http://www.fjsoft.at MyPhoneExplorer] (MPE) is a great tool for synchronizing and controlling an Android phone over ADB with Windows.<br />
<br />
My use case is as follows: I usually have turned on Bluetooth and connect to MPE over Bluetooth. However, in my office I use a dockingstation. Not only for charching the battery but also for providing a high-speed connection for synchronizing my files.<br />
<br />
I would like MPE to automatically use USB connection (and drop Bluetooth) when I insert the phone into the dockingstation. This is where "MPE Reconnect" comes into play: It is a very light footprint (13k) exe that just resides in background once called. It waits for an Android ADB device over USB. And once such a device is identified, it makes MPE do a disconnect, followed by a reconnect, effectively dropping Bluetooth connection and using USB connection.<br />
<br />
This however requires that the connection type is set to "Automatic" in the settings.<br />
<br />
If MPE_Reconnect.exe is started ''after'' MPE, it displays a short startup greeting via a balloon over the MPE tray icon.<br />
<br />
Whenever an ADB device has been plugged it, it isses a reconnect command and displays a balloon over the MPE tray icon.<br />
<br />
<br />
== Screenshot ==<br />
<br />
<br />
The "screenshot" looks as follows:<br />
<br />
[[Datei:MPE_Reconnect.png]]<br />
<br />
<br />
== Installation ==<br />
<br />
<br />
Installation: Just copy MPE_Reconnect.exe to the MPE installation directory (where MyPhoneExplorer.exe resides). '''The executeable must be in the same directory!''' Call MPE_Reconnect.exe manually. It will reside in background and use essentially no resources (just a few kB RAM and only wakes up when a device is attached).<br />
<br />
== Download ==<br />
<br />
<br />
[[Datei:MPE_Reconnect_v1.0.zip]]<br />
<br />
<br />
<br />
== Internals ==<br />
<br />
The exe generates a small, invisible window and registers for device notification via RegisterDeviceNotification. It then waits for WM_DEVICECHANGE (it does nothing more). When a device of type DBT_DEVTYP_DEVICEINTERFACE connects, the first part of the device path for the compound device is extracted (the compound device is usually the smartphone device itseld and has modem ports, file access or ADB as children). For example, for my phone:<br />
<br />
\\?\USB#VID_04E8&PID_6860#1a02869f#{a5dcbf10-6530-11d2-901f-00c04fb951ed}<br />
<br />
becomes<br />
<br />
\\?\USB#VID_04E8&PID_6860<br />
<br />
Using AdbWinApi.dll from the MPE DLL subdirectory, it is checked if there is an active ADB device matching this compound device. For this purpose, AdbEnumInterfaces, together with AdbNextInterface is used to iterative over all available ADB interfaces. The appropriate ADB device in my case looks like:<br />
<br />
\\?\usb#vid_04e8&pid_6860&adb#7&232e4fec&0&0003#{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}<br />
<br />
so the check reduces to a simple substring search.<br />
If there is a match, the program uses ShellExecute to execute:<br />
<br />
MyPhoneExplorer.exe action=disconnect<br />
// sleep for 3 seconds<br />
MyPhoneExplorer.exe action=connect<br />
<br />
It also displays a balloon over the MPE tray icon. Unfortunately the the HWND which handles the tray icon in MPE is just arbitrary! A window without caption and non-unique WNDCLASS. For this reason I decided to use a not very clean ''shotgun technique'' (yeah, I just invented this term): First, any window that starts with "MyPhoneExplorer" is found using EnumWindows. For each of those, all child windows are enumerated using EnumChildWindows and a Shell_NotifyIcon is issued for these HWND. This is not clean at all but it does not harm either.<br />
<br />
== Discussion ==<br />
<br />
<br />
<comments />{{:{{TALKSPACE}}:{{PAGENAME}}}}</div>Niki