Edit Artist, Album or other fields of multiply music files at once

Software EasyTAG needed.

Select all files you want to edit, enter (for instance) the Artist info you want in the Artist field, then click the little square to the right of the field and whatever info you have entered will be copied to that field in ALL files that you have selected. Repeat for the remaining fields.

Using Sshuttle in Daily Work

Source: http://teohm.com/blog/2012/04/01/using-sshuttle-in-daily-work/

I was first introduced to sshuttle by Sooyoung (@5ooyoung) in Favorite Medium as a workaround to The Great Firewall in China.

Since then, it has become my light-weight network tunneling tool in daily work.

Install sshuttle

The installation is easy now. You can install it through Mac OSX Homebrew, or Ubuntu apt-get.

I use sshuttle to..

1. Tunnel all traffic

This is the first command I learned. It forwards all TCP traffic and DNS requests to a remote SSH server.

Just like ssh, you can use any server specified in ~/.ssh/config. The -v flag means verbose mode.

Besides TCP and DNS, currently sshuttle does not forward other requests such as UDP, ICMP ping etc.

2. Tunnel all traffic, but exclude some

You can exclude certain TCP traffic using -x option.

3. Tunnel only certain traffic

To tunnel only certain TCP traffic, specify the IP addresses or IP ranges that need tunneling.

This command comes in handy, whenever I need to test an app feature (e.g. Netflix movie streaming) which only available in certain countries, or to bypass ISP faulty caches.

4. VPN to office network

I seldom do VPN, but all you need is the remote SSH server with -NH flags turned on.

-N flag tells sshuttle to figure out by itself the IP subnets to forward, and -H flag to scan for hostnames within remote subnets and store them temporarily in /etc/hosts.

IP addresses.. troublesome?

Well, I try not to deal with IP addresses manually. So I wrote a few sshuttle helpers (tnl, tnlbut, tnlonly, vpnto) that allow me to use domain names instead of IP addresses:

Tunnel all traffic

Tunnel all traffic, but exclude some

Tunnel only certain traffic

VPN to office network

The script is available on my GitHub repo. You can load it into your ~/.bashrc. To override the default tunneling SSH server in the script:

Preventing Brute Force SSH Attacks

Many VPS customers are surprised at the number of failed SSH login attempts to their servers. By just having a listening server on the Internet, you will get dozens or even hundreds of brute force login attempts each day. Most of these attempts come from automated scripts running on other compromised machines. If you are tired of reading through the failed attempts in the logs, there are a number of things that you can to do block the attempts, or otherwise make them unsuccessful.

1- If you will always be connecting to your server from the same IP address, you can firewall off port 22 to everything EXCEPT your own IP address.

iptables -A INPUT -p tcp -d 0/0 -s YOUR.IP.GOES.HERE –dport 22 -j ACCEPT
iptables -A INPUT -p tcp -d 0/0 –dport 22 -j DROP

Then run ‚iptables-save‘

Note: if you setup IP tables this way then it may cause you to lose ssh access to your server if your IP ever changes. And it can also make access to your server by RimuHosting staff more difficult.  It will also obviously prevent you from connecting to your server except from that one source IP.

2- Run sshd on a non-standard port. Since most automated attacks only attempt to connect on port 22, this can be an effective way to hide from automated attackers. To configure this, just change the Port line in /etc/ssh/sshd_config and restart ssh

Port 1022

3- Use the AllowUsers directive in the ssh configuration to only allow certain users or IP’s. In /etc/ssh/sshd_config, you can specify a list of allowed users like this:

AllowUsers bob john root@ root@

This will allow users ‚bob‘ and ‚john‘ to log in from anywhere, and root is only allowed to log in from those two IP addresses.

4- Use strong passwords! Brute force attempts will try common passwords like words (or combinations of words) in a dictionary, names, and common passwords. Strong passwords generally use a combination of upper and lower-case characters, numbers, and non-alphanumeric characters.

5- Even better, don’t use passwords at all. Instead, install your public key on the server and use it to log in. If all of your users will use public keys, you can set PasswordAuthentication to ’no‘. To disable password authentication just for root, use ‚PermitRootLogin without-password‘. For Debian/Ubuntu, you’ll also need to turn off ‚UsePam‘ and ‚ChallengeResponseAuthentication‘.

