On Fri, 2004-11-19 at 03:11 +0200, Enver ALTIN wrote:
Hi,
On Thu, 2004-11-11 at 17:20 -0500, Rodney Dawes wrote:
> In this mockup, we have the "Test", "Work", and "Test Work" accounts
> (yes, I'm lazy, and just copied stuff
> around in GIMP). The "Test" account is connected, but is not over
Hi,
On Thu, 2004-11-11 at 17:20 -0500, Rodney Dawes wrote:
> In this mockup, we have the "Test", "Work", and "Test Work" accounts
> (yes, I'm lazy, and just copied stuff
> around in GIMP). The "Test" account is connected, but is not over a
> secure connection. The "Work" account
> is connected, an
On Thu, 2004-11-11 at 17:20 -0500, Rodney Dawes wrote:
> As far as actual behavior and settings go, the most user-friendly
> method, is to default to the highest level
> of security, and safely fall back through lower levels. Based on this
> ideology, we can get rid of the "Never"
> and "Whenever
Hi,
The icons probably wouldn't have the look of being broken, and wouldn't
have the check or x in a box on them either, in a real implementation.
They were the best thing I could find for the mock-up. The icon is
small as it is, so adding the socket with a lock, is probably not so
much better. Ma
El jue, 11-11-2004 a las 17:20 -0500, Rodney Dawes escribió:
>
> In this mockup, we have the "Test", "Work", and "Test Work" accounts
> (yes, I'm lazy, and just copied stuff
> around in GIMP). The "Test" account is connected, but is not over a
> secure connection. The "Work" account
> is connecte
So,
Back to the three-letter acronym problem we have. I talked with fejj a bit yesterday at lunch, about
the use of SSL/TLS, and how the code behaves, and what optimal solutions might be. It occurs to me
that people don't use "Whenever Possible" out of the fear that they will be reading e-mail
