Stephans Blog
Private Blog

This is the private blog of Stephan Bösebeck, covering topics like Multicopters, Drones, Games... Leisure stuff...

covering topics like Multicopters, Drones, Games... Leisure stuff...

found results: 154

<< 1 ... 2 ... 3 ... 4 ... 5 ... 6 ... >>

category: Computer

The ErgoDox EZ reinforcement kit...

2017-05-20 - Tags: ergodox-ez

What's that?

The first persons to get the ErgoDox EZ were lucky, and happy. Only until they learned, that there is a little flaw in the first Batch of ErgoDox-EZ's (what's the correct plural for that?). The thing is, if you happen to connect your EZ to the computer without having the two halfs connected properly, the keyboard might stop working for good. Everybody from the first batch got this little Email from Erez explaining things and offering this reinforcement kit. I chose the reinforcement kit - as it needs a bit of soldering, it might not be the solution for everybody.

Just to make that clear, this does only affect a very little number of the first customers to receive the ErgoDox-EZ - only those, from batch 1 - not batch 1a or batch 2. Only if your ErgoDox got this batch number. And you got an email from Erez about this problem, too. So, if you did not receive this email, you probably have a different batch.

Why do I create this post, if it does not affect a lot of people:

  • maybe in future times, this might be interesting for others. and for me as well...
  • I want to show (off) the internals of the ErgoDox-EZ and the very good quality of it
  • and for the fun of it

This kit needs to be soldered and fixed at the PCB of both halfs of the ErgoDox, but it is actually not that hard...

What's in this kit?

Today I received the Reinforcement Kit from USA. It took quite some time to get shipped and through customs. Which is a bit strange, as the kit only contains

  • two very little PCB
  • two new backplate stickers for your ergodox halfs
  • a 3 page instruction manual with photos

And that's it! The two little PCBs need to be soldered to the PCB of each keyboard half, should not be so hard....

Installing the kit.

It took me about 30 minutes in total to do that, and I'm really not practiced in soldering such delicate things. It worked fine, as it seems.

First you need to remove the stickers from the back, as below the sticker there is one screw that needs to be removed. You only need to loosen those screws and then take the lid off...

To remove the stickers, a cutter actually comes in very handy.

Just to mention: on the big sticker there is actually a little small sticker with your serial number. I removed that first (also with the help of the cutter) and kept that for reattaching to the new stickers afterwards...

After that, remove those screws one after the other. That should be more or less self explanatory😉

I kept the screws "lying" in the holes, so I did not need to search for them when putting everything back together. So I removed the lid with the screws still inside the holes, but lose.

You might have noticed that I put some valcro tape on the back of both halfs. This way I can "stick" them together for transportation purpose. In my case it’s a bit tilted, so I don't need to remove the tent. Makes transporting the ErgoDox EZ a bit more safe and easy.

So, back to the Reinforcment Kit. When you removed it lid, you reveal the real beauty of your keyboard, the inner soul ;-)

"Above" (or below, depends on your point of view) the inter-keyboard-half-connector (or simple: audio jack), there you need to solder the little PCB that came with the kit to the PCB of the keyboard:

If you have a look at the labels on the keyboards PCBs, they're actually wrong... meaning that the left half of the keyboard is actually labeled right. But this is probably due to the production process. So keep calm, all is ok..

So, now you only need to fix the kit-PCB to the big one. This not that hard to do, you only need to solder it on 4 places. What makes it a bit hard is that it is so damn small! If you're not used to soldering such delicate things, take your time. For some experienced guy this is probably done within a couple of minutes.... I took my time doing that... and it ended up being really kind of ugly:

it really does not look good, but it seems it is working fine. At least the keyboard is... and that's what counts for the moment ;-)

After soldering you only need to repeat the steps above in the opposite order... and voilĂĄ! You reinforced your Ergodox-EZ!

I asked Erez how would I know, if the soldering went on well? How do I know that the fix is in place properly.... the answer was "if your keyboard is still working, everything is fine." - So, as I type this on my reinforced ErgoDox-EZ, it seems to be all fine!

category: Computer

OSX Yosemite Beta 7

2017-05-20 - Tags:

no english version available yet

category: Computer

The Infinite loop of performance improvement

2017-05-20 - Tags: tweet fun

category: global


2017-05-20 - Tags: jblog

hi ho,

as you all know, the software here is quite new and of course i found some bugs i did not realize till I went live...

unfortunately I cannot deploy without downtime yet sorry

I will try to keep it to a minimum!


category: global --> drones

Drones and such...

2017-05-19 - Tags: drone legal gesetzliches drohne

Some of you might know, that in Germany there is a new regulation for drones and UAVs (unmanned areal vehicle). I just wanted to post something about that. As this is my Hobby and I'm directly affected by this...

I already wrote some things about that here.

Now, since a couple of months this new regulation is effective, wich is aiming a lot at those camera carrying drones like Phantom and such. (This list is not intended to be exhaustive. This is what I researched for me and my type of flying)

  • you are not allowed to fly higher than 100m - but you might get a permit (new)
  • you need to stay in line of sight
  • you are not allowed to fly above crowds of people
  • not allowed to fly near highways (Bundesstrasse, Autobahnen) and water ways (most bigger rivers)
  • not near official buildings like police and such. Also not near or above factories (Nuclear Plants)
  • not above private property, unless you have a permit from the owner. (or your drone does not carry a camera or video transmitting device or is lighter than 250g)
  • all drones that are heavier than 250g need a non flammable plate with the full address of the owner
  • if your drone is heavier than 2kg, you need a proof of knowledge (some kind of test, I guess)
  • everything heavier than 5kg can only be flown if you have a dedicated permit for that thing
  • flying at night is forbidden
  • drones heavier than 250g can be flown FPV only if you have a spotter nearby, who will warn you if anything happens. Before the new regulation, the spotter actually needed to be ably to fly the drone...
  • is your drone lighter than 250g, you can fly without spotter, and you do not need a plate on it
  • in all cases, you need to have an insurance
  • it seems like, it is not necessary to have a special permit if you want to fly for business (or it is easier to get one)

in addition to that, the old No-Fly-Zones (Airports, Helipads etc) are also still valid. Also flying in natural reserves usually is vorbidden.

For the usual drone-Flyer thit actually does not mean a lot of change. Well, except for those, who like to fly 200m high, this might be a bit annoying.

But the most important thing, it seems nobody actually knows, that these regulations existed and do exist! Especially the media is not really a role model here. It seems like every 2nd shot needs to be a cool drone shot, no matter if flown over cities, private property, autobahns or whatever.

Just the other day on RTL, they filmed in the garden of some Messie using a drone! I bet they did not have a permit for doing that. Not only that flying above private property is forbidden, also it is not allowed to invade someones privacy with or without a drone - and this was privacy invasion, if you asked me.

No wonder people get afraid of this technology. "Can you film me from up there" and if I show them, what kind of photo that is, they are usually reassured.

But if dad goes in to the next tech marked and buys a drone for his son, the guy at the counter will not tell him, that he needs to have an insureance and for that heavy thing you need to have a proof of knowledge and btw. flying before the age of 14 is not allowed"... No, he will not say something like that, because that might prevent the deal.

realy a sad world

category: Computer

New blogging software

2017-05-16 - Tags: java jblog security

I did complain about wordpress several times (for example here). I took that for an opportunity, to take on my software development skills and use a weekend or two to build a new blogging software. Well, th result is this wonderful (well... hop so) page here.

PHP sucks

To stop all PHP fainbois from whyning, I do not like PHP very much, because I don't know it very much. Hence, wordpress is also kind of a mystery for me. The configuration works with luck, let alone get php to do what you want in a more secure way.

so, my blog was hacked several times during the last year now and this is pissing me off! So, I wanted to use a java based solution, but it seems like there is no simple, easy to use one out there.

so why not do it yourself?

