Intro & observations

[Davidson Rodrigues Paulo]

2007/8/21, Bryan J. Smith <b.j.smith at ieee.org>:
> That's typically because there is no "Point'n Click" 'process.'  Yes,
> there are key managers and other GUI solutions, but the "process"
> (including the concepts of "Public Key" authentication in general) is
> what most people take issue with.  ;)

No. This is what the people say. The process is simple, when the tools
are simple. In other words, give to people tools that make more easy
to execute each step of the process and the entire process will looks
easy for them.

> The ultimate irony is that most people say, "I just want it to work"
> and don't stop to realize part of the "process" *IS* to understand
> *WHY* you don't "just want it to work."  I.e., what protections and
> processes you must proliferate, not, for example ...
>
>   "okay, I got a key, not sure which one you need so
>    I'll upload both of them to you."  ;)
>
> [ Oh man, that happens *WAY* too much! ]

Welcome to the Earth. :-)

> I know, but the "process" is what people complain about, not the GUI.

If a computer don't turns on, the owner will say to the technician "My
computer don't turns on", not "My computer don't turns on because one
of the RAM modules". Do you understand? We have an issue with the
process, but we need to know that the problem is not the process
itself, same way as the problem with the computer is not the computer,
but something inside it that the owner don't know what it and the
technician needs to discover.