diff options
| author | Justus Winter <4winter@informatik.uni-hamburg.de> | 2014-04-04 11:50:26 +0200 |
|---|---|---|
| committer | Justus Winter <4winter@informatik.uni-hamburg.de> | 2014-04-04 11:50:26 +0200 |
| commit | 0f6e7b65dec62d61ee933e8b605f3df9e552c58d (patch) | |
| tree | 0df01392c55b7caffea0e45087d837e7b1ba5c1b /open_issues | |
| parent | 081588619324e4ade508ce6d093170987fdfd63d (diff) | |
mention portseal
Diffstat (limited to 'open_issues')
| -rw-r--r-- | open_issues/automatically_checking_port_deallocation.mdwn | 10 |
1 files changed, 10 insertions, 0 deletions
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. <youpi> which is already a good thing <youpi> of course the coverage can't be perfect <youpi> 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]] |