>>> Also, the GUI really need to make clear how many of assp's >>> functions this setting negates. >> It makes it quite clear: -> All data will be encrypted and >> unreadable to ASSP > > Technically it is accurate, but it does not make the significant > consequences clear. A GUI with explanations should do this, where > possible. It's one thing to provide accurate information, it's another > to provide useful information. A GUI with explanations should do this, > where possible. You might want to add something like this: > > "Because the TLS-Tunneling setting prevents assp from inspecting the > contents of both incoming and outgoing messages, it has the effect of > switching off all assp functions that rely on looking at the content > of headers and messages (such as auto-whitelisting, content Bayesian, > content regex, etc.)." > > HTH. > > Unfortunately, the above text addition does not solve the problem of > getting Do TLS to work with all clients. :-/ I need to talk to Thomas > some more. :-)
The GUI is already burdened with too much data. I have always felt only the most basic of descriptions should live in it. Each item could then simply link to the wiki, where users are in control to provide as much, or as little detail as they desire. -- Scott Iphone says hello. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