exactly. That was my thought also. Could not be so complicated, could it? So, I wanted to create a blogging software that

  • has a simple technology stack
  • does not need a complex plugin funktionality. If it cannot do, what I like it to do, i rewrite it
  • themes or designs... well... er... could be better, but I think this is ok
  • Security, that is the point. I created the blogging software (called it jblog - not rally creative) myself and it is not so complex as wordpress. So we should be ok. I guess. But I know for sure, that th standard wordpress exploits wont work no more!
  • Intrnationalization... also a topic. jblog does only do 2 languages, German and English (I do not speak more, so I don't need more for my blogs).
  • whitelabeling. I have a couple of domains, I wanted to reuse / revive with this project.
  • one administration: I did not want to create the same thing 3 times, I wanted to have the same thing look like 3 different hings. Hence there should only be one administration page.


I am quite ok with what I accomplished here. Although it took longer than one weekend, it was finished quite fast. I lik that.

But please: if some links do not work anymore, some images look strange or are missing - I will fix this eventually emoji people:smirk

the different blogs - this blog here

the private main blog. Will cover topics like hobby, drones, games, gadgets etc. - the java blog

There I will put all my opnsource stuff, like morphium. And all the other programming tips and tricks I wrote over time. Hmm... seems like 'java blog' is not the right term...

This should be a business site anyways. So, here I will put in topics about my professional carreer, Scrum, processes etc.


well, this is going to be tough. I cannot produce content for 3 full blogs. Even filling one is quite hard. But I will try. And we will see, how that works

technical discussion

as mentioned above - not here, but at emoji people:smirk

category: security

Sometimes, I hate Wordpress

2017-04-04 - Tags: php blog

This site was hacked again!

Well, the title is a bit missleading, as it is not only Wordpress at stake here, it is also related to php and obviously apache also.

I was not very active here for a couple of weeks, and obviously missed an update for Wordpress and some of the plugins. And that was enough for a white hat hacker to hack the site... well white is probably not the right color, as he posted links to illegal sites here.

Disclaimer: It was not me adding those links to download portals of illegal stuff! unfortunately I cannot tell, where the attack came from.

But I can tell, that he only had access to the Wordpress-Stuff. This happened again! << Sarcasm_mode >> Apache, PHP and Wordpress are in this respect really a _great_ team... << / Sarcasm_mode >>

I know, that this will cause some people to call me a troll, but I can tell you, from a professional point of view, there are way better solutions from a security point of view to create websites. Yes, most of them are complicated and complex. But at least, you cannot get hacked that easily...

PHP is a fine language, if you want to build a calculator or something like that. For professionals this is crap. Even Facebook needed to create their own interpreter (yeah, because of speed issues, but who knows what else).

Sorry, this php stuff pisses me off... was hacked here, that happened to customers of mine using PHP-based software....

Need to find something more reliable...

category: Tweet --> global

Tweet: War ein toller Vortrag von @TCole1066 gestern auf...

2016-10-26 - Tags: tweet

sorry, no english version available

category: global

Drohnen und so.

2016-10-08 - Tags: drohne fpv

no english version available yet

category: Computer --> Test of Tools

Test Of Tools: Nach Hause Telefonieren - VPN mit OSX / iPhone

2016-05-30 - Tags: vpn howto test of tools osx security

no english version available yet

Eigentlich kein echtes "test of tools", weil nicht viele Tools vorkommen, aber dennoch hab ich es mal zu dieser Rubrik gepackt.

Folgendes Scenario: man ist unterwegs oder in der Arbeit oder sonst wo und möchte kurz daheim mal auf seinen Servern eine Datei holen oder mal schnell eine TV-Aufnahme mit der Dreambox Programmieren. Eine eigentlich lösbare Aufgabe sollte man meinen. Hier eine Aufstellung der von mir getesteten Möglichkeiten (und ein paar Tipps dazu):

"Eigenes" VPN mit SSH

Naja, so richtig als VPN kann man das nicht bezeichnen. Aber man kann per SSH ne Menge machen. Das einzige, was man tun muss, ist in seinem Router einen Port frei schalten. Bei der Fritz!Box ist das unter Internet->Freigaben:

Man kann Portfreigaben deaktivieren, aus SicherheitsgrĂŒnden hab ich hier mal ein paar versteckt. Der Dynamic DNS Eintrag ist wichtig (s.u.) und mit dem Button "Neue Portfreigabe" kann man eine Neue Freigabe einrichten - das sieht dann so aus:

Dabei gibt man an, welche externe also öffentliche port-Range (von-bis) auf den Computer im eigenen Netz geleitet werden sollen. FĂŒr SSH sollte der Zielport 22 sein (das ist der Standardport fĂŒr ssh), Protokoll ist TCP. Leider gibt es in der Vorauswahl von Anwendungen SSH nicht, weshalb man auf "Andere Anwendung" gehen muss. Achtung: Nutzt nicht Exposed host! Dann wird der gesamte Traffic an den Rechner weitergeleitet und das will man normalerweise nicht.

Das ganze kann natĂŒrlich nur funktionieren, wenn man auch dyndns oder so was eingerichtet hat - sonst "findet" man seinen Router ja gar nicht und kommt somit auch nicht an die freigegebenen Ports.

Wobei man da schon beim nĂ€chsten Problem ist: Wohin sollte man den Port weiter leiten. Man benötigt da also irgendwas, was nen SSH-Server laufen lĂ€sst. Man kann das schon auf der FritzBox selbst machen, oder normalerweise auch auf den meisten anderen Routern, aber das erfordert doch ein wenig Geschick: Anleitung dafĂŒr gibt’s zum Beispiel hier.

Wenn man in der Firmware des Routers nicht rumfummeln will, dann benötigt man irgend einen anderen Rechner im Netz, der als SSH-Endpunkt dient. Da funktioniert z.B. auch die Qnap (wobei man evtl. den SSHD hier auch korrigieren muss: siehe hier). Ein Mac oder Linux Rechner wÀre Ideal, ein Windows-PC geht auch - allerdings muss man sich dann nen SSHD installieren (mit cygwin z.B.).

Der Standard-Port des SSH ist Port 22. Man sollte allerdings vermeiden, den Port 22 nach außen frei zu schalten, sondern man sollte da irgend einen anderen nehmen, am besten was ĂŒber 1024 oder sogar noch grĂ¶ĂŸer. Da alle ports < 1024 gerne mal gescannt werden und es ne Menge Scripts gibt, die versuchen mit "default"-Passwörtern einzubrechen (und sich ein paar MöchtegernHacker dann tierisch freuen, wenn sie "eigebrochen" sind... dann sind die total 1337).

Da sind wir dann auch schon beim nĂ€chsten Tipp: gute Passwörter verwenden! Oder, wenn man den Zugriff nur von wenigen Rechnern aus machen möchte, dann kann man auch eine Public-Key Authentifizierung verwenden und die Password-Auth Komplett ausschalten. Die Konfiguration dafĂŒr ist ein wenig abhĂ€ngig vom Betriebssystem aber im Allgemeinen muss man im Home-Verzeichnis des Users, der sich anmelden soll (auf dem SSH-Server!), ein Verzeichnis namens .ssh anlegen. Dieses sollte nur fĂŒr den Nutzer les- und schreibbar sein. In dem Verzeichnis legt man ein File an, names "authorized_keys". Das ist ein einfaches Textfile in dem man die PublicKeys aufnimmt.

Die Public-Keys muss man dann auf dem Client erstellen, also auf dem Notebook mit dem man unterwegs ist. Das funktioniert auch wieder recht unterschiedlich, unter Windows nutzen viele Putty, da gibt’s dafĂŒr nen MenĂŒpunkt. In der Shell tippt man einfach ein

ssh-keygen -t rsa -b 2048
Damit wird ein neues Keypair erzeugt. Das liegt wieder in dem .ssh-Verzeichnis des Users und besteht aus 2 Dateien: id_rsa und Die pub-Datei ist der Public key, dessen Inhalt mĂŒsst ihr einfach in das Authorized-Keys File auf dem Server einfĂŒgen. Dann sollte der Zugriff gehen.

Und wie geht das jetzt mit dem Tunnel? Dazu muss man im Client den Aufruf entsprechen Konfigurieren. Bei Putty unter Windows gibt es da Dialoge fĂŒr die Einstellung der tunnel. Aber auch in der Kommandozeile geht das recht simpel:

ssh -l user -L1234:
so wird z.B. eine Verbindung zu aufgebaut. Wenn man sich erfolgreich mit dem Benutzer "user" eingeloggt hat, wird ein Tunnel geöffnet: Alle Anfragen an den lokalen Port 1234 werden ĂŒber SSH weitergeleitet an den Server, welcher seinerseits die Anfragen und Daten weiterleitet an in diesem Fall den Server mit der IP, Port 80.

D.h. wenn ich jetzt in meinen Browser die URL http://localhost:12345/ eingebe, lande ich auf dem Webserver mit der IP

Man kann zwar nahezu beliebig viele solche Tunnelangaben beim Aufruf von SSH machen, das ist aber wenig spassig, und man ist auch immer auf der Suche nach den richtigen Ports. Zum GlĂŒck gibt es auch dynamische Ports

ssh -l user -D 1234
Damit wird ein dynamischer SOCKS-Proxy erzeugt. Dieser funktioniert quasi identisch zu dem manuellen Tunnel mit -L, aber er baut dynamische Tunnel zu beliebigen Zielen auf. Nachteil: die Anwendungen, die man nutzen will, mĂŒssen SOCKS unterstĂŒtzten. Die gĂ€ngigen Browser tun das alle, aber bei anderer Software wird es schnell eng...

Außerdem kommt man so auch nur schwer an die Freigaben von z.B. seinem NAS ran oder so.

Übrigens: das funktioniert auch mit dem iPhone - die SSH-Clients fĂŒr das iPhone unterstĂŒtzen alle auch Tunnel...

die FlexibilitĂ€t ist natĂŒrlich extrem, ich kann jeden beliebigen Port weiterleiten. Allerdings muss ich das auch, wenn ich darauf zugreifen will.

Die Nachteile liegen somit ziemlich auf der Hand: man muss alle ports mehr oder minder manuell mappen und dann funktioniert es auch nicht immer reibungslos (AFP-Sharing z.B.). Namensauflösung darĂŒber zu machen ist auch schwer, da man kein UDP-tunnel machen kann, sondern nur TCP. Deswegen ist das eine recht gute Lösung fĂŒr den Notfall, aber fĂŒr den mehr oder minder tĂ€glichen Zugriff ist das nix.

TestOfTools Rating: 4/10 Punkten


Pseudo VPN mit ShareTool

Im Endeffekt ist das eine grafische OberflĂ€che fĂŒr die oben beschriebenen SSH-Methoden + noch mehr. Allerdings ist die Software nicht umsonst - dafĂŒr wirklich "Narrensicher";-)

