Gary Feldman wrote:
>
> > From: [EMAIL PROTECTED]
> > On Behalf Of Sean Wieland
> ...
> > (with OK as the default -- stupid users always assume the defaults are
> > correct)
>
> Let's be fair. As your example really points out, the problem in this
> specific case (your example, not necessarily the "Accept this invalid
> certificate case") is with the developers, not the users. The defaults
> should always be correct, and if they're not, it's because the developer
> goofed, not because the user thought the developers were competent.
>
> Gary
This is going on a tangent, but even with the invalid certificate case
it's still something a developer (someone who's knowledgeable) can
handle better than a typical user (someone who's typically not
knowledgeable). As a general rule, users don't read. Experienced users
think they know the answer before they read the question while
inexperienced users just don't want to read (they'd rather be doing
their task at hand than deal with the issues of the tool they're using
to accomplish that task) and assume "ok" is always correct. Thus, with
the invalid certificate scenario, the dialog should be "This certificate
is invalid, so authorization will not happen." and then an override
choice as NOT the default. As you said, it's a developer competency
issue.
-Sean
--
+-----=[export-a-crypto-system-sig RSA-3-lines-PERL]=-----+
|#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj|
|$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1|
|lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) |
+--------=[http://www.cypherspace.org/~adam/rsa/]=--------+
"Most people would rather die than think, and most people do."
-- Bertrand Russell
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
