Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

2023-07-28 Thread forest . owlet
Hi Richard, I'm sorry for my tardy response. I just returned from holiday. On 2023-07-23 05:11, Richard Laager wrote: > Some questions from upstream, with my commentary added... > >> How busy is this sustem? Is it just a simple client or also a server? If >> server, how busy? This is a server

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

2023-07-23 Thread Richard Laager
Is this reproducible for you? If you have experience with building from source, upstream has proposed the following patch. Otherwise, I could build a test package for you. diff --git a/ntpd/nts_cookie.c b/ntpd/nts_cookie.c index 166d0230f..a73955fb7 100644 --- a/ntpd/nts_cookie.c +++

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

2023-07-22 Thread Richard Laager
Some questions from upstream, with my commentary added... How busy is this sustem? Is it just a simple client or also a server? If server, how busy? From the stack trace, the server side is trying to decode a NTS cookie. Is this box setup as a NTS server? That needs a certificate and key so

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

2023-06-29 Thread forest . owlet
Hi, Here's a backtrace from the latest ntpsec coredump. root@karita:/var/lib/systemd/coredump# export DEBUGINFOD_URLS="https://debuginfod.debian.net; root@karita:/var/lib/systemd/coredump# coredumpctl debug PID: 61726 (ntpd) UID: 110 (ntpsec)

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

2023-06-28 Thread Richard Laager
On 2023-06-28 20:14, forest.ow...@riseup.net wrote: On 2023-06-28 02:39, Richard Laager wrote: The original submitter replied off the tracker (probably by accident). I'll summarize here. The ntp.conf he included is the stock ntp.conf. He indicated he will try to get a backtrace. I'm trying

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

2023-06-28 Thread forest . owlet
On 2023-06-28 02:39, Richard Laager wrote: > The original submitter replied off the tracker (probably by accident). I'll > summarize here. > > The ntp.conf he included is the stock ntp.conf. > > He indicated he will try to get a backtrace. I'm trying to setup ntpsec to get a backtrace. I

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

2023-06-27 Thread Richard Laager
The original submitter replied off the tracker (probably by accident). I'll summarize here. The ntp.conf he included is the stock ntp.conf. He indicated he will try to get a backtrace. -- Richard

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

2023-06-26 Thread Richard Laager
I'm not sure if you saw this, as he didn't send it directly to you, but Matt Selsky asked: > Can you please share your ntp.conf or if there's a particular server > that seems to cause this segfault so that we can try to reproduce it? Also, can you get a stack trace? There are some instructions

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

2023-06-17 Thread R.L. Nicholas
Package: ntpsec Version: 1.2.2+dfsg1-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: forest.ow...@riseup.net Dear Maintainer, I updated the Debian release from bullseye to bookworm. With that update the ntp package (ntpd 4.2.8p15) was replaced by ntpsec. The ntpsec