Sharetool 2 bekommt ihr hier - probiert mal die Demo aus, das ist echt ok - die $20 sind gut investiert, wenn man auf "daheim" zugreifen möchte.

Sharetool benötigt allerdings einen Mac auf dem es laufen kann - Linux oder Windows lÀuft leider nicht. Was sicher einer der Nachteile von Sharetool ist. Allerdings ist die Einrichtung denkbar simpel und man benötigt nicht mal so was wie Dyndns - das erledigt der Sharetool Service. Auf dem Server, also dem Rechner im Heimnetz, startet man Sharetool und konfiguriert das sharing:

Dabei könnte man seine eigene Portfreigabe verwenden, oder sich von sharetool einen eigenen Port konfigurieren lassen - sofern euer Router UPNP versteht. Falls ihr das das erste Mal macht, mĂŒsst ihr noch einen Login anlegen. Der Server meldet sich dann unter dieser Kennung mit seiner öffentlichen IP-Adresse an. Clientseitig lĂ€uft das genaue "Gegenteil" - man loggt sich ein, erhĂ€lt die IP Adressen der verschiedenen Netzwerke unter eurer Kennung und man kann sich aussuchen, wo man sich einloggen will:

Nach dem Login kann man aus den bekannten Netzen wĂ€hlen und sich ggf. verbinden. DafĂŒr ist zwingend ein User auf der anderen Seite nötig, als der ihr euch einloggen könnt. Ich wĂŒrde aus SicherheitsgrĂŒnden dazu raten, einen eigenen User nur fĂŒr diesen Zweck einzurichten, der sonst keine Rechte am System hat - Das kann man am Mac ja relativ simpel machen. Vergebt fĂŒr diesen User aber bitte ein vernĂŒnftiges Passwort oder authentifiziert euch mit dem Public-Key des SSH (s.o.).

Auf dem Mac kann man das auch in /etc/sshd_config einstellen, genauso, wie unter Unix ĂŒblich. In der Systemsteuerung gibt’s das HĂ€ckchen "Entfernte Anmeldung". Das startet, bzw. stopped den SSHD. Wenn ihr also eine Änderung an der /etc/sshd_config gemacht habt, solltet ihr den Server kurzt neu starten. Hier die wichtigsten settings:

PubkeyAuthentication yes - ist per Default an, kann man aber explizit im File setzen, wenn man möchte AllowRootLogin no - sollte zwingend aus sein PasswordAuthentication no - aus, falls man sich nur per PublicKey authentifizieren möchte, ansonsten mĂŒssen ALLE user ein gutes Passwort haben ValidUsers USER1 - so kann man den Login auf nur einen User reduzieren, alle anderen dĂŒrfen nicht
Mit diesen Settings ist auch euer Mac einigermassen sicher fĂŒr angriffe von außen - allerdings wĂŒrde ich immer ein gutes Passwort vergeben.

Hat man es geschafft, sich anzumelden, bekommt man von ShareTool eine sehr praktische Auswahl aller Bonjour-Services:


Durch einen Doppelklick kann man sich dann mit dem entsprechenden Service verbinden - so als wĂ€re man im eigenen Netz... Und möchte man dann noch "Anonym", also ĂŒber seine eigene Home-Verbindung im Internet surfen (das ist manchmal ganz praktisch fĂŒr sehr strikte firmenpolitik), dann kann man unter Options den MenĂŒpunkt "Browse Web securely" wĂ€hlen. Das öffnet den Firefox und surft dann ĂŒber den SSH-Tunnel und seine eigene Leitung.

Nachteile von dieser Lösung: Man bekommt eigentlich nur relativ Problemlosen Zugriff auf Bonjour Services, alles was darĂŒber raus geht, erreicht man nicht. Man kann zwar auch eigene Services registrieren, aber das ist ein gefummel und habe ich noch nicht hin bekommen - wenn Ihr da ne Idee habt, immer her damit ;-)

Aber fĂŒr die Meisten sollte das gut reichen, da der Zugriff auf Shares, Web, Printer und Screen Sharing gut funktioniert.

Ist noch erschwinglich und ist eine solide 90% Lösung, sofern man einen MacServer hat - und das können nicht viele von sich behaupten.

TestOfTools Rating: 7/10 Punkten


Das ist eine "echte" VPN Lösung, die den Netzwerktraffic auf einer der unteren OSI-Layern verschlĂŒsselt. Das ganze funktioniert auch ĂŒber SSL und verlangt keine besonderen Einstellungen oder FĂ€higkeiten vom Router oder Provider  - es gibt auch eine Implementierung fĂŒr das iPhone oder Android, allerdings nicht nativ, muss gesondert installiert werden.

OpenVpn wird immer beliebter, hat aber leider noch nicht in viele Router einzug gehalten. Deswegen benötigt man auch hier einen eigenen Server, der als OpenVPN-Server fungiert. HierfĂŒr muss im Router eine Portfreigabe eingerichtet werden - normalerweise UDP 1194. Ist aber frei wĂ€hlbar.

FĂŒr den Zugriff vom Mac aus benötigt man einen Client, da auch hier keine native VPN-Implementierung verfĂŒgbar ist. Am besten bewĂ€hrt hat sich bei mir das Tool Tunnelblick, obwohl es noch immer im Beta Stadium ist. Dennoch klappt das recht gut, auch wenn der einwahlvorgang immer recht lange dauert (im Vergleich zu den anderen hier vorgestellten lösungen).

