Direkt zum Hauptbereich

Posts

Messer selber machen

Bevor hier jemand meckert oder zu gleichgültig an die Sache herangeht: Messer machen ist eine Kunst, die sehr viel Wissen und Erfahrung beinhaltet. Ein Resultat dieser Kunst ist die Weisheit, dass man Messer nur auf Wasser- oder Ölsteinen schärfen sollte. Warum? Der Messerstahl darf nicht zu heiss werden, da er dann wieder weich wird und beim Schneiden schnell an Schärfe verliert. Daher ist es ratsam sich helfen zu lassen, denn ansonsten bezahlt man viel Geld für Ofen, Hammer, Amboss, Schleifgeräte usw. und endet dennoch mit Müll. Schmieden wollte ich schon seit längerem, aber der Materialaufwand ist mir zu hoch. Aber letztens ersteigerte ich mir zwei 100 Jahre alte Kochmesserrohlinge von Sabatier (aus den USA!), für die ich Griffe bauen muss. Nachdem ich diese Hürde genommen habe, werde ich irgendwann folgendes versuchen: Stahl kaufen: Schwedenstahl bei Dictum (rostender Stahl wird schärfer, und ist leicht schärfbar) Messer bearbeiten, wobei Hitzeeinwirkung keine Rolle ...

Stream your media to your DLNA device e.g. tv with miniDLNA on a linux machine

Recently we bought a Sony Bravia LED TV with the possibility to receive streams. It can read DLNA, which is not much, so dont fall for the certificate. DLNA means it can read MPEG-I/II and some other normal stuff. Luckily the Sony Bravia can read mkv and x256 and some other codecs. And this is something the sells people and adverbs dont tell you, so be warned not to trust the DLNA-Certificate too much, the device has to decode the media in the end. Anyway i set up miniDLNA on my laptop and now I am able to stream my media to the television. Although the process did not go that well. The problem was miniDLNA was breaking down all the time. And checking it by reading the logs etc revealed permission issues. I had to start miniDLNA as the user my files belonged to. BUT I did not use the user setting in the minidlna.conf instead I just started the daemon as the user. I could have done this with a startup script, but there were some issues with the network being set up at the sam...

Ripping a CD on linux via the command line - which even works for "funny" CDs

Recently I installed a car radio with a USB slot, so I wanted to take some of my music to the car. Since I have about 500< CDs you see the need for storing them as mp3s I hope. And by law I am allowed to do so, but some companies make it difficult to do so. Normally I ripped with k3b, but the settings always disappear, and I switched to KAudioCreator (grip etc did not work), but even there its funny sometimes. These three commands will rip any CD: show CD content: sudo cdparanoia -vsQ  rip to the harddrive (mkdir first!): sudo cdparanoia -B convert to mp3: for f in *.wav; do lame --vbr-new -V 3  "$f" "${f%.wav}.mp3"; done now I used KTagEditor for processing the id3 tag manually But I will try the tool "ripit" for now, it looks promissing. PS: actually, you should use ripit (on linux) because it uses cdparanioa as well as lame with CDDB queries. One command, some YES to CDDB choices and the cd is ripped.

Almost perfect mail server: postfix - dovecot - postgresql -- with virtual mail boxes and SSL

Its a long time ago I had enough time to set up my mail server, so I will summarize my steps, or better: my problems: [on debian 7] install postfix install postfixadmin install postgresql make them work together as they all should use virtual users install dovecot and make it the default SSL handler for postfix, main.cf master.cf etc. Well, this is bull because its of no help to anyone, the devil resides in the details: postfixadmin sets up the database postfix should use queries for to look for mails in the database, so virtual_mailboxes etc have to be set up dovecot should be the MDA for the MTA postfix dovecot and postfixadmin should use a simple and same encryption, because both look into the database; is this step is done (and it took me a while, CRAM-MD5?) you can set up mailboxes via the web interface postfixadmin

Putting phpPgAdmin behind SSL virtualhost and securing it a bit more

This could be a huge post, but I am cutting it short: configure pg_hba.conf right, e.g. set host stuff to password md5 try to connect to your database locally to test it, e.g. psql -U user "psql -U user dbname -W" and type in the password install phppgadmin, e.g. on debian I could not find a /etc/phppgadmin/apache.conf but a /etc/apache2/conf.d/phppgadmin your apache2 should be able to serve SSL, otherwise look a my post from yesterday: SSL virtualhost after you setup a SSH connection through rsa keys and always redirect to it in order to serve multiple site using SSL you should change to *:443 instead of _default_ also you have to tell /etc/apache2/ports.conf to use NameVirtualhost when listening on 443; otherwise apache will tell you about conflicting virtualhosts. apache2: now its time to copy the content of conf.d/phppgadmin into a sites-available file and dont forget to delete the alias line and adjust names and folders. From now on I followed these steps: Step...

SSL virtualhost after you setup a SSH connection through rsa keys and always redirect to it

You may have done this: ssh-keygen and ssh-copy-id and now you want to enable SSL. With Eric Ambergs "Linux-Server" book and Converting keys between openssl and openssh , I did this so far: local: "scp MYKEY root@remote.server:~" after this its just remote: "a2enmod ssl" "mkdir /etc/apache2/ssl" "openssl req -x509 -days 365 -new -key MYKEY -out /etc/apache2/ssl/nedab.de.pem" and make sure you use a wildcard domain as common name, e.g. *.common.com. That way your certificate is valid for all subdomains.  "a2enmod redirect" virtualhost in /etc/apache/site-available with help from Redirect Request to SSL : <VirtualHost *:80> ServerName .......... Redirect permanent / https://........../ </VirtualHost> <VirtualHost _default_:443> SSLEngine on SSLCipherSuite HIGH:MEDIUM SSLCertificateFile /etc/apache2/ssl/........pem SSLCertificateKeyFile /etc/apache...

iptables - setting up a decent firewall

Here is nothing else to write about but the source code you put into /etc/init.d/firewall as a 755 script, and a ". /etc/init.d/firewall" line in to /etc/rc.local". I adjusted some stuff reading through Eric Ambergs "Linux-Server" book. #!/bin/sh echo "Initialisiere Firewall iptables ..." # Firewallregeln löschen iptables -F iptables -X iptables -P INPUT DROP iptables -P OUTPUT DROP iptables -P FORWARD DROP iptables -Z # Module laden für FTP ports modprobe ip_conntrack_ftp #------------------------------------------------------------------------------ # # http://wiki.debianforum.de/Einfaches_Firewall-Script # # Logging options. LOG="LOG --log-level 4 --log-tcp-sequence --log-tcp-options" LOG="$LOG --log-ip-options" # Defaults for rate limiting RLIMIT="-m limit --limit 3/s --limit-burst 30" # Custom user-defined chains. # LOG pack...