op public repos

Commits

Commit:: 0ac785a6fa007acdc8ecb4f697981c574ab1b710
From:: Omar Polo <op@omarpolo.com>
Date:: Mon Jun 5 20:35:12 2023 UTC

revert aae8f6bf2b it's just not worth it to inflict this breaking change to the users.

Commit:: e1e04caa4f847162936a6908d3bc02a3dbdfac6d
From:: Omar Polo <op@omarpolo.com>
Date:: Mon Jun 5 20:27:27 2023 UTC

+log.h

Commit:: df5058c919cbd1538d0a04cb2a4c179c0291566f
From:: Omar Polo <op@omarpolo.com>
Date:: Mon Jun 5 17:07:52 2023 UTC

provide a more usual fatal fatal usually appends the error string. Add 'fatalx' that doesn't. Fix callers and move the prototypes to log.h

diff | patch | tree

Commit:: a01a91db06a943ef0cc8fbb7294786814a63b65c
From:: Omar Polo <op@omarpolo.com>
Date:: Mon Jun 5 16:18:57 2023 UTC

move some server-related code to server.c

diff | patch | tree

Commit:: 9a821f8c0f04bf9135bff60cc3ae3f4d109a02ee
From:: Omar Polo <op@omarpolo.com>
Date:: Mon Jun 5 15:07:24 2023 UTC

fold long lines

diff | patch | tree

Commit:: ac9f55ba3248ea026ca146202c69c2aa4b3594ed
From:: Omar Polo <op@omarpolo.com>
Date:: Mon Jun 5 14:35:23 2023 UTC

gencert: add -e flag to generate a cert using an EC key

diff | patch | tree

Commit:: 34886b1e55ef0eda629b22742e7173fea04bf8f7
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 8 10:30:00 2023 UTC

add tags target

diff | patch | tree

Commit:: 1e0b974519c8228e271b2b6e677c1b8f9a109b6b
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 8 10:27:32 2023 UTC

send capsicum/landlock/seccomp hack to Valhalla

diff | patch | tree

Commit:: 0b62f4842d7c65b8f64c5f676a0a05333fd7db6f
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 8 10:27:32 2023 UTC

drop landlock/seccomp and capsicum support it reached a point where this stuff is not maintenable. I'd like to move forward with gmid, but the restriction of capsicum and the linux environment at large that make landlock unusable (how can you resolve DNS portably when under landlock?) -and don't get me started on seccomp- makes it impossible for me to do any work. So, I prefer removing the crap, resuming working on gmid by cleaning stuff and consolidating the features, improving various things etc... and then eventually see how to introduce some sandboxing again on other systems. Patches to resume sandboxing are, as always, welcome!

diff | patch | tree

Commit:: c9e97a6ecb4acc6796468cf6bf1f31e8dc172694
From:: Anna “CyberTailor” <cyber@sysrq.in>
Via:: Omar Polo <op@omarpolo.com>
Date:: Sat Dec 24 08:41:09 2022 UTC

include grp.h for setgroup(2) on linux

diff | patch | tree

Commit:: 837156014c5dc5746ecfcc00e5b02db16cb90f67
From:: Omar Polo <op@omarpolo.com>
Date:: Fri Dec 2 15:37:49 2022 UTC

add a disclaimer

diff | patch | tree

Commit:: 195f32d3a4e0b3c962cb089cde148fbaf0abb58b
From:: Omar Polo <op@omarpolo.com>
Date:: Fri Dec 2 15:21:20 2022 UTC

update the site for 1.8.6

diff | patch | tree

Commit:: bd8683d0fd36893c18e7271faaa3b9ea67df0695
From:: Omar Polo <op@omarpolo.com>
Date:: Fri Dec 2 11:53:35 2022 UTC

add tests and compat for setresuid and setresgid

diff | patch | tree

Commit:: 06035a023710962df95f48d8486739154a9d707a
From:: Omar Polo <op@omarpolo.com>
Date:: Tue Nov 29 23:03:55 2022 UTC

more is*() unsigned char cast continuation of 6130e0eeac9db4fa8e6fe5934ec2d0ab202f979e

diff | patch | tree

Commit:: 97b306cbee6d105885a761e04274f661a0ec3757
From:: Omar Polo <op@omarpolo.com>
Date:: Sun Nov 27 15:35:10 2022 UTC

add an implicit fastcgi parameter: GEMINI_SEARCH_STRING it’s the QUERY_STRING decoded if it’s a search-string (i.e. not a key-value pair.) It’s useful for scripts to avoid percent-decoding the querystring in the most common case of a query, because in Gemini querystrings key-value paired are not common. Idea from a discussion with Allen Sobot.

diff | patch | tree

More ↓