On Jul 31, 6:06 pm, Ari <arisilverst...@yahoo.com> wrote:
> On Tue, 31 Jul 2007 02:48:40 -0700, ric wrote:
> > Don't even *think* about voice or video recognition, this is such a
> > dumb idea.
>
> Why?
> --
> "You can't trust code that you did not totally create yourself"
> Ken Thompson "Reflections on Trusting Trust"http://www.acm.org/classics/sep95/

Where do I start?
Consider why neither of these options are in widespread use.
Some points to start you off:
1) you'd need to securely rewrite MSGINA on windows to allow logon via
either option. How do you expect your video or audio recognition to
work before logon? Are you proposing to do it in hardware? If so,
which hardware did you have in mind? What is the cost of that
hardware? Is your solution going to be able to be remotely
administered so when a worker forgets their glasses or has a headcold
they can still login? Will it hook into AD, etc?
2) there are much simpler methods that demonstrably work. If you
can't deal with individual usernames/passwords then rely on a simple
physical token and password - e.g. a smartcard. these are easy to
integrate into your infrastructure.
3) why over complicate things? no-one is going to congratulate the OP
on their expensive, overly elaborate and fragile implementation of
something just because it's "cool".
4) In a burger-flipping environment, something that relies on voice
login in a noisy environment is a dumb idea. Logging in via a video
image in an environment where people regularly wear hair nets etc is
similarly dumb.
5) Whilst adding significant cost and complexity, both video and voice
login would have lower security: unless you can somehow avoid being
able to login with a recording of someone or a photograph.

I could go on, but this is such an obviously bad idea I don't think I
need to.

Ric