Clean up the make file and use a more portable method of making tarballs.

[irker.git] / security.txt

diff --git a/security.txt b/security.txt
index 62bcee5bfafc75b3df28b4341e8dd6c9a8d258b3..8faf43faf4565891c339c0fa5badd7ec7a0359be 100644 (file)
--- a/security.txt
+++ b/security.txt
@@ -163,10 +163,6 @@ near resource limits.  An ordinary DoS attack would then be prevented
 from completely blocking all message traffic; the cost would be a
 whole lot of join/leave spam due to connection churn.
 
-We also use greenlets (Python coroutines imitating system threads)
-when they are available.  This reduces memory overhead due to
-threading substantially, making a thread-flooding DoS more dfficult.
-
 == Authentication/Integrity ==
 
 One way to help prevent DoS attacks would be in-band authentication -
@@ -233,21 +229,6 @@ project.  The only other competitor to replace CIA known to us
 In the general case we cannot guarantee this property against
 groups A and F.
 
-== Why there is no support for passworded channels ==
-
-We've had support for password authentication to IRC requested, but it
-would be a rather bad fit for irkerd’s usage pattern. The problem
-isn’t that credentials would be difficult to pass to irkerd – an 
-optional password field wiuld ve easily enough added to the JSON. 
-
-No, the problem is that once irkerd were to acquire such a credential,
-it would have to do source-address IP checking to know (at a minimum)
-whether the source host of any given notification request is the same
-as one that has presented the password.
-
-It seems best not gong to go there; the potential for IRC access controls
-becoming leaky seems too high.
-
 == Risks relative to centralized services ==
 
 irker and irkerhook.py were written as a replacement for the