[Sugar-devel] How to authenticate with the Schoolserver on non XO hardware was: (Re: Auto-authentication for Browse)
dr at jones.dk
Thu Feb 26 15:42:26 EST 2009
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, Feb 27, 2009 at 09:09:08AM +1300, Martin Langhoff wrote:
>On Fri, Feb 27, 2009 at 1:06 AM, Simon Schampijer <simon at schampijer.de> wrote:
>> Martin, are there any plans yet on how to make the services of a
>> school server available to non XO hardware?
>I'm certainly keen on supporting it. We'd need a "uid" scheme - what
>would be the best approach for this?
>First, my thoughts went to hw UIDs, like a MAC address or a hash of
>the UIDs reported by lspci. But if the SoaS is indeed on a USB stick
>to be used on any hw but retaining my identity, then we want to make a
>purely random uid, created at first boot or with the Sugar "give me
>your name" screen..
>If the uid we use matches the format of the XO uids, then the XS will
>just take it. Maybe put a prefix to it so if we need to special-case
>it on the XS then we can...
Do you propose to *change* from identifying hardware to identifying OS?
Or do you propose adding a fallback, i.e. if no hardware id is found,
use OS id instead?
I suspect the best is on the client end to keep hardware id as such and
invent OS id as a new thingy. And on the XS end implement fallback
mechanism if no hardware id is provided but only OS id.
Keeping them separate allows each XS sysadmin the choice of e.g. only
(sorry for the noise if I got this all wrong...)
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the Sugar-devel