From Callum Brown to ~sircmpwn/hare-dev
Signed-off-by: Callum Brown <callum@calcuode.com> --- content/tutorials/introduction.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/tutorials/introduction.md b/content/tutorials/introduction.md index 7f55dcb..e6b6a0e 100644 --- a/content/tutorials/introduction.md +++ b/content/tutorials/introduction.md @@ -825,7 +825,6 @@ sections: which can be caused by that module. - title: Propagating errors sample: | use errors; [message trimmed]
From Callum Brown to ~sircmpwn/hare-dev
Apologies, I forgot to edit the subject prefix for this patch, as well as for https://lists.sr.ht/~sircmpwn/hare-dev/patches/41113 It should be [PATCH hare].
From Callum Brown to ~sircmpwn/hare-dev
After commit a8b5f993854cf9767ad308dabe025aadf0292820 Signed-off-by: Callum Brown <callum@calcuode.com> --- docs/haredoc.scd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/haredoc.scd b/docs/haredoc.scd index 2d5b497b..9269a317 100644 --- a/docs/haredoc.scd +++ b/docs/haredoc.scd @@ -22,7 +22,7 @@ See *DOCUMENTATION FORMAT* for details on the format. Show undocumented members (only applies to -Fhare and -Ftty). [message trimmed]
From Callum Brown to ~sircmpwn/hare-dev
Signed-off-by: Callum Brown <callum@calcuode.com> --- fmt/README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fmt/README b/fmt/README index 9eb3a975..f4388666 100644 --- a/fmt/README +++ b/fmt/README @@ -12,7 +12,7 @@ modifiers, and parametric format modifiers. Inline format modifiers are a series of characters within a format sequence. You may use a colon to add format modifiers; for example, "{:x}" will format an argument in hexadecimal, and "{3:-10}" will left-align the 4rd argument (zero [message trimmed]
From Callum Brown to ~sircmpwn/public-inbox
Hi Drew, Just want to say a quick thanks for todo.sr.ht. It's been very helpful organising my thoughts, planning what to tackle next, and keeping track of problems. And this is for a small project only I am working on! Highlights: - dense list lets me see lots of info at a glance and reduces scrolling and paging - tabular layout makes it easy to mentally sort and compare items - nice label system - "Submit another?"
From Callum Brown to ~sircmpwn/gmni-discuss
Hi, Solderpunk recently sent a "Request for feedback from server/client implementers using non-OpenSSL TLS stacks" to the Gemini mailing list. https://lists.orbitalfox.eu/archives/gemini/2021/007539.html gemini://rawtext.club/~sloum/geminilist/007539.gmi This might be of interest to people who use or develop gmni, and so I thought it worth linking here for those (like me) who do not subscribe to the gemini mailing list. Callum
From Callum Brown to ~sircmpwn/gmni-devel
With GCC 4.9.4 you get
src/certs.c:75:2: error: missing braces around initializer [-Werror=missing-braces]
br_skey_decoder_context skdec = {0};
---
Or you could have
br_skey_decoder_context skdec = {{{0}}};
and use -Wno-missing-field-initializers
Of course there probably aren't many people using error throwing
versions any more.
src/certs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/certs.c b/src/certs.c
[message trimmed]
From Callum Brown to ~sircmpwn/gmni-discuss
I still haven't worked out what precisely is going wrong, but I have managed to reliably reproduce the issue by sending a ton of requests at once. Basically and extremely easy DoS attack. #!/bin/sh while true do gmni -j once gemini://xxxxx/ & done
From Callum Brown to ~sircmpwn/gmni-devel
Quoting RFC 5280 section 4.1.2.5 [0]:
> To indicate that a certificate has no well-defined expiration date,
> the notAfter SHOULD be assigned the GeneralizedTime value of
> 99991231235959Z.
This fixes commit 8b65e303b01fc573cb1c40a365fb5db166146a37 where the
certificate expiration is set to LONG_MAX seconds in the future.
Using LONG_MAX avoids an integer overflow when using 200 years on 32
bit systems, however on 64 bit systems LONG_MAX is 9223372036854775807,
which is around 292 billion years worth of seconds. Unsurpringly, this
doesn't go down well with X509 certificates.
[0] https://datatracker.ietf.org/doc/html/rfc5280#section-4.1.2.5
---
[message trimmed]
From Callum Brown to ~sircmpwn/gmni-discuss
Here it is: coredumpctl info shows the following stack trace: #0 0x00007ff231f86005 __GI__IO_fread (libc.so.6 + 0x86005) #1 0x0000561b774b1611 client_writable (gmnisrv + 0x11611) #2 0x0000561b774b1fcd server_run (gmnisrv + 0x11fcd) #3 0x0000561b774a6621 main (gmnisrv + 0x6621) #4 0x00007ff231f270b3 __libc_start_main (libc.so.6 + 0x270b3) #5 0x0000561b774a42ee _start (gmnisrv + 0x42ee)