6- If you need to permit logins from arbitrary addresses, consider using a program like DenyHosts or Fail2ban. They watch for failed logins and add the IP addresses of attackers to /etc/hosts.deny and/or update firewall rules to null route them. DenyHosts can also be configured to synchronize with a global database so you can proactively deny hosts that other users have blacklisted.  Keep in mind that mistyping your password when you try to log in will then probably lock you out of your VPS.

7- Use ‚hashlimit‘ in ‚iptables‘:

iptables -I INPUT -m hashlimit -m tcp -p tcp –dport 22 –hashlimit 1/min
–hashlimit-mode srcip –hashlimit-name ssh -m state –state NEW -j ACCEPT

This rule limits one connection to the SSH port from one IP address per minute.

For more information, ‚man iptables‘ and ‚iptables -m hashlimit –help‘.

8 – Use port knocking to completely hide the port your SSH server is listening too; example.  This will of course make it pretty complicated for you to log in.

If you manage to lock yourself out, you can always log in using your root password via the Console over SSH feature.

Source: https://rimuhosting.com/knowledgebase/linux/misc/preventing-brute-force-ssh-attacks

Owncloud installation on debian 8

Install owncloud via the owncloud repository.


Debian_8.0 owncloud-8.2.2-1.1

You can add the repository key to apt. Keep in mind that the owner of the key may distribute updates, packages and repositories that your system will trust (more information). RUN:

Run the following shell commands as root to add the repository and install from there.

After this you have to create a database user with a password and a database for owncloud.

Now you can visit http://yourdomain.com/owncloud/

There you fill in all data and finish the installation.

When you are logged in you see that owncloud recommends you to enabling caching:

Also TLS should be installed:

Therefore I followed the instructions of http://workshop.tecchannel.de/a/owncloud-8-2-unter-ubuntu-server-14-04-lts-installieren,3277676,7#s9



For Update notification you can use apticron


  • https://www.howtoforge.com/tutorial/owncloud-install-debian-8-jessie/
  • https://doc.owncloud.org/server/8.2/admin_manual/installation/source_installation.html
  • https://www.techandme.se/how-to-configure-redis-cache-in-ubuntu-14-04-with-owncloud/
  • http://workshop.tecchannel.de/a/owncloud-8-2-unter-ubuntu-server-14-04-lts-installieren,3277676,7#s9
  • http://www.rojtberg.net/687/secure-owncloud-setup/

Installation bbcp

Attention: bbcp traffic is not encrypted!

bbcp must be installed on both ends


Veröffentlicht unter Linux

Install Visual Code Grepper on Ubuntu 14.04×64

VisualCodeGrepper needs the .net 4 Framework  installed. The following steps are necessary to get VisualCodeGrepper working with wine on ubuntu 14.04.


Java – Call a shell script and wait until it’s end


Send Strg + C on Eclipse in Linux

I wasn’t able to send strg + c in the console. So I found the following command which must be executed from a shell.


HowTo – Installation of 3proxy 0.8.6, a tiny free proxy server on Debian 8

In this tutorial I’m going install and configure 3proxy on Debian 7×86. It is a really fast and lightweight alternative to Squid Proxy. My whole system with running 3proxy needs only 15 MB RAM. I will configure a HTTP Proxy and chroot him to increase security. Users for the Proxy are stored in the /usr/local/etc/3proxy/passwd file. At the end of the article I will add an user.

# Install Dependencies

# Download, compile and move 3proxy to wanted directory
# 3proxy will be chrooted to the directory /usr/local/etc/3proxy for security reasons

# Setting the file permissions.
# Only the log folder and the pid file should be rightable by 65535

# Save the following config in /usr/local/etc/3proxy/3proxy.cfg

# Generate an init script for automatic startup 3proxy after reboot

Content of the file /etc/init.d/3proxyinit

# Make the file executable

# Manual stop and start 3proxy

# Tell iptables, the internal firewall to forward packets arriving at Port 443 to 3128 (Port 3proxy ist listening)

# Install programm to make iptable Rules persistent (even after reboot)

######Add a user to the /usr/local/etc/3proxy/passwd file