From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Tue, 10 Mar 2009 16:01:33 -0700 Message-ID: <3e1162e60903101601l607fab61r700bc15d34f18e1@mail.gmail.com> From: David Leimbach To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001636e1fb0a77182b0464cbbb5f Subject: [9fans] factotum question Topicbox-Message-UUID: b8989834-ead4-11e9-9d60-3106f5b1d025 --001636e1fb0a77182b0464cbbb5f Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Factotum is some guy in the room that, even though you have the phone, you keep asking what to say next on the line to get authentication to happen. Is this a bad analogy? Factotum is available on the client side during authentication via a library we can use to talk to it. When we get an "afd" we basically write and read from it asking our local factotum what to say next? Is this where the proxying happens? If so I think I get it... otherwise no :-) Dave --001636e1fb0a77182b0464cbbb5f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Factotum is some guy in the room that, even though you have the phone,= you keep asking what to say next on the line to get authentication to happ= en.

Is this a bad analogy? =A0

Facto= tum is available on the client side during authentication via a library we = can use to talk to it. =A0When we get an "afd" we basically write= and read from it asking our local factotum what to say next?

Is this where the proxying happens? =A0If so I think I get i= t... otherwise no :-)

Dave
--001636e1fb0a77182b0464cbbb5f--