AVM tries to convince you to use their MyFritz service or another dyndns provider to use the new Wireguard
VPN which the new Fritzbox software supports.

Since I have a static IP and my own domain pointed to it, I have one of the use cases where a dyndns should not
be required. Perform the following workaround to enable Wireguard:

Go to the Dyndns settings and activate the use the following settings:

Use DynDNS: checked
url: http://httpstat.us/200
domain: yourdomain
username: xyz
password: 123

The current version of lftp in the debian repository does not connect to an own sftp server,
using self genereted certificate. It simply hangs at the ls command (list directory) upon connection.

By starting it using: lftp -d you can see if this is the same problem on your side.

The reason is because on first connect, the server is not yet in the list of known hosts.
To circumvent this issue, there is a simple workaround:

Connect to the server via ssh, like:
ssh username@server.url -p portnumber

If you upload files to an owncloud server via FTP, SCP or some other tool, the owncloud server at first does not notice on its own, that new files are present.

You can however, trigger a manual refresh via the command line...
A php script from owncloud can be triggered as www-data (webserver) user:

Go to your owncloud folder:
cd /var/www/owncloud (just an example)

Change to the www-data user:
su -s /bin/bash www-data

Execute the php script:
php console.php files:scan --all

Recently, the glibc library had a bug that could
be exploited over the network using a DNS request.

This bug can be fixed on debian by updating the libc6 library:

apt-get update
apt-get install libc6

After the update, the computer should be restarted, since a lot of
services and libraries use the libc6.
It is also possible to restart all services, but missing one service
is easily possible, so better be on the safe side.

I have installed a new kernel on my root with the grsecurity and pax patches.
After installing the new kernel, grub is not working correctly any more.

It seems that pax conflicts with some programs of grub.

Thanks to the following article (https://dustri.org/b/grsec-and-grub.html), a solution was found:
Install the paxctl tool:
apt-get install paxctl

Call the tool with the following parameters:
paxctl -Cpms /usr/sbin/grub-mkdevicemap
paxctl -Cpms /usr/sbin/grub-probe
paxctl -Cpms /usr/bin/grub-mount

To block ads on the skype application (tested with 7.12 from 28.10.15) , you can
add the following lines to your host (file: %windir%\system32\drivers\etc\hosts) as administrator! rad.msn.com live.rads.msn.com ads1.msn.com g.msn.com a.ads2.msads.net b.ads2.msads.net ac3.msn.com

If you also add the following line, as stated in some tutorials: apps.skype.com

the skype home can not be loaded any more.

In case you just want to view the original content of the windows assembly folder, or other system folders, you can do the following:

1. In console, type cd /d %windows%\assembly
2. Type: attrib -r -h -s desktop.ini
3. Type: ren desktop.ini desktop.bak

Reload the explorer window to see the actual contents...

If you want to restore the original view, just rename the desktop.bak back to ini.

This works also for other system folders, e.g. fonts folder.

In case you want two seperate views at the same time, you can do:

This article shows you how to install Scrapy - a python web crawling toolbox, under debian/ubuntu or linux mint.

use apt-get with proxy:

http_proxy=http://domain\user:pass@hostname:port apt-get install packagename

or set the environment variable upfront

export http_proxy=http://domain\user:pass@hostname:port

Use pip with proxy:

pip install --proxy="http://domain\user:pass@hostname:port" packagename

Now step by step:

Bash shell has a serious vulnerability that can be exploited by
an remote attacker in some cases.

To check if you are using bash can be done with entering the following at the shell:
echo $0
echo $SHELL

If it prints bash, then you are using bash.

Debian Wheezy is using dash by default since version 6.10, so it should not be vulnerable.

If your version of bash is vulnerable can be tested by entering the following in bash:
env X='() { (a)=>\' bash -c "echo echo vuln"; [[ "$(cat echo)" == "vuln" ]] && echo "still vulnerable :("