test.git - Random test repo

	Commit message (Collapse)	Author	Age	Files	Lines
*	{config,index}.go, cca.scfg.example, style.css, *.html: Link to source	Runxi Yu	5 days	1	-0/+3
\|
*	*: Change license to AGPL-3.0-or-later	Runxi Yu	5 days	1	-21/+11
\|
*	auth.go, config.go, cca.scfg.example: Issue expiring cookies	Runxi Yu	5 days	1	-0/+3
\|
*	ws.go, config.go, config.scfg.example: Attempt to fix deadlock	Runxi Yu	6 days	1	-0/+3
\| \| \| \| \| \| \|	When propagate tries to propagate a message to a connection that actually called propagate, it deadlocks because the it tries to send to that connection's send channel in the same goroutine. This is an attempt at a fix.
*	courses.go, etc: Make courses a map instead of a slice	Runxi Yu	8 days	1	-3/+0
\| \| \| \| \|	We need to refer to courses by their ID, and a map makes significantly more sense than a slice.
*	*.go, cca.scfg.example: Expose performance options	Runxi Yu	9 days	1	-0/+16
\|
*	*.go: Wrap errors	Runxi Yu	9 days	1	-2/+3
\|
*	*.go: Linting	Runxi Yu	11 days	1	-7/+7
\|
*	*.go: Add comments	Runxi Yu	2024-09-09	1	-4/+8
\|
*	*: Call Graph API for department information	Runxi Yu	2024-09-07	1	-0/+6
\| \| \| \| \| \| \| \| \| \| \| \|	I am using a hybrid flow with "id_token" for OpenID Connect and "code" for an Authorization Code. I would use "token" too but that doesn't seem to be supported for standard web-apps and could result in strange session-hijacking issues. We still need PKCE sometime in the future; however it's not a priority: the worst attack someone could pull off is to use a different user's Authorization Code and steal a Department, which probably isn't too big of a deal as the Authorization Code should be secret anyways.
*	*: Basic authentication and templates	Runxi Yu	2024-09-07	1	-0/+111
	These are imported from FBFP and slightly modified to be specific to YKPS (while not being hard to port to other environments that use APIs that use OAUTH 2.0). Some code is also simplified. Database code still needs an audit, and things are not tested yet.