From f2f2fcdd57d20de23e80d95d9537ad4b123c79bd Mon Sep 17 00:00:00 2001 From: Marco Ochse Date: Mon, 23 Oct 2017 15:08:37 +0200 Subject: [PATCH] update documentation --- docker/p0f/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker/p0f/README.md b/docker/p0f/README.md index bd5bda33..1fc304b7 100644 --- a/docker/p0f/README.md +++ b/docker/p0f/README.md @@ -1,6 +1,6 @@ [![](https://images.microbadger.com/badges/version/dtagdevsec/p0f:1710.svg)](https://microbadger.com/images/dtagdevsec/p0f:1710 "Get your own version badge on microbadger.com") [![](https://images.microbadger.com/badges/image/dtagdevsec/p0f:1710.svg)](https://microbadger.com/images/dtagdevsec/p0f:1710 "Get your own image badge on microbadger.com") -# dockerized p0f +# p0f [p0f](http://lcamtuf.coredump.cx/p0f3/) P0f is a tool that utilizes an array of sophisticated, purely passive traffic fingerprinting mechanisms to identify the players behind any incidental TCP/IP communications (often as little as a single normal SYN) without interfering in any way.