Your question made me think that you were worried about security. I would 
suggest that the randomness provided by the ID assignment is not helpful if you 
are thinking of using these like people often use authentication tokens or 
things like shareable urls for Dropbox or Google docs. The most basic question 
in those scenarios is - if a user has one key what is the likelihood that they 
could guess another valid key, potentially for another users data? Depending on 
how you are enforcing user separation, with datastore keys the answer is 
actually it is quite likely that they could guess another valid key.


In general, you probably want to be handing out security tokens created by a 
standard process combined with HTTPS with the key. But unfortunately getting 
this kind of security right means that you have to thoroughly understand what 
security you are trying to enforce (i.e., threat modeling).


Karl







> On Sep 28, 2015, at 10:33 AM, Rob Curtis <robertbcur...@gmail.com> wrote:
> 
> 
> Excellent, thanks very much.
> 
> On Mon, Sep 28, 2015 at 4:22 PM Ryan (Cloud Platform Support) 
> <rbruy...@google.com
>> wrote:
> 
>> Salutations Rob
>> 
>> "The Blobstore value is assigned a unique, randomly generated key." [1]
>> 
>> The book was written by a Googler and is a good read.
>> 
>> [1] http://ae-book.appspot.com/chapters/blobstore
>> 
>> 
>> On Sunday, September 27, 2015 at 3:23:50 PM UTC-4, Rob Curtis wrote:> Hi, I 
>> can't find any information on this in the documentation;
>>> Are blob keys guessable? 
>>> Is it safe to expose stringified blob key to a user?
>>> 
>>> Thanks
>>> Rob
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Google App Engine" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-appengine/B2H5YeiDqLQ/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-appengine+unsubscr...@googlegroups.com
>> .
>> To post to this group, send email to google-appengine@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/google-appengine
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/f5615b93-9c7d-4494-bf4e-17bc4e72f242%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout
>> .
>> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-appengine+unsubscr...@googlegroups.com
> .
> To post to this group, send email to google-appengine@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/google-appengine
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-appengine/CAFk6oqCGp%2BtSSV3vYkOn8GOc%3D1yGkC_3opF2UVyyxE4dXoVmHQ%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/E2100131-534F-467A-A5F5-15C737DB510D%40rakkoon.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to