WARNING: This server is unstable and will be retired in the next days. If you want to keep this forum available, please request immediately a migration on the Nabble Support forum. Forums that don't receive any migration request will be deleted forever.

 « Return to Thread: Security Considerations for Link Extensions

Re: Security Considerations for Link Extensions

by Colm Divilly :: Rate this Message:

| View in Thread


James Snell wrote:

> Ok, so I'm working on finishing up the basic link extensions draft.
> The Security Considerations are currently TBD. I wanted to take a
> moment to solicit input on appropriate security considerations for
> these optional, advisory extension attributes.
>
> One in particular... hash digest are often used as a simple means of
> verifying that data has not been modified while in transit.. hash
> digests contained within an atom:link cannot be used for that purpose.
> Rather, the hash attribute is used to express the state of the linked
> resource at a given point in time so that a feed consumer can detect
> whether or not the resource has been modified since the link was
> created.
>
>  
That sounds more like an Entity Tag (which are often but not always
generated using hashes),  so  do we  really mean an Entity Tag or is
there a reason to restrict this to just using hashes ?
> Other than that, there really shouldn't be any further security
> concerns with regards to the link extensions.. but I welcome being
> corrected on that :-) Thoughts?
>
>  

 « Return to Thread: Security Considerations for Link Extensions