Source: Ubuntu manuals
raring (1) par2.1.gz
Provided by: par2_0.4-11build1_i386 
NAME
par2 – PAR 2.0 compatible file verification and repair tool.
SYNOPSIS
par2 c(reate) [options] <par2 file> [files]
par2 v(erify) [options] <par2 file> [files]
par2 r(epair) [options] <par2 file> [files]
Or:
par2create [options] <par2 file> [files]
par2verify [options] <par2 file> [files]
par2repair [options] <par2 file> [files]
DESCRIPTION
par2 is a program for creating and using PAR2 files to detect damage in
data files and repair them if necessary. It can be used with any kind
of file. Lire la suite…
Nemo is a file manager application developed by Linux Mint team. It is a fork of Nautilus, the GNOME’s file manager. In the beginning, Nemo was just Nautilus 3.4 (Nautilus version which is forked to become Nemo) with different name.
With rapid development and improvement, Nemo now become a full-featured file manager with lots of features, more customizable, and looks beter (in my opinion) than its original (Nautilus).
Nemo is the default file manager in Linux Mint, to handle folder and also handle the desktop. You can also easily install Nemo in Ubuntu if you want which is just apt-get away using a PPA (read more: How to install Nemo in Ubuntu),
When you install Nemo in Ubuntu, it doesn’t set itself as the default file manager, Nautilus remains as the default one. If you want to integrate Nemo into Ubuntu system (as the default folder handler), you have to do it manually.
Here I want to share simple command to set Nemo as the default file manager in Ubuntu.
We will invoke the xdg-mime command from freedesktop.org, which is standard command and installed by default in most Linux distribution including Ubuntu. It can be use to set an application (*.desktop file) as the default file opening a certain file type(s) (mime-type). You can also use it to find out what application on your system to handle type(s) of file. Lire la suite…
source: http://www.the-art-of-web.com/system/fail2ban/
Around the beginning of 2005 we saw an increase in brute-force ssh attacks – people or robots trying different combinations of username and password to log into remote servers. A quick search on this topic returns many references to iptables and ipchains but noone really explained how they work.
Having just gone through this learning curve myself, and found a satisfactory solution in the fail2ban package, I’m going to try and explain how to achieve the simple goal of banning IP addresses that make repeated failed ssh login attempts.
If you want more technical information regarding firewalls and iptables in particular, see the References section at the bottom of this page. Lire la suite…