Als OpenVPN-Server habe ich die Qnap gewÀhlt, da geht das recht simpel:

hier kann man eigentlich nur den Haken bei "Server aktivieren" anschalten, dann lĂ€uft alles. Man muss nur noch die Konfigurationsdatei herunterladen und alles sollte einigemassen passen. Allerdings muss man da drin die Öffentliche IP Adresse vermutlich Ă€ndern. Da steht, wenn man nicht DynDns auch ĂŒber die Qnap macht, die gerade aktuelle öffentliche IP drin. Das funktioniert dann fĂŒr den Moment, aber morgen nicht mehr.

In Tunnelblick muss man nur ne neue Config anlegen, das erklÀrt sich mehr oder minder von selbst... auch wenn es einige Schritte sind.

Leider kann man hier das routing nicht einstellen, d.h. man surft immer komplett ĂŒber die Leitung "daheim". Also ein Zugriff nur auf das Netz, ohne den ganzen Traffic darĂŒber zu leiten ging nicht. Auch gibt es wohl einen Bug in der Qnap: Wenn man die Default-Route ausschaltet, geht gar nix mehr. War zumindest bei mir so...

Das ist allerdings auch erstaundlich simpel einzurichten und es funktioiniert recht solide, wenn man einen Brauchbaren Server hat. Dennoch gibt’s ein paar PunktabzĂŒge, da die Konfiguration so etwas nervig ist. Im normalfall wĂŒrde ich da 10/10 Punkten vergeben, aber da das ganze leider auf der Qnap ein wenig krankt bekommt das ganze weniger. auch ist schade, dass es keine Nativen Clients von Apple fĂŒr OSX und/oder iOS gibt, so wie fĂŒr IPSec Und leider auch keine Implementierung fĂŒr die Fritz!Box.

TestOfTools rating: 8/10


IPSec VPN mit Fritz!Box OS6.0

Das ist eigentlich wĂ€re das die optimale lösung. Allerdings war es bisher immer ein Graus, IPSec selbst zu konfigurieren. Vor allem, weil die Router spezielle Protokolle korrekt weitergeben mussten. Der Support fĂŒr IPSec war da nicht so verbreitet. Obwohl es angeblich die sicherste VPN-Variante sein sollte.

Zum glĂŒck ist die konfiguration mittlerweile in der Fritz!Box so stark vereinfacht worden, dass man das in ein paar Mausklicks zusammengestellt hat. wichtig: Man muss fĂŒr jeden VPN-Zugang einen User anlegen. Das Passwort dafĂŒr sollte entsprechend komplex sein.Die VPN-Einstellungen sind auch unter "Freigaben" zu finden, dort gibt es einen Reiter "VPN":

Dort kann man dann einen User fĂŒr den Remote Zugriff einrichten, oder netz-zu-netz verbindunge (also Fritz-zu-Fritz) einrichten.  Das ist ganz sinnvoll, wenn man zwei Standorte verknĂŒpfen will - die fungieren dann netzwerktechnisch als einer - was den Zugriff auf Fileserver etc. natĂŒrlich stark vereinfacht.

fĂŒr uns hier wichtig, ist der erste Punkt: Fernzugang fĂŒr einen Benutzer einrichten. Dort ist eigentich nur das HĂ€ckchen fĂŒr VPN zu setzen, ein gutes Passwort zu vergeben und das war es schon. Bei Bedarf kann man dem User auch noch Zugriff auf andere Services der Fritzbox gewĂ€hren. Das ist ganz interessant: wenn man aus dem lokalen Netzwerk auf die Fritz!Box zugreifen möchte, muss man ein Passwort eingeben. Macht man das selbe ĂŒber das VPN, dann kommt ein User/Passwort login - aus SicherheitsgrĂŒnden!

Die emailadresse kann ĂŒbrigens auch als Login benutzt werden, wenn ich das richtig verstanden habe. Bisher hatte ich das aber noch nicht nutzen mĂŒssen. Am Ende der ganzen Prozedur, kann man sich noch die Einstellungen fĂŒr iOS und Android anzeigen lassen:

Mit diesen Einstellungen kann man auch recht simpel den Zugriff von OSX aus einrichten. Dazu muss man eine Neue Netzwerkverbindung einrichten. Unter Systemeinstellungen->Netzwerk kann man durck klicken auf das "+" eine Neue Verbindung einrichten.

Nach dem man auf den + geklickt hat, muss man nur noch Cisco-VPN auswĂ€hlen und die Einstellungen von der Fritz!Box eintragen. DAbei auch nicht die "Authentifzierungseinstellungen" vergessen, denn dahinter verbirgt sich die Gruppe und das Shared Secret. Und auch wichtig: Unter "Weitere Optionen" muss der fĂŒr das Zielnetz gĂŒltige DNS angegeben werden - also die IP-Adresse der Fritz!Box - sowas wie oder so.

Das alles funktioniert normalerweise recht gut - auch hier ist wieder eine Dyndns-Anmeldung nötig. Allerdings hat das ganze einen kleinen Haken - man kann nicht mehr einstellen (OSX 10.9 mavericks), dass nicht der gesamte Traffic ĂŒber die Leitung gehen soll. Das konnte man frĂŒher mal einstellen, ist aber jetzt weg.

D.h. wenn ich eingewĂ€hlt bin, geht der gesamte IP-Traffik ĂŒber das VPN.

Korrigieren kann man das allerdings recht einfach: Es gibt eine Route, ĂŒber die das geregelt wird. in der Shell kann man das recht einfach korrigieren. Allerdings ist da manuelles Eingreifen nötig. FĂŒr die meisten ist das vermutlich eh kein Problem, sondern eher ein vorteil.

Der einzige Nachteil dieser Lösung ist, dass man wenig einstellen kann. Aber sonst ist das doch eine der besseren Varianten. Leider funktioniert es aber nicht ĂŒber 3G oder LTE - zumindest bei meinem Anbieter wird IPSec nicht unterstĂŒtzt. Evtl. ist das bei anderen Anbietern anders, im Zweifel solltet ihr euch erkundigen. Im WLAN/LAN sollte es eigentlich funktionieren, aber auch hier ist man AbhĂ€ngig vom WLAN/LAN Route. Wenn der IPSEc auch nicht unterstĂŒtz ist man .... angeschmiert. Deswegen auch hier nicht volle Punktzahl:

TestOfToolsRanking: 9/10


Irgendwie gibt es wohl keine 100%-Lösung, an der man nicht lange rumbasteln muss. 100% - zumindest was die FlexibilitÀt und routing etc betrifft, könnte man vermutlich nur mit einem eigenen Linux-Server und viel Zeit erreichen. Wenn man sich da reinfuchsen will, ist das sicherlich die 100% Lösung.

fĂŒr die allermeisten Zwecke sind die  hier vorgestellten Wege (abgesehen vom ersten vielleicht) völlig ausreichend. Wer spezielle Anforderungen hat, muss sich auch speziell darum kĂŒmmern.

Mein Favorit momentan ist das IPSec-VPN, da ich dafĂŒr nicht noch einen eigenen SSH oder OpenVPN-Server benötige. Ich konnte aber auch eine ganze Zeit lang ohne IPSec leben und das ganze mit ShareTool bzw. Openvpn erledigen, da ich hier (noch) einen MacMini rumstehen habe, der gerne auch mal was tun soll ;-)

Entscheiden mĂŒsst ihr wohl von Fall zu Fall, welche Lösung am besten auf eure BedĂŒrfnisse passt, da alle Lösungen eigene Nachteile haben:

  • SSH manuell ist viel zu kompliziert und erfordert eine Menge Wissen ĂŒber die Dienste, die man ansprechen will. FĂŒr NotfĂ€lle aber sicherlich sinnvoll
  • Sharetool zeigt nur Bonjour-Services, der zugriff auf andere ist schwierig
  • Sharetool kostet Geld
  • OpenVPN und ShareTool benötigen beide einen Server auf dem sie laufen können
  • IpSec natĂŒrlich auch, aber die Fritzbox unterstĂŒtzt es mittlerweile
  • OpenVpn hat keine Native Implementierung in OSX oder der Fritzbox.
  • OpenVPN ist beim Verbindungsaufbau recht langsam


