puggan

Keybase proof

I hereby claim:

• I am puggan on github.
• I am puggan (https://keybase.io/puggan) on keybase.
• I have a public key whose fingerprint is BE9D 250A 8063 1C89 186E BFA7 A6AC BD46 A488 1BE3

To claim this, I am signing this object:

puggan

This Gist confirms the Linked Identity in my OpenPGP key, and links it to this GitHub account.

Token for proof:
[Verifying my OpenPGP key: openpgp4fpr:be9d250a80631c89186ebfa7a6acbd46a4881be3]

puggan

This Gist confirms the Linked Identity in my OpenPGP key, and links it to this GitHub account.

Token for proof:
[Verifying my OpenPGP key: openpgp4fpr:be9d250a80631c89186ebfa7a6acbd46a4881be3]

puggan

This Gist confirms the Linked Identity in my OpenPGP key, and links it to this GitHub account.

Token for proof:
[Verifying my OpenPGP key: openpgp4fpr:be9d250a80631c89186ebfa7a6acbd46a4881be3]

puggan

This Gist confirms the Linked Identity in my OpenPGP key, and links it to this GitHub account.

Token for proof:
[Verifying my OpenPGP key: openpgp4fpr:be9d250a80631c89186ebfa7a6acbd46a4881be3]

puggan

Serverside - Cron:
create a base folder, and then put bare git dirs in it.
for each git/subfolder:
 * fetch all
 * list all `git log --all --date-order --pretty=oneline --show-signature`
 * save commit-hash, a project-reference, a gpg status, sign- uid, email and fingerprint
 
 Serverside - JSON
 Make an api that takes a commit-hash (or a list of them),
 and answer with 

puggan

https://alexnisnevich.github.io/untrusted/
lvl 1: https://gist.github.com/b735d851674ee4bd3be6fd68f699a327
lvl 2: https://gist.github.com/1933f2f8fd6f6a8979badee8ae851d7b
lvl 3: https://gist.github.com/3f591c084483872172e21f58164cd5ea
lvl 4: https://gist.github.com/cb9689e18e67c08d67c030a4a4cfd9aa
lvl 5: https://gist.github.com/753c7f7b7201033b4d67a0cc3a9bf7b8
lvl 6: https://gist.github.com/b35cb130c4337c31e034261c3993ad3d
lvl 7: https://gist.github.com/abf04d64cc80006a66b095dc0c959b7d
lvl 8: https://gist.github.com/79966422553a5feb2338b584b4ae74fb
lvl 9: https://gist.github.com/e48ba09b686c8c356064c7fc204e68c6

puggan

echo 'body {color: pink}' > pink.less
echo "{}" > package.json
cat << HEREDOC > gulpfile.js
const gulp = require("gulp");
const plug = require("gulp-load-plugins")();

gulp.task("default", () => gulp
	.src("pink.less")
	.pipe(plug.sourcemaps.init())
	.pipe(plug.less())

puggan

The base is PSR-12 from https://www.php-fig.org/psr/psr-12/

Here is some aditions that are allowed, but not enforced by PSR-12:

2.3 Lines

• PSR-12 says:
  • Blank lines MAY be added to improve readability and to indicate related blocks of code except where explicitly forbidden.
• I add:
  • There MUST NOT be more then one consecutive blank line.

puggan

How the JWT tokens work at https://scoutid.se/admin

The requests

1. Ajax: https://scoutid.se/jwt/jwt.php?app_id=<domain_name/entity_id>
   Response 403: {ok: false, error: "No session", url: "<auth url>"}

2. redirect to <auth url> (https://scoutid.se/simplesaml/module.php/core/loginuserpass.php?AuthState=...)

3. Ajax: https://scoutid.se/jwt/jwt.php?app_id=&lt;domain_name/entity_id>
   Response 200: {ok: true, token: "<jwt token>"}