I regularly work on software projects that I make publicly available. Below is - a selected few of my projects that I am either currently working on or am - currenty the most proud of. If you want to see all of the open source projects - that I have worked on in the past, feel free to checkout the github or - snorbaart links above! + a selected few of my projects that I am either currently working on or am the + most proud of. If you want to see all of the open source projects that I have + worked on in the past, feel free to checkout the github or snorbaart links + above!
Shield your gitea API from bad actors on public instances.
diff --git a/index/last_checksum.txt b/index/last_checksum.txt index 1e31213..4174b3e 100644 --- a/index/last_checksum.txt +++ b/index/last_checksum.txt @@ -1 +1 @@ -3544450995 2099 +381269847 2090 diff --git a/index/last_edit_date.txt b/index/last_edit_date.txt index 91c4769..0083227 100644 --- a/index/last_edit_date.txt +++ b/index/last_edit_date.txt @@ -1 +1 @@ -1653402568 +1653462513 diff --git a/projects/dns-yml/index.html b/projects/dns-yml/index.html index 85d796e..c141a7f 100644 --- a/projects/dns-yml/index.html +++ b/projects/dns-yml/index.html @@ -24,7 +24,7 @@
@@ -37,12 +37,12 @@
While it hasn't been tested in large deployments, I think that this DNS YAML - could theoretically be a great addition for large bodies of people who work - on applications within the same infrastructure. Traditionally, DNS records - are something that is managed by sysadmins who edit zone files by hand, or - through self-service UIs that some employees are allowed to acces. If one - were to, in stead, use version controlled DNS YAML documents in combination - with CI/CD, the following things would be achieved: + could be a great addition for large bodies of people who work on applications + within the same infrastructure. Traditionally, DNS records are managed by + sysadmins who edit zone files by hand, or through self-service UIs that some + employees are allowed to acces. If one were to, in stead, use version + controlled DNS YAML documents in combination with CI/CD, the following things + would be achieved:
+ I built the Gitea API Protector in response to a request for help that + maintainers of codeberg.org put out on the + fediverse in january of 2020. Codeberg was (and probably still is) one of the + largest public gitea instances and as such was + having trouble with spam bots that would create spam issues on repositories + using the API. My solution was to lock new users out of API access and have + them apply for it through a pull request they could create using the gitea web + UI. The people from codeberg + were interested, + but in the end they didn't end up going with my solution. Nevertheless the + software is fully functional and the codebase is small enough for people to + change it for their own use cases if they so desired. +
+ ++ A more elaborate explanation of the technical details an setup instructions can + be found in the README of the repository + on github or + on codeberg.org. +
+ + + + diff --git a/projects/gitea-api-protector/last_checksum.txt b/projects/gitea-api-protector/last_checksum.txt new file mode 100644 index 0000000..f690272 --- /dev/null +++ b/projects/gitea-api-protector/last_checksum.txt @@ -0,0 +1 @@ +452533407 1259 diff --git a/projects/gitea-api-protector/last_edit_date.txt b/projects/gitea-api-protector/last_edit_date.txt new file mode 100644 index 0000000..796fa50 --- /dev/null +++ b/projects/gitea-api-protector/last_edit_date.txt @@ -0,0 +1 @@ +1653462474 diff --git a/projects/gitea-api-protector/publish_date.txt b/projects/gitea-api-protector/publish_date.txt new file mode 100644 index 0000000..00a6bdb --- /dev/null +++ b/projects/gitea-api-protector/publish_date.txt @@ -0,0 +1 @@ +1653462215