category: Tweet --> global

Tweet: My week on Twitter: 1 Mentions, 4 Retweets, 378 Re...

2016-02-09 - Tags: tweet

sorry, no english version available

category: Tweet --> global

Tweet: ARG... Sky mal wieder...

2016-02-02 - Tags: tweet

sorry, no english version available

category: Tweet --> global

Tweet: update for my @ErgoDoxEZ review -ego-shooter suppo...

2016-02-01 - Tags: tweet

sorry, no english version available

category: Tweet --> global

Tweet: Sky mal wieder - ServicewĂŒste Deutschland. Macht e...

2016-02-01 - Tags: tweet

sorry, no english version available

category: Service in Germany

ServicewĂŒste Deutschland - Sky mal wieder

2016-02-01 - Tags: servicewueste sky tv

sorry, no english version available

category: Tweet --> global

Tweet: My week on Twitter: 1 Retweets, 15 Retweet Reach....

2016-01-26 - Tags: tweet

sorry, no english version available

category: Tweet --> global

Tweet: My week on Twitter: 1 Mentions, 2 Retweets, 590 Re...

2016-01-19 - Tags: tweet

sorry, no english version available

category: Tweet --> global

Tweet: ErgoDox EZ auf Deutsch | Stephans Blog - und auf d...

2016-01-17 - Tags: tweet

sorry, no english version available

category: Apple --> Computer

Mechanical Keyboard Razer Blackwidow Chroma on the Mac

2015-07-27 - Tags:

sorry, no english version available

category: Computer

Stephans Blog wieder online...

2015-06-12 - Tags: allgemein blog

no english version available yet

Das war stressig. Zum Umzug kam noch hinzu, dass mein Server die GrĂ€tsche gemacht hat. Ich musste neu installieren. Was ja – dank Backups – eigentlich kein allzu großer Aufwand wĂ€re, hĂ€tte ich nicht vergessen, ein Backup von der Datenbank zu machen
 Deswegen jetzt der neue Start des alten Blogs ;-)

category: Computer

ErgoDox EZ in German on a Mac

2015-05-22 - Tags: ergodox ergodox-ez keyboard

The ErgoDox EZ in German on a Mac

This introduction and review is already available in German here. Yes, I admit, I was following the Indiegogo campagne of the ErgoDox-EZ quite a while. And since about 5 days now I'm a proud owner of an ErgoDox-EZ keyboard! Details about the campaign and the ErgoDox-EZ can be found here.

Unfortunately the keyboard was designed for the english speaking areas and does have it's issues with international layouts. Hence it also has problems with the German layout - that means, when setting the operating system to German, the keys are not at the place they should be. At least not with the default firmware. Most of the special characters were "somewhere" on the keyboard - ok, that could be learned. And you need to get used to this keyboard a bit. But some of the umlauts (Ă¶Ă€ĂŒĂŸ) were spread around the keyboard as well. This made fluent typing (if you're touch-typing you know what I mean) nearly impossible. Well, the internet states this keyboard is fully programmable, everybody can make his own layout. Ok, this was not as easy as it sounds, but not as hard as it could be. Especially because I did not only want to fix the German layout, I also wanted to address other issues as well:

  • as already mentioned, the umlauts were spread across the keyboard, often in the lowest row of keys. They should return to the usual QWERTZ-location
  • I did have problems with the space key only being on the left side of the keyboard, as I'm typing space with both thumbs. (update: after using that, I learnt that having space on the right, having backspace on the left works way better!)
  • the location of CMD-keys was a bit bad * the ALT-keys were also a bit awkwardly located
  • I liked the idea of different layers, but the "Coder"-layer was not working with a German layout - about 70% of the keys were just sending the wrong keycodes (sometimes even umlauts) - that means, that about 70% of the keys were actually there, but at a wrong place. And the places were mixed up a lot. So, this thing is so greatly programmable, I read. let's go - how does that work? Well, this was kind of a setback, as this was not easy to find. There are a lot of github projects and forum discussion around the ErgoDox, but not really a simple howto. Thanks to Erez Zukerman (he initiated the indiegogo campagne) and that he replied after just a couple of hours after each of my questions (including the different time zones!), it did not take that long to get into the topic. Now, compiling a new custom firmware for the ErgoDox-EZ is no big deal anymore.

Disclaimer: what I describe here, are my findings, things that worked well for me. I'm not claiming this to be complete, or fitting for everybody (e.g. I cover only OSX German here). And, of course, this is probably not free of errors and faults. So, if you use these information, it's your responsibility. And please, read further documentation.

DE-Layout for the ErgoDox EZ on a Mac

I try to address all the issues mentioned above and created a first version of such a layout - it can be downloaded

here. Feel free to test it... This is what the layout looks like: There are some features I'd like to point out:

  • There are 4 layers in total, default layer (all normal keys), symbol or coder layer (containing all kinds of brackets, symbols etc which come in handy when coding), the media layer (there you can control the mouse and it contains multimedia keys like play/pause, volume up/down...) and last but not least a number block.
  • All umlauts are at their usual location * Because the umlauts are at their usual location, some of the special characters had to be moved to the lowest row of keys (like #)
  • the cmd and alt keys are now in the middle of the keyboard (on both halfs), CTRL is where the upper cursor keys were located. So, CTRL, CMD and ALT are located in a vertical row on the "inner" edge of each half of the ErgoDox EZ.
  • There is a space key on each half located in the thumb block
  • the tab and ESC-Keys were moved to their default location
  • the Caps-Lock-key is a layer switch now (as I don't use Caps-Lock at all)
  • several keycodes (like CTRL) are defined on multiple locations due to several reasons: sometimes I like to type for example CTRL on the right, sometimes on the left half of the keyboard, depending on the context. and I did not always know what to put at a certain key - too many keys there :) As already mentioned, this is a layout that works for me quite ok now. I will probably improve it over time (fortunately that is possible). It is opensource and available in github. Maybe you have additional ideas, how to improve things. Or you create your own custom firmware. But this is just the beginning...

Beginners guide / howto for ErgoDox on a (german) Mac

As we speak about beginning. I did not find a good howto, how to start with the ErgoDox-EZ on the Mac, especially with a mapping the keys and such, creating a custom firmware. There is an english wiki being created right now

here. No real how to or similar. But there are actually not many steps necessary to alter an existing layout, compile a new firmware and finally upload it to the ErgoDox-EZ (sometimes called "flashing" the device). But before we get to that, let's just explain some terms you'll read all the time when looking for information about the ErgoDox.

ErgoDox vs ErgoDox-EZ

The ErgoDox keyboard is already available quite some time now and could be ordered at Unfortunately, it was necessary to build the opensource keyboard yourself. That means, you'd get a lot of parts, you need to put together, soldering them , build a case, etc... And this is not working for everybody, as some of us do not have the time for such a DIY-project, or simply lack the knowledge and craftsmanship. And: if a little mistake happens, you end up with a really beatuiful, but not working keyboard. This is where Erez Zukerman comes in - his indiegogo project addresses exactly that by creating a real product out of an opensource DIY-keyboard. A product, you can buy, like any other product, including warranty and support. But still: everything still is opensource, including the things that are built right now especially for the ErgoDox EZ (like custom firmware)


At the first version of the ErgoDox (not EZ!) could be bought. As mentioned above, this was just a bag full of parts, you needed to do all the soldering and building it up from scratch. But at massdrop you get a configurator which is capable of creating .hex files directly and visually. You can create your layout there and end up with a file you can directly flash on your ErgoDox. There are some issues when it comes to non-standard keycodes, though. So I did not find a way to do the

long type or other special functionalities there. That's why I took the manual approach. If you only need a simple layout, without fancy stuff, the configurator on massdrop might be the easiest way to create a working .hex-file.


This actually is the hardware the ErgoDox (and the ErgoDox-EZ) is built upon. This is not very important, only if you wanted to build an own custom firmware from another code base. You also need to upload the firmware to the ErgoDox, if you want to change the layout. On a mac you can use the tool

teensy loader, which is named after the hardware. This tool takes some .hex-files and uploads it to your ErgoDox. You can download your copy here.

QMK Firmware

This is the standard firmware for the ErgoDox-EZ. You can guess by the way I'm saying that, that there are probably some other alternatives out there. And on github you can find some of those. I did not dive into that topic yet, I'll stick to the "original" for now.


As already mentioned above, the firmware for the ErgoDox-EZ (or more precise for the Teensy Microcontroller) es stored in .hex-files after compiling. Only those files are needed. When you compile, you end up with a whole bunch of new files (like .sym, .obj and alike) which are not really necessary. You only need the .hex file.

How to install a new firmware

This is rather simple if you already have a proper firmware file in .hex-format. Some examples of those can be downloaded from the official repository here. This is the firmware project repository for the QMK-Firmware - there is a subdirectory ÂŽkeyboard/ergodox-ez/keymapsÂŽ where you can find some of those .hex-files. My version of the layout can be downloaded here. To install this file, you only need to follow these easy steps: 1. Download the .hex file (if you compile it yourself, you end up with such a file also) 2. Open the App Teensy Loader (see above - Teensy). Then take a paperclip and klick the button on the keyboard on the upper right (there is a little hole in the case). This brings your ErgoDox EZ into programming mode. 3. Open the .hex file (first icon from the left - looks like a document icon) 4. To upload (aka flash) the firmware file to your keyboard, click on the 2nd button from the left ("rounded" Arrow). You'll see a progress bar during the upload process. 5. now klick on the reboot button (small arrow, 3rd icon from the left) After that, your new firmware is installed and used. You should see your changes now. I experienced some kind of "failures" after the reboot, like, the keyboard was stuck in a certain mode, the left half of the keyboard would not react... but I could fix it by just unplugging it and replugging it after a couple of seconds. I flashed the ErgoDox-EZ now about a dozen times, and in maybe a 3rd of those cases, an error like described happened. All could be fixed in no-time. So, don't panic!

howto create your own firmware

To do this, you need to do some preparations. As already mentioned I only consider MacOSX here - I did not try the ErgoDox on Linux or Windows. You should install If you have macports installed, you might end up with an error. We need to install a so called cross compiler. This is a compiler, that produces code not for the hardware it is currently running on, but something completely different. In our case this is the Teensy 2 microcontroller. If you use macports you'd have to find, how to install this crosscompiler. With ÂŽbrewÂŽ the installation is just a few lines: brew tap osx-cross/avr brew install avr-libc after that you need to checkout the project from github. Details you can find there, but this is the command, you need (creates a folder in current directory):

git clone
 now go to the directory 

qmk_firmware/keyboards/ergodox_ez. for testing, you should run make there, this will create the default layout .hex file in this directory. The file is called ergodox_ez.hex. If you end up with an error message, take a close look. Probably you only need to install some tools or something. If you want to create a different than the default layout, you need to store the name of your layout into some environment Variable: export KEYMAP=osx_de if you run make now, this layout will be created. If the corresponding C-File exists in the directory

keymaps (here the filename is keymap_osx_de.c. You can easily change an existing C-File, create a completely new one (not recommended), or copy an existing C-File and alter it to your liking. You only need to change the environment variable accordingly. If you need additional information about what possibilities you have with this C-Files and what is possible, have a close look at the project documentation. I really hope, this little howto is helpful for you and your new ErgoDox-EZ!

Features of the ErgoDox-EZ - layout programming details

As you now know, how to compile and upload a new firmware, let's have a look at the features, you might use in those firmwares. I call the process of defining the layout for your keyboard in C-Files "layout programming" - it is not real programming, although there a datascructures involved, some C-experience is surely beneficial. But it is not real programming... you usually do not need to do loops, if-then-else or something. But you need to know some things.


First, every key can be programmed so send any keycode a keyboard might have (and actually mouse also). So, it would be possible, to change the position of keys completely (e.g. DVORAK, NEO or ADNW layouts. All alternatives to the existing QWERTY/Z layout). You could also create a special layout for a special purpose. Like a special software, where you actually do not type a lot, but really use hotkeys and shortcuts. (like in a game or other special purpose software, CAD, PhotoEditing... whatever you use). In the QMK-Firmware, every of those layouts needs a corresponding C-File (see above). In this C-File there is the layout defined as an array of 64bit integer values, every

place in this array determines the key, the value of this determines the keycode that is going to be send from this key when pressed (or released...). Imagine the keys are numbered from the top left, to the bottom right, each half of the keyboard separately. So in my layout, the first keycode in this array defining it is the ESC-Key. The name for that in the C-File is KC_ESC. All "raw" keycodes have the prefix KC_, there are international definitions of keycodes also with their corresponding prefix for the country (like, DE_), but in my case, those keycodes were meant for Windows, not OSX. But that is no big deal, just think about what you would type.


You can have several of those layouts defined in the c-file. Actually, the data structure is an array of arrays, the latter ones defining a layout each. So, when you switch between layout, you can completely redefine the whole keys (with one exception - the key you use for switching between layers, see below) There is one keycode defined, called KC_TRNS, which actually is no real keycode but telling the firmware, "if this key is pressed, use the keycode from the layer below the current one". This does not work with the first (base) layout in your configuration, because we need to have something defined to fall back on. So, when you start up the keyboard, you start with that layer 0, the base layer. When you hit one of those layer switches, you switch to a different layer, lets say layer 3. That means, layer 3 is on top of layer 0. If you have any keys defined as KC_TRNS in layer 3, pressing one of them when switched to that layer, acutally issues the keycode from layer 0. And to make things a bit more complicated: you can actually stack those layers. You could define a layer switch with one key, pressing anotherone will add a layer to that stack. KC_TRNS will then fallback to the layer below in the current stack. This feature could be used, if you need a similar behaviour like with ALT and SHIFT. Think about it: when you Press shift, the keys switch all to upper case, when you press alt, some special characters occur. But when you hit both, the layout changes again, at least for some keys. Acutally, this stacking of layouts is pretty standard. We just were not aware of it... With that you could create your own more or less simple layout, without any layers or any fancy features like long type or something. This is - at least as I understood it - what you can get from the massdrop configurator.

Special keypresses

But there are features, you might enjoy...

  • you can not only send a simple keycode, but also one in combination with a modifier (like shift, alt, cmd, ctrl... and so on). This can be done easily by adding for example LSFT to your keycode, LSFT(KC_7) would send a shift 7 keycode - usually the /. In this case it is actually pressing the left shift for doing that, but that usually does not make much of a difference.
  • you can make a key not sending a real keycode but making a switch to a different layer. in the DE-Layout this is actually done with the "Tab"-key, just switches to and out of the cursor layer. Please keep in mind: your layer-switch key, should always be defined to have the keycode KC_TRNS in the target layer, otherwise you might not be able to switch back. Toggling a layer on and of is done with the function TG(), as parameter you give the number of the layer you want to toggle, like TG(3) which would switch to your layout on index 3 (always starting at 0 (baselayout), this is the 4th layer!).
  • you have the option to define keys to behave differently when pressed long or just typed quickly. This is useful for modifiers. You can have the hyper key issued when pressed long, but when typed it sends a normal keycode. There are actually several ways of achieving this behaviour. First you can use the method LT() where in the brackets you add two arguments. First the layer it shoul switch to, when pressed long, the 2nd one is the keycode to be issued when typed. The other way is to use functions with the suffix _T, like CTL_T(). This one means, issue the keycode for control when pressed and held, but send the keycode given as argument, when typed. In my layout definition this is used for the Y and Minus-key to be also used as CTRL. Which comes in quite handy some times. with that you can define quite some layout - take a look at the baselayout for the osx_de version:

    //Base layer KEYMAP(

        KC_ESC,                  DE_1,         DE_2,   DE_3,   DE_4,   DE_5,   DE_6,
        KC_TAB,                  DE_Q,         DE_W,   DE_E,   DE_R,   DE_T,   KC_LGUI,
        KC_LALT,                   DE_A,         DE_S,   DE_D,   DE_F,   DE_G,
        KC_LSFT,                 CTL_T(DE_Y),  DE_X,   DE_C,   DE_V,   DE_B,   KC_LALT,
                                                                        M(M_MEH_SH_ACUT),       TG(2),
                                                                        KC_BSPC,KC_DEL,         LT(SMLY,KC_END),
        // right hand
             M(M_CTRL_CMDC),  DE_7,   DE_8,   DE_9,   DE_0,   DE_SS,            DE_HASH,
             KC_RGUI,     DE_Z,   DE_U,   DE_I,   DE_O,   DE_P,                 DE_UE,
                          DE_H,   DE_J,   DE_K,   DE_L,   DE_OE,                ALT_T(DE_AE),
             KC_RALT,     DE_N,   DE_M,   DE_COMM,DE_DOT, CTL_T(DE_MINS),       KC_RSFT,
                                  KC_LEFT,  KC_UP,KC_DOWN,KC_RIGHT,        LT(SYMB,DE_PLUS),
             TG(4),       ALL_T(DE_ACUT),
             KC_PGDN,KC_ENT, KC_SPC

One additional thing you should consider. When you have more than let's say two layers, it would be very useful to show the user, which layout is currently active. This is best done using the 3 different LEDs on the keyboard. To define that, you need to have a look at the method

matrix_scan_user. There you can do something depending on the currently active layer. In the case of the osx_de-layout, it looks like this:

void * matrix_scan_user(void) {

  uint8_t layer = biton32(layer_state);

  switch (layer) {
    // TODO: Make this relevant to the ErgoDox EZ.
    case 1:
    case 2:
    case 3:
    case 4:
        // none


I think this is more or less self explaining. The every case statement defines what to do for each layer. So for layer 0 (not listed here) all LED will be off. For layer 1, the led 1 will be on (the red one)... and so on. This function is called periodocally in a loop, so there you could add any other custom code, if you liked. These are the major features, I needed to implement my layout. There are more features, that might be useful (like stacked layers), but for now things work fine. I will work on improvements, if you have any suggestions, just leave me a note...

ErgoDox-EZ - Should you buy it?

Actually, that is a tough question. I think, it was worth it. But I use the keyboard only a couple of days now. I was quite fond of my "Razer Blackwidow" also and that changed over time. In this very moment when I'm typing this text I can only say, it feels very worthy, the switches feel like Cherry (but they aren't), the feedback is good as expected from a mechanical keyboard. Of course these switches do make som noise, you do not only get tactile feedback, but also audible one - I like that noise, but this is maybe not everybodys way of working. I installed dampener rings on the keys in order to reduce the sound wen typing through. But I actually like this "noise" a lot and it motivates me. But that is my personal opinion. And I ordered the ErgoDox-EZ with that Switches that are comparable with the Cherry blue ones, but there are different options. For me the ErgoDox-EZ is very close to the perfect keyboard. There are some things that might be missing (LED backlighting maybe). But I really like it. Right now, I like typing with the ErgoDox-EZ, it also helps me to go easy on my elbows and wrists, which are somewhat aching after a long day. This was one major reason in getting an ergonomic keyboard. I will maybe also create a ADNW-Layout (neo2 based layout, optimized for German and English typing), but that is a very different thing....

Update after one week: Still like typing a lot with the ErgoDox. Especially as i got my custom layout up and running. It makes things a lot more smooth. Typing is a breeze... Also, I have to say, the support from Erez and his team is great! Thanks again. I am really astonished, how quickly I could adjust to the new keyboard. After just a couple of days, it really felt awkward typing on a normal keyboard again. This actually is a good sign!

update after some weeks of use

I got used to the ErgoDox quite fast. Really still like typing on it. And I learned some things about my own layout: having space on both sides of the keyboard is actually not that great. I miss having the delete key easily accessible. So... I removed the space key on the left side of the keyboard and replaced it with backspace, putting the current backspace to be a DEL-key. This seems to work ok... And: I really was not using the CTRL-keys on the upper row. Used the keys on both pinky fingers for CTRL. That works better actually. I put CMD-C / CMD-V there... at least for now. Maybe I'll experiment with macros there... Did not come up with a better solution for that... Also still looking for something useful to put on the Caps-Lock-Key... right now its only a mode / layer switch. Did not come up with something fancy for that yet.  

Annother update - one month in to 2016

I really like typing on the ErgoDox EZ, it feels great, I'm quite fast and my layout seems to be working fine now for me. Although I needed to add some additional features:

Smiley Macro Layer

I thought I need to play a bit with macros and wanted to put some things I often type there. So I decided to create a smiley layer. This is available in the currently merged version of the firmware. When pressing the lowest, rightest key on the left halfs keyboard thumb block you temporarily enter this layer and can type smileys with the right hand side! Works like charm! 😉 :-D EgoShooter Layer The default layout I have created is optimal for typing (at least for me) - but it did not work at all for EgoShooters like Counterstrike global offensive or alike. I had to create an additional layer. But I did not want to waste a key just for switching to this layer, and - obviously - did not want to have a key pressed all the time in order to be "temporarily" in that layer. I wanted to switch from one layer to this new layer and only there... Right now, when enter the symbol / coder layer you can switch to the ego shooter layer by typing the top left key on the right keyboard half. Then all 3 LEDs will be on indicating that you are ready to go for some serious ego shooting ;-) The changes are more or less minimal: * left side backspace becomes space * left side delete becomes control * left side < / symbol layer switch becomes Ctrl * the outer thumb keys on the left side become F1-F4 maybe there will be some additional changes to this, but right now, it seems to work quite good. Happy fraggin'

** Another Month - another update **

Still love typing on the ergodox, but I start feeling uncomfortable writing on a "normal" keyboard. I had to install the "reinforcement kit" last week, as I got one of the ErgoDox-EZ' with a slight fault (look here)

For some reason, I did not like having the numbers on the right side starting with 6, I wanted them to start with 7. So I changed the layout to reflect that. That works fine for me and has some advantages:

  • I could put the # to the top right key
  • I could put the F12 there as well
  • the 6 is now on the left side, top rightmost key. This was CMD-V before. Missing that to some extend. I'll have to have a look for that.

as some time went by, here is a new update again

I played with the layout a bit again. I did not like the asymmetric shape of the numbers, and it did not really work well. I changed a lot of things today:

  • moving cursor key layout back to the "deafult" ergodox
  • adding ISO-Cursor keys to the symbol layer
  • adding a CTRL-SHIFT key on the rightmost, topmost key on the left half
  • needed to move the # somewhere useful. Put it on the topleft key on the right half
  • some fixes, especially adding a , to the number pad. This caused problems with typing some numbers already

maybe this is the best layout for my case. I was astonished how hard it is to get rid of the "used" positions of keys. And I actually do not like to move things to totally different locations - this would mean I cannot type on an usual keyboard anymore fluently. And this is not working with carrying the macbook from meeting to meeting.

really like playing with the programming of the ergodox! this is fun. And it will improve the layout over time. Still need to find some way to build these layout pictures somewhat more easily - right now is's pain!

** Update on documentation **

The layout went through some iterations till today and for now it seems to be ok. Go check it out at github. There is also a new Project I created that (for now) helps me createing a png of the layout so that you get a better overview. Later this might be used to create layouts as well.

Check the post here and the github page here

the current layout looks like this:

category: Apple --> Computer

Have to dump my favorite Mail Client due to Exchange

2015-03-25 - Tags:

sorry, no english version available

category: Apple --> Computer

Opinion: iOS or Android or Apple vs. the World

2014-09-17 - Tags:

sorry, no english version available

category: Computer

OSX 10.10 Yosemite & iOS 8 - erste Erfahrungen

2014-08-13 - Tags:

no english version available yet.

NatĂŒrlich musste ich mir auch ios8 installieren, wo ich doch schon mit Yosemite ganz gut fahre. Wobei so langsam einige kleinere Bugs auftauchen. In meinem letzten Post zu dem Thema habe ich ja schon einige Bugs erwĂ€hnt, es kommen aber noch einige dazu, insbesondere in den Einstellungen stimmt die Ansicht nicht immer mit den wirklichen eingestellten Werten ĂŒberein.

Continuity und HandOff

Was allerdings wirklich nervig ist, ich schaffe es nicht meinen iMac mit meinem hier im BĂŒro erstellten Wlan einzuhĂ€ngen. Er geht nur ĂŒber Kabel ins Netz. Das ist auch der Grund, warum Continuity und Handoff hier nicht funktioniert, denn dazu mĂŒssen die GerĂ€te ja im selben WLan sein – IP-Netz reicht offensichtlich nicht aus.

Hier ist es so, dass alle GerĂ€te, egal ob ĂŒber Kabel oder Wlan angeschlosen im selben Subnetz sind. Anpingen der GerĂ€te untereinander funktioniert, allerdings weigert sich der iMac seit Yosemite standhaft, sich ins Wlan einzubuchen.Roblox Hack Free Robux

wobei das nicht ganz stimmt, er bucht sich ein, bekommt aber keine IP-Adresse. Auch wenn ich die manuell vergebe, funktioniert kein Datentransfer, nicht mal Ping funktioniert – da stimmt wohl was mit der VerschlĂŒsselung nicht

Ein test mit einem Apple AirPort Extreme hat dagegen reibungslos funktioniert. Klar, dass die neue Software erst mal mit der Hardware aus dem eigenen Hause getestet wird. Und auch klar, es ist Beta Software. Und da MUSS es ja noch Bugs geben
 Insofern alles ok.

Neues Feature: Markup

Ein Feature, dass ich im letzten Post unterschlagen habe ist die neue Markup Funktion in Mail. Wenn man ein Attachment in eine Mail hinzufĂŒgt, kann man (je nach Dateityp), Markierungen in der Datei machen (wenn es sinn macht – bei Audio-Dateien geht das nicht. Bei PDF, PNG’s etc sehr wohl).

Wenn man das oben gezeigte MenĂŒ aufklappt und dort auf „Markierungen“ geht, kann man in der Datei (hier ein Screenshot) „rummalen“
 allerdings funtkioniert das etwas besser als â€žĂŒblich“. Normalerweise sehen mit der Maus gezeichnete Markierungen meist aus wie das Gekritzel eines 3-JĂ€hrigen. Hier jedoch werden die eingegebenen Formen erkannt. Apple Mail macht da auch einen recht guten Job mit der erkennung. Meine „Kreise“ sehen mit der Maus gezeichnet wirklcih eher krakelig aus, aber Mail erkennt den Kreis. Auch Dreiecke und Vierecke funktioineren ganz gut.

Macht man eine Linie und am „Ziel“ einen Spitzen Winkel erhĂ€lt man einen Pfeil – meist etwas gebogen. Aber nachbearbeiten kann man ja auch immer noch.

Des Weiteren kann man auch seine Unterschrift (Ă€hnlich wie das in Mavericks bei geht) einfĂŒgen oder Formen oder Text.

Bei der erstellung der Screenshots fĂŒr diesen Post ist mir genau diese Funktion allerdings mehrmals abgeschmiert. LĂ€uft also noch nicht ganz Rund das mit dem markup. Aber die Idee ist super!


Das Update hat auf den ersten Blick recht wenig neues gebracht (fotos dazu gibt’s ja zur GenĂŒge). Klar, die neue Tastatur bemerkt man recht schnell. Aber sonst sind sich iOS7 und 8 sehr Ă€hnlich. Man kann nicht auf den ersten Blick einen Unterschied ausmachen. Erst die Details machen es.

Stabil scheint Die iOS8 Beta 5 auch zu sein – zumindest auf meinem iPad funktioniert (fast) alles reibungslos. Ein paar Kleinigkeiten klemmen schon noch, wie z.B. dass die Multitasking-Bedienung nicht immer funktioniert oder das einige Apps nicht wirklich kompatibel sind. Aber das wird sich sicher noch Ă€ndern.

Da einzige, was wirklich auffĂ€llt, ist die neue „Tipps“-App. Da werden einem ein paar Hilfestellungen fĂŒr den Umgang mit iOS8 gegeben. Die spotlight-Suche wurde auch verbessert und macht was her

die Erinnerungen-App ist jetzt etwas „Bunter“ aber vom Funktionsumfang her nicht wirklich „gewachsen“.

Neu ist natĂŒrlich auch die Möglichkeit, per iMessage Sprachnachrichten zu verschicken, DafĂŒr gibt es neben dem Eingabefeld fĂŒr den zu sendenden Text ein kleines Mikro. Tippt man da drauf, kann man eine Nachricht aufnehmen und dann versenden. Wirklich praktisch, wenn man grad nicht so viel tippen kann.

Siri soll angeblich auch leistungsfÀhiger geworden sein, aber das kann ich im Moment nicht bestÀtigen. Die Erkennungsrate ist bei mir genauso gut oder schlecht wie vorher und so wirklich eine Neuerung in dem Normalen Umgang habe ich jetzt nicht gesehen. aber das kann ja noch kommen.

Sonst ist iOS8 auch recht gut geglĂŒckt, die StabilitĂ€t ist fĂŒr ein StĂŒck Beta-Software wirklich ganz ok.

category: MacOS / OSC --> Computer

Mail App und Google Mail

2014-07-24 - Tags:

sorry, no english version available

category: Computer

Update zum "Frust bei 1und1"-Post

2014-06-27 - Tags:

sorry, no english version available

category: global

Neuer Bug in IOS - Keylogging möglich

2014-02-26 - Tags:

sorry, no english version available

category: Apple --> Computer

Riesen SSL-Bug in OSX - alles total unsicher und gefÀhrlich

2014-02-25 - Tags: ios osx security

sorry, no english version available

category: Service in Germany

ServicewĂŒste Deutschland: Amazon

2013-11-22 - Tags:

sorry, no english version available

category: Computer

using Qnap as GIT-Server - SSH Problems

2013-11-06 - Tags: git qnap

originally posted on:

Linux really rules, especially if you consider the possibilities you get, adding functionalities to linux based gadgets or fix / add missing functionalities.

The latter one is something that also can be said about the Qnap storage system. I use git for my own little software projects. This is cool as a version control system and easy to use - better than SVN or CVS.

So I have my repositories on a share on my qnap. You can mount the share and use git to synchronize stuff, that works fine so fare. But causes problems, when working remotely where you do not want to mount the share in order to be able to push things.

Luckily you can install additional tools on the qnap, git is one of them. And it works fine out of the box, you can use ssh to access git and the repositories.

Unfortunately is the sshd that comes with the qnap somewhat works strange, you can alter the /etc/sshd to what you want, it won't be possible to log in as something else than admin.

I do not want to open some root login to this qnap, no way. So I digged a bit deeper and found out, that the sshd is altered to only allow logins as admin.

But I am root on this machine, so lets hack.

  1. install openssh via the Optware installation frontend. unfortunately this alone does not work, as the installation is not replacing the existing one. So we need to go further
  2. rename original in /usr/sbin: mv sshd sshd.qnap
  3. create link: ln -s /opt/sbin/sshd
  4. alter your sshd_config to your needs
  5. restart sshd (either via the GUI by disabling and re-enabling remote login or via kill the SSHD - Attention, this might and often will kick you out)

ok, now you should be able to log in as someone else than admin.

now you only need to create your repositories to your liking. I created one special share for it (which can also be mounted).

in my case it would be something like: git clone user@qnap:/share/development/git/repo

if you think this might be a security risk, you could set the login shell for that user to git-shell to avoid direkt access of this user.

Happy Hacking

found results: 154

<< 1 ... 2 ... 3 ... 4 ... 5 ... 6 ... >>