aboutsummaryrefslogtreecommitdiffstats
path: root/util/shredder/ShredOAuth.sh
Commit message (Collapse)AuthorAgeFilesLines
* Implement permission checking for OAuth clients using the xperm table. ↵redmatrix2015-05-171-1/+1
| | | | Currently 'all' permissions are applied to OAuth clients which gives them the same rights as the channel owner and full access to API functions as the channel owner. However, individual permissions can now be created. These mirror the permission names from the normal permission table (although it isn't required that they do so). Lack of an xp_perm entry for the specified permission and lack of an 'all' override indicates permission denied.
* limited progress in providing a POST option to shredder, back to auth ↵friendica2014-06-191-8/+19
| | | | signature mismatches again, likely a quoting issue
* wherein I revive some of my 30+year old shell scripting skills so that we ↵friendica2014-06-181-3/+20
| | | | | | | | can process arbitrary api endpoints which generate arbitrary json and be able to crunch all of these on the command line. Getting the arbitrary query arguments into a form where they could be signed as part of the oauth packet was a challenge. (It still might be - I haven't tried querying any Chinese photo album names yet). But you can now do something like for a in `util/shredder/shredder -c red/photos -q album=2013 | jshon -e photos -a -e src` ; do wget $a; done and download all the photos in your 2013 album
* Turns out Linux has a shred command in /usr/bin and its purpose is to ↵friendica2014-06-181-0/+191
over-write files so we don't want to invoke it accidentally. So as not to cause confusion and issues we will rename ours to "shredder". Aussies are of course allowed to alias this to "shredda".