pas mal ce petit outil

'faut que je fasse un tour d'horizon de mes linux pour corriger ce défaut
http://www.it-connect.fr/securiser-ledition-du-grub/

Un tool pas mal du tout pour cibler les problèmes d'exploit sur un site

hop, on se test redshift sous linux cet aprem :-)

perf record -p $pid <3

les snippets, c'est la clé du succès du fainéant :D

find . -type d -empty -exec rmdir {} \;

home | blog | popular | study | writing | projects | about | connect
Collection of Less Commonly Used UNIX Commands
September 11th, 2013 | Linux | System Administration | Technology

[ Check out my latest post on the HP Security Blog: “The Secure Web Series, Part 1: Securing The Password Reset Mechanism” ]

unixcommands

Over at Hacker News there are often threads about less-traveled UNIX commands. One particular comment collected a few of the posts, and I decided to parse all of those threads’ commands, plus my own favorite list of obscure entries, and put them in one place.
Somewhat obscure UNIX commands

column: create columns from text input
tr: translate/substitute/delete input
join: like a database join but for text
comm: file comparison like a db join
paste: put lines in a file next to each other
rs: reshape arrays
jot: generate data
expand: replace spaces and/or tabs
time: track time and resourcing
watch: execute something on a schedule in realtime
xargs: execute something on all inputs
iftop: visually show network traffic
jnettop a more detailed iftop
htop: show system stats more powerfully
xxd: manipulate files in hex
mtr: powerful traceroute replacement
mdfind: osx find replacement that uses spotlight
brew: osx package manager
df: disk free
du: disk usage
iotop: i/o stats
dig: dns queries
host: dns queries
man ascii: lookup your ascii
sshfs: mount a directory through ssh
wget: get w’s
dstat: powerful system statistics
tmux: a better screen
jq: command line JSON parsing
pushd: push your pwd to a stack
popd: pop pwd off your stack
lsof: godlike system information [*]
ncat: nmap-based replacement for nc
fuser: kills locking processes
vim: attack yourself
tac: cat in reverse
slurm: network interface stats
rename: change spaces to underscores in names
bmon: a simple bandwidth monitor
open .: in osx, open finder in the current dir
lsmod: show kernel modules
printf: change the format of output
timeout: execute something and kill it soon after
disown: protect a job from disconnect
fc: edit your last command in your editor and execute it
sudo !!: repeat last command with sudo
tee: send output to stdout as well
pgrep: greps through processes
pkill: kills processes based on search
fmt: text formatter
multitail: see logs in separate views
bc: an interactive calculator language
apropos: info on commands
strace: the uber debug tool
man units: interesting
pstree: shows processes in a…well…tree
pv: a progress bar for piped commands
ddate: wtf
zgrep: grep within compressed files
zless: look at compressed files
nping: nmap-based custom packet creation
readlink: read values of links
iostate: look at your disk i/o
atop: another top
split: break a file into pieces
dd: disk writing
ndiff: show differences in nmap scans
ss: socket statistics (show apps using the Internet)

une petite cheatsheet sur les regexp

No no no. Don't use kill -9.

It doesn't give the process a chance to cleanly:

1) shut down socket connections

2) clean up temp files

3) inform its children that it is going away

4) reset its terminal characteristics

and so on and so on and so on.

Generally, send 15, and wait a second or two, and if that doesn't
work, send 2, and if that doesn't work, send 1. If that doesn't,
REMOVE THE BINARY because the program is badly behaved!

Don't use kill -9. Don't bring out the combine harvester just to tidy
up the flower pot.

Just another Useless Use of Usenet,

Un article framablog fort intéressant ... Ils font la promotion de jekyll pour le blogging, qui est aussi utilisé par img.bi ... Python, c'est vraiment impressionnant :-)

un article intéressant de blog qui propose de suivre une utilisation de FreeBSD avec une utilisation des jails (advanced chroot à la openvz, ptet moins avancé), je me met ça la et dans ma tdl 'faut que je mette la mimine un peu dans les BSD based qui sont quand même légion et bien différentes des RedHAT et Debian based ...

très, TRÈS pratique :)

excellent outil de dessin, qui surpasse les qualités de visio :D

Un site qui permet de tester la qualité d'un client SSL

How's My SSL? is a cute little website that tells you how secure your TLS client is. TLS clients just like the browser you're reading this with.

How's My SSL? was originally made to help a web server developer learn what real world TLS clients were capable of. It's been expanded to give developers and the very technically-savvy a quick and easy way to learn more about the TLS tools they use.

It's also meant to impell developers to modernize and improve their TLS stacks. Many security problems come from engineers simply not knowing what worries to have. How's My SSL? is a demonstration of what those TLS client worries should be.

How's My SSL? chooses topics important to today's security environment and analyzes clients in that context. It will never be a complete audit, but it can hit the high notes. Over time, How's My SSL? will change to live in an ever more difficult security environment. It will be kept up by people who care.

une doc bien foutue pour le chroot !

a voir comment généraliser à toutes les webapps le memcached

A tester ! Un outil comparable à nmon on dirait

scripts préconfigurés pour déployer des outils sur un serveur (via sebsauvage)