From 0f6e7b65dec62d61ee933e8b605f3df9e552c58d Mon Sep 17 00:00:00 2001 From: Justus Winter <4winter@informatik.uni-hamburg.de> Date: Fri, 4 Apr 2014 11:50:26 +0200 Subject: mention portseal --- open_issues/automatically_checking_port_deallocation.mdwn | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'open_issues/automatically_checking_port_deallocation.mdwn') diff --git a/open_issues/automatically_checking_port_deallocation.mdwn b/open_issues/automatically_checking_port_deallocation.mdwn index fb8cfd01..6aeaf207 100644 --- a/open_issues/automatically_checking_port_deallocation.mdwn +++ b/open_issues/automatically_checking_port_deallocation.mdwn @@ -20,3 +20,13 @@ IRC, unknown channel, unknown date. which is already a good thing of course the coverage can't be perfect one of the bugs I fixed happened only for setuid binaries for instance + +- - - + +portseal can automatically detect port leaks. It is somewhat +intrusive, as it leverages a source-transformation and hence requires +a recompilation of the code that contains the port leak. Currently, +it is a prototype. If you are looking for a port leak, I'd love you +to try it though: + +[[http://darnassus.sceen.net/gitweb/teythoon/portseal.git]] -- cgit v1.2.3