[Opensim-dev] Proposed additional db fields

[Frisby, Adam]

SHA256/512 are pretty well defined - I'd probably go with either of those TBH. SHA-1 is looking slightly leaky these days (it's not 'broken', but could be in the next 5 years)

Adam

> -----Original Message-----
> From: opensim-dev-bounces at lists.berlios.de [mailto:opensim-dev-
> bounces at lists.berlios.de] On Behalf Of Hurliman, John
> Sent: Tuesday, 4 November 2008 11:35 PM
> To: opensim-dev at lists.berlios.de
> Subject: Re: [Opensim-dev] Proposed additional db fields
>
> What about 160-bit?
>
> -----Original Message-----
> From: opensim-dev-bounces at lists.berlios.de [mailto:opensim-dev-
> bounces at lists.berlios.de] On Behalf Of Frisby, Adam
> Sent: Tuesday, November 04, 2008 6:17 PM
> To: opensim-dev at lists.berlios.de
> Subject: Re: [Opensim-dev] Proposed additional db fields
>
> If you use a SHA hash, please consider a 256 or 512 bit signature
> rather than a 128-bit hash. 128-bit hashes are generally considered to
> be heading towards insecure (as far as asset forgery, etc goes). I'd
> just go the 512 bit signature myself - it's not really that much extra
> storage space.
>
> Adam
>
> > -----Original Message-----
> > From: opensim-dev-bounces at lists.berlios.de [mailto:opensim-dev-
> > bounces at lists.berlios.de] On Behalf Of Hurliman, John
> > Sent: Tuesday, 4 November 2008 1:14 PM
> > To: opensim-dev at lists.berlios.de
> > Subject: Re: [Opensim-dev] Proposed additional db fields
> >
> > This sounds great, as create_time is one of the missing metadata
> fields
> > that the distributed asset server uses. Would you also consider
> adding
> > a SHA-1 hash field for assets? It makes asset synchronization between
> > two servers easier and simple auditing possible.
> >
> > John
> >
> > -----Original Message-----
> > From: opensim-dev-bounces at lists.berlios.de [mailto:opensim-dev-
> > bounces at lists.berlios.de] On Behalf Of Sean Dague
> > Sent: Monday, November 03, 2008 12:12 PM
> > To: opensim-dev at lists.berlios.de
> > Subject: [Opensim-dev] Proposed additional db fields
> >
> > I've got a couple of proposed db fields that I think we should add
> in,
> > but I want feedback before just putting it in.
> >
> > users:
> >  * email - this is added by a lot of the web based management stacks,
> > and would be really handy to be in the base user definition.  I
> suspect
> > this is non controversial.
> >
> > assets:
> >  * create_time - the unix timestamp when the asset is created
> >  * access_time - the unix timestamp for last asset access
> >
> > The rationale for these asset additional fields was some
> brainstorming
> > this weekend on how we'd ever support asset reaping.  Why not
> perfect,
> > this may help in determining what are active assets, and what are
> > ancient assets that may be suitable for reaping.  Without these bits
> of
> > information, we've got a hard time here.
> >
> > Comments welcomed,
> >
> >         -Sean
> >
> > --
> > Sean Dague / Neas Bade
> > sdague at gmail.com
> > http://dague.net
> >
> >
> > _______________________________________________
> > Opensim-dev mailing list
> > Opensim-dev at lists.berlios.de
> > https://lists.berlios.de/mailman/listinfo/opensim-dev
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev