Commits
- Commit:
ff05125eb81e5bbf2cf05b8434d03bce584936e0
- From:
- Stephen Gregoratto <dev@sgregoratto.me>
- Via:
- omar-polo <op@omarpolo.com>
- Date:
Implement OCSP stapling support
Currently dogfooding this patch at gemini.sgregoratto.me. To test,
run the following command and look for the "OCSP response" header:
openssl s_client -connect "gemini.sgregoratto.me:1965" -status
- Commit:
f0a01fc742e83b3f4736b5d64af3ab18148afc5a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
two -n to dump the parsed configuration
This adds a barebone dumping of the parsed configuration. It is not
complete, but I'm interested in dumping the full path to `cert' and
`key' in order to write some scripts that can inspect the
configuration, extract the certificates and renew them when expired
automatically.
It's not easy to parse gmid configuration otherwise because the syntax
is flexible and users can use macros. Instead, the idea is to run
gmid and let it dump the configuration once it's been parsed in a
static and predictable format.
Now is possible to parse gmid configuration with, say, awk or perl.
- Commit:
1298e4307f587041ae2a31611a92bb92799bff5a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
split the cert generation example on multiple lines
- Commit:
fba809b5c775fd4d3c28a012259ee3b1908d4e40
- From:
- Omar Polo <op@omarpolo.com>
- Date:
tag 1.7.3
bump version number
- Commit:
2bb1776bacc96357fc182ef396508fe71816e0b0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
keep the openssl key generation example under 80 columns
- Commit:
301e039d24172a5e15bed60701bf279798d28621
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
gmid.1: some spelling, grammar and crosslinks
- Commit:
e308526cf63d7cbbabaa4bf93bae45a27fb58d4b
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
gmid.1: provide certificate generation example
- Commit:
e58a447a28a416ee719a9e457bfc8160a9b0e771
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
gmid.1: document logging
- Commit:
af5f9b271e852c641ff6c1d226e42d98f4182f25
- From:
- Omar Polo <op@omarpolo.com>
- Date:
use \e instead of \\ as a mean to escape \
Just read in a mail from Ingo to tech@
> Using \\ outside macro definitions (i.e., outside the bodies of roff(7)
> .de and similar requests) is almost always wrong even in low-level roff
> code, and \\ must never be used in manual pages.
- Commit:
8068d2ff33992fcaf0e5f38bc7b3d86789e7e92e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
tag v1.7.1
This version includes two bugfixes:
- use ${MAKE} to recursively call make
- fix the misleading example in the man page: macros name may not be
reserved words
Both bugs found and fixed by Anna “CyberTailor”, thanks!
- Commit:
ad15003be8fc1422b52600f1d5c6b6875e46cad7
- From:
- Omar Polo <op@omarpolo.com>
- Date:
align
- Commit:
2d06ae62aeb4c107a1c8fd04f23aa81b5b93fe3f
- From:
- Anna “CyberTailor” <cyber@sysrq.in>
- Via:
- Omar Polo <op@omarpolo.com>
- Date:
fix misleading example in man page
> Macros names may not be reserved words
- Commit:
b79b2d811b7775f6be71f7248c3cc498a6115bb0
- From:
- Omar Polo <op@omarpolo.com>
- Date:
tag v1.7
- Commit:
528f37cd2dbed6a7906e3adb96c12f44acba919d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync macro usage and mention the `include' keyword
- Commit:
3d132b283345475921bf9cf1e8d77e56ede2edf3
- From:
- Omar Polo <op@omarpolo.com>
- Date:
`param' is forbidden inside `location's too
and while there sort the list of disallowed rules.