This isn't really an example of security via obscurity. Assume the incoming email handler is some random value - that could be considered your "shared secret". A more precise definition can be found here: http://en.wikipedia.org/wiki/Kerckhoffs's_Principle. Even if an attacker knows you're doing this, the attacker still needs to figure out what the incoming email address is.
(FWIW I think you are getting ahead of yourself). Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Thu, Jun 2, 2011 at 7:54 AM, J C <ciho...@gmail.com> wrote: > "Security through obscurity" is really the only way? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/Qkg2dHQteVktRGNK. > > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
