Update documentation to popproxy, instead of improxy.

diff --git a/NEWS b/NEWS
index 29923a6..8626204 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,7 +1,5 @@
-NEWS for improxy
+NEWS for popproxy
 
-* Version 0.1
+* Version NOT 0.1
 
-- This is our first pre-alpha release. There is not much use to the
-software besides verifying which hosts are connecting to which
-servers.
+- This is our first non-release.

diff --git a/README b/README
index 5cf1b97..9a4aca8 100644 (file)
--- a/README
+++ b/README
@@ -1,12 +1,7 @@
-improxy is a Instant Message Proxy.
+popproxy is a POP3 proxy.
 
-Its primary focus is XMPP transparent proxying. It should be able to:
+It may be used as a reverse proxy mainly, but extending it to work as a
+gateway proxy based on username is possible.
 
-* find out which server the client is connecting to and connect to it
-using its SRV record.
-
-* control which servers can be connected to and which users should be
-able to connect.
-
-* filter XML stanzas by from an to (control which entities you send data
-to or receive data from).
+It currently is able to control access based in username and has some
+SSL support.

diff --git a/TODO b/TODO
index 4513d15..be02e02 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,35 +1,15 @@
-A list of TODO items that should be more detailed in a ROADMAP,
-perhaps.
+Immediately:
+* Remove connection/socket leaks.
+* Support server-side (client-to-proxy) SSL connections.
+* Configuring SSL support, like certificates and keys.
+* Configuring access control policy.
 
-Next soon releases:
+Some easy protocol support:
+* Support APOP.
+* Support STLS. 
 
-* Support SRV DNS record lookups.
-* Support TLS connections.
-* Identify user identities and log that.
-* Block based on sender/destination JID.
+Some extensibility support:
+* Support gateway proxies based on username maps.
 
-
-Later releases:
-
-* Allow online configuration of addresses to block accepting HTTP
-connections, perhaps. Jabber commands would be nice too.
-* Support other protocols.
-* Distinguish between types of data/messages and block based on them.
-* Support other criteria for blocking, like time/day of day/week.
-* Archive data transmitted and allow administrator to read it.
-
-
-Protocol messing:
-
-* Filter the server offer for TLS, forcing some clients not to use it.
-* Start TLS for clients that don't and even send them an invalid
-certificate if they don't check if it's a valid one (all configurable
-by administrator)
-* Intercept archive configuration and use it for the proxy archiving
-feature itself.
-
-
-Protocol updates?
-
-* Design and publish JEP to allow non-transparent proxies.
-* Design and publish JEP for proxy configuration.
+Some sysadmin cake:
+* Configuration interface besides CLI.