News for hackers. Stuff that matters.
Re:Prose, a content editor for GitHub by jgeewax on Saturday May 03, 2014 @04:33PM (#7692263)
Couldn't agree more... Do we really need to grant read and write access to all repos? Sucks if GH's scoping is that coarse.
Re:Prose, a content editor for GitHub by Wingman4l7 on Saturday May 03, 2014 @04:46PM (#7692294)
It definitely isn't that coarse: https://developer.github.com/v3/oauth/#scopes
Re:Prose, a content editor for GitHub by VoxPelli on Sunday May 04, 2014 @02:24AM (#7693505)
GitHub are also working on enabling users to accept just a subset of the requested scopes, like just access to public repos, which will make using all of the more fine-grained scopes easier: https://developer.github.com/changes/2013-10-04-oauth-change...
Re:Prose, a content editor for GitHub by hk__2 on Saturday May 03, 2014 @04:47PM (#7692297)
No it’s not, you can make an app that have access only to your public info, and/or public repos, etc.
Re:Prose, a content editor for GitHub by malandrew on Sunday May 04, 2014 @08:56AM (#7694099)
Unfortunately Amazon is the only cloud provider out there with a robust ACL system.

Is there an open industry standard for implementing ACL policies flexibly like the one Amazon has?

Re:Prose, a content editor for GitHub by garblegarble on Sunday May 04, 2014 @05:29PM (#7695904)
http://en.wikipedia.org/wiki/XACML would be one - it can be a little complicated, but if you can get over that it's quite nice and also adds the idea of an Obligation (something that must be performed on a grant/deny - for example, logging/e-mailing)
Re:Prose, a content editor for GitHub by stanzheng on Saturday May 03, 2014 @05:02PM (#7692328)
I agree that breakdown should be more anonymized. Readme permission/gitignore/license/code should have different end permissions