News for hackers. Stuff that matters.
Re:DataKit: It's like Parse, just open source. Written in no... by charliesome on Wednesday March 28, 2012 @07:04AM (#3765598)
I'm not totally thrilled about having a 'secret' key embedded in the app that's distributed publicly.

I had a brief skim over the code and I can't see any access control stuff so I'm guessing this key has full access.

If that's the case, I can't see how this could ever be suitable for use in any real app.

Re:DataKit: It's like Parse, just open source. Written in no... by eaigner on Wednesday March 28, 2012 @07:16AM (#3765628)
What's the difference to the "clientKey" of Parse's SDK? The requests should be served over SSL anyway, so if your point is you don't want to distribute a key you got the same problem with Parse. You can obfuscate the key though.
Re:DataKit: It's like Parse, just open source. Written in no... by charliesome on Wednesday March 28, 2012 @07:23AM (#3765650)
It doesn't matter whether you use SSL or not. If it's in your app, it can be found quite easily.

Parse provides you with a few different keys and also offers ACL functionality. I'm still not too crash hot on expecting the client to setup an ACL on their own objects though...

Re:DataKit: It's like Parse, just open source. Written in no... by lukeholder on Wednesday March 28, 2012 @01:13PM (#3767271)
can you propose how an client can authenticate with this type of service without a key?