>Expires February 2036 minus the current date
>is about 12 years and 5 months maybe ish...
The context is a duration of time rather than time of day. eg the result of
sub_tspec() How many seconds did it take to do X? The current date has
nothing to do with it.
--
These are my
James Browning said:
> The NTP solution would be to convert the mess to l_fp which
> will work for a bit less than 13 years.
Thanks. l_fp is the right answer.
How did you get 13 years? I get 136. Did you drop/typo the 6?
> My joke would be to have it as a long long of micro-seconds which
I just pushed the first cut.
No documentation yet.
Like sysstats and usestats, ntsstats and ntskestats get logged every hour.
If you look at the output from ntpq -c nts, the counters fall into two clumps,
one for NTS and one for NTS-KE. All the counters get logged in the same order.
Should
e behavioral databases are compiled and analytical
methods are developed.
Hal Whitehead, Dalhousie University (hwhit...@dal.ca)
___
MARMAM mailing list
MARMAM@lists.uvic.ca
https://lists.uvic.ca/mailman/listinfo/marmam
Windows feature that resets system clocks based on random data is wreaking
havoc
https://arstechnica.com/security/2023/08/windows-feature-that-resets-system-c
locks-based-on-random-data-is-wreaking-havoc/
Windows Secure Time Seeding resets clocks months or years off the correct time.
That's
> To receive first an email requesting you to confirm your address, only to
> next receive another email from them with the actual information? That seems
> over-engineered...
How often is it only one message? I typically get 3, often 4 sometimes even 5:
we got your order
we shipped it
it
https://bugs.kde.org/show_bug.cgi?id=472677
Hal changed:
What|Removed |Added
CC||hmeye...@comcast.net
--
You are receiving this mail
James Browning said:
> If the project is sleeping, then you may as
>well cut the new release now.
I think we should do a normal release. That includes scanning the issues and
merge requests. And lots of testing.
I'm working on making a couple of new stats files for NTP packets using NTS
ntpd/ntp_parser.y has this line:
%token T_Timingstats
T_Timingstats is never defined. All the other similar tokens are defined in
ntpd/keyword-gen.c
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
Should that also go to users@ and devel@?
What fraction of people on users or devel are also on announce?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
in open-source firmware/devices. You will have a bad time.
Regards,
Hal
On Fri, Jul 28, 2023 at 10:50 AM Zeh, Werner via coreboot
wrote:
>
> Hi Carl-Daniel.
>
> We had an issue with Cisco Meraki last year (see [1]) where it turned out
> that at least their MX84 and MX250 switches ru
Thanks Gary and Fred.
I found it in ~/.gitconfig
It would have taken me a long long long time to look there.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
git log on a fresh clone shows things like this:
Author: Hal Murray
Date: Tue Jul 4 15:16:47 2023 -0700
Squash warnings about not handled enumeration
I haven't used that email in ages. My profile has been updated. Mail from
gitlab goes to the right place.
Where is the other address
> On Jul 19, 2023, at 11:18 AM, Hal Kierstead via lyx-users
> wrote:
>
>
>
>> On Jul 19, 2023, at 9:57 AM, Axel Dessecker wrote:
>>
>> Am Mittwoch, 19. Juli 2023, 16:12:20 CEST schrieb Hal Kierstead via
>> lyx-users:
>>> All -
>&g
> On Jul 19, 2023, at 9:57 AM, Axel Dessecker wrote:
>
> Am Mittwoch, 19. Juli 2023, 16:12:20 CEST schrieb Hal Kierstead via lyx-users:
>> All -
>>
>> I am trying to follow these instructions from the UserGuide, but the
>> character I should enter is undef
font and spacing!
I am using LyX 2.3.7 on maxOS 13.7.1(c)
Thanks,
Hal--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users
On Tue, 11 Jul 2023 11:09:23 +0200, Torsten Duwe wrote:
> On Fri, 7 Jul 2023 18:50:06 +0800
> Hal Feng wrote:
>
>> The clock dt-bindings and DT nodes are not consistent with Linux now.
>> Let's sync them with Linux, so the same dtb can work for Linux & U-Boot.
&g
From: Xingyu Wu
Add child node about PLL clock controller in sys_syscon node.
Signed-off-by: Xingyu Wu
Signed-off-by: Hal Feng
---
arch/riscv/dts/jh7110.dtsi | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/riscv/dts/jh7110.dtsi b/arch/riscv/dts/jh7110.dtsi
From: Xingyu Wu
Drop the PLL part in SYSCRG driver and separate to be a single
PLL driver of which the compatible is "starfive,jh7110-pll".
Signed-off-by: Xingyu Wu
Signed-off-by: Hal Feng
---
drivers/clk/starfive/clk-jh7110-pll.c | 86 +--
drivers/clk/st
From: Xingyu Wu
Modify the drivers to add of_xlate ops and transform clock id.
Signed-off-by: Xingyu Wu
Signed-off-by: Hal Feng
---
drivers/clk/starfive/clk-jh7110-pll.c | 29 ++-
drivers/clk/starfive/clk-jh7110.c | 287 +-
drivers/clk/starfive/clk.h
From: Xingyu Wu
The clock id needs to be changed to be consistent with Linux.
Signed-off-by: Xingyu Wu
Signed-off-by: Hal Feng
---
.../dt-bindings/clock/starfive,jh7110-crg.h | 101 +-
1 file changed, 51 insertions(+), 50 deletions(-)
diff --git a/include/dt-bindings/clock
From: Xingyu Wu
Change the PLL clock source from syscrg to sys_syscon child node.
Signed-off-by: Xingyu Wu
Signed-off-by: Hal Feng
---
arch/riscv/dts/jh7110-starfive-visionfive-2.dtsi | 6 +++---
arch/riscv/dts/jh7110-u-boot.dtsi| 1 -
arch/riscv/dts/jh7110.dtsi
The clock dt-bindings and DT nodes are not consistent with Linux now.
Let's sync them with Linux, so the same dtb can work for Linux & U-Boot.
To achieve this goal, the PLL clock driver is separated and some clock
IDs conversion is needed in clock drivers.
For the motivation, please see the
>
I linked above has a subsection entitled "Example of joining page_ids and
titles to wikidata QID" that shows how you can retrieve a set of QIDs
manually for a given page ID or title. Hope this helps get you started!
Thanks again,
Hal
On Sun, Jun 25, 2023 at 4:30 PM Kai Zhu wrote:
> Even traditional data centers have not been known to be especially
> considerate about scheduling their -loud- genset tests. Doesn't matter so
> much in the middle of an industrial zone but when you do it near where people
> live you're going to make them angry.
Why are gensets loud?
Is
> That usually means there is no "default:" case in a switch.
OK, but where did the unity code come from and/or have we cloned it or are we
tracking what they do? Or ...
--
These are my opinions. I hate spam.
___
devel mailing list
Is anybdy familiar with this area?
Is this something I did? Or are others seeing the same problem?
(I might have turned on some more-warnings flag, but I don't think so.)
../../tests/unity/unity.c:984:5: warning: enumeration value
\u2018UNITY_FLOAT_INVALID_TRAIT\u2019 not handled in switch
Gary said:
> Weird... Since ttyACM0 is USB, maybe a driver thing.
Yes, I'm using the USB port rather than the serial port.
The question is: Which driver? Linux or U-Blox?
--
These are my opinions. I hate spam.
___
devel mailing list
Gary said:
> To open to read binary:
> tty = open("/dev/ttyACM0", "rb")
> The line will be binary. Getting just the NMEA out will be fun.
Thanks. That's what I needed.
There is no problem getting just the NMEA. I'm using isASCII to detect the
garbage cases.
I get things like:
### Not
Can somebody give me a lesson on this area?
The code is:
tty = open("/dev/ttyACM0")
forever:
line = tty.readline()
a) How do I read mostly ASCII without crashing when there is non-ASCII?
b) Why is a u-Blox LEA-M8T sending me non-ASCII crap?
This is coming from the USB port. It's
Perl and bash are different scripting languages. They both have their strong points, and both have their weaknesses. (Sent from iPhone, so please accept my apologies in advance for any spelling or grammatical errors.)On May 3, 2023, at 12:06 AM, Claude Brown via beginners wrote:
> Can
By Alan L Donovan and Brian W Kernighan
350+ pages
In case you didn't notice, that's the K of K
I don't know anything about Go, yet, but I like books. This is a good one.
I flipped around, reading a paragraph or a page or two. It feels good. Lots
of examples. The text is easy to read and
I took a scan at the code. It's pretty broken. It won't be a quick fix.
Given how broken the code is, this seems to be the first time anybody has
tried to use that feature. :) [If there were others, they didn't bother to
tell anybody.]
Can we get a packet trace of a working example?
I
Thanks Pete. It was a memorable time... I had a Slackware distribution
in the late 1990's. Still have the multi-cd distribution medium.
-Hal Thorne
On 4/15/2023 7:51 AM, brad--- via TriEmbed wrote:
I started around '97. There was a distro that came on a bajillion
floppies. Good stuff
> one is to append '||cat build/config.log' to lines 386 and 402 (ish) of
> .gitlab-ci.yml
Worked. Thanks.
err: ../../test.c:3:10: fatal error: 'openssl/opensslv.h' file not found
#include
--
These are my opinions. I hate spam.
___
devel
I merged James' latest version for printing out the OpenSSL version during
configure.
It barfs on macos.
https://gitlab.com/NTPsec/ntpsec/-/jobs/4105995926#L126
The log file says:
Checking for OpenSSL != 1.1.1a : yes
OpenSSL version
>> For a small project, I think we should make mode6/ntpq require the cookie on
>> everything but getting the cookie, and we should make sure that there is no
>> amplification when getting the cookie.
> That would break compatibility with ntpq from classic NTP.
There are 2 areas I'm interested
[Context is a multi-threaded Go echo server]
> I can manage to do that.
I'll send you the C code off list.
Here is an outline of the big picture:
Linux and FreeBSD have a SO_REUSEPORT option. The idea is that you can open
several sockets on the same port number. The kernel will hash on
>Given that the things I have been turning in are not in the direction
>we are headed, what should I be working on? Other than trying to do a
>Golang port by myself, or revisiting the more than a-year-old list?
MR 1307 and/or 1309 is high on my list. I was hoping somebody else
Or interested in it?
I gave up a long time ago. It was too fiddly.
James has split the list of syscalls out from a list built into the source
(with a few ifdefs) to a text file. I think we will need a file for each
libc/kernel cross each hardware. But I think that gets us the right
Has anybody tried them?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
https://lists.ntpsec.org/mailman/listinfo/devel
h...@selasky.org said:
> A typical video stream of 4 MBit/s may produce on average 333 packets per
> second, and I ask a simple question if it is really needed to authenticate
> all of those packets while the user sits in a chair and eats popcorn?
Are you sure there is a user eating popcorn?
I was thinking that "latest" suggested newer. 3.1 is out, but none of the
distros I test with are using it yet. I was expecting a bug in that area.
It turns out that ubuntu-latest has an older version of OpenSSL 3. It's using
3.0.2. The oldest 3.0 I have is 3.0.3. Many distros are using
> I am reasonably sure about it. Jammy comes from [1] which come after looking
> at ./dockerfiles/ubuntu-latest to get ubuntu:latest
Thanks.
> Seriously though, docker works great for this, and you don't need to glass
> wipe a machine.
But I don't know anything about docker and I do know
James Browning said:
>> Where/how do I get ubuntu-latest?
> I would suggest `docker push registry.gitlab.com/na280/ntpsec`, but it seems
> that it rarely is acceptable, or go to the Ubuntu website and download Jammy.
Are you sure about Jammy? Where did that come from?
I found a download page
The pipeline fails on:
Name: ubuntu-latest-basic
Name: ubuntu-latest-refclocks
Name: macos-basic
Name: macos-refclocks
All 4 get the same clump of errors:
TEST(macencrypt, CMAC_Encrypt)../../tests/libntp/macencrypt.c:109::FAIL:
Expected TRUE Was FALSE
TEST(macencrypt,
dapter and cable, and a clean
install of MacOS Monterey.
Asking $350 or best offer.
--
Hal Widlansky
Salt Lake City, UT 84108
--
You received this message because you are a member of the LEM Swap group.
To post to this group, send email to lemswap@googlegroups.com
To unsubscribe, send an email *fro
dapter and cable, and a clean
install of MacOS Monterey.
Asking $400 or best offer.
--
Hal Widlansky
Salt Lake City, UT 84108
--
You received this message because you are a member of the LEM Swap group.
To post to this group, send email to lemswap@googlegroups.com
To unsubscribe, send an email *fro
needed for my setup anymore.
Asking $75 shipped in the US.
--
Hal Widlansky
Salt Lake City, UT 84108
--
You received this message because you are a member of the LEM Swap group.
To post to this group, send email to lemswap@googlegroups.com
To unsubscribe, send an email *from your subscribed a
richardcoch...@gmail.com said:
>> +NTOHS(atoi->type);
>> +NTOHS(atoi->length);
> These two lines are wrong. The net/host conversion of type and length
> already happened in suffix_post_recv() in msg.c
They may be wrong in the sense of duplicating work that has already been done,
but
I would like to hear the latest configurations for BIND to help with DDoS.
--
Hal King - h...@utk.edu
Systems Administrator
Office of Information Technology
Shared Services
The University of Tennessee
103c5 Kingston Pike Building
2309 Kingston Pk. Knoxville, TN 37996
Phone: 974-1599
[cid
Thanks.
matthew.sel...@twosigma.com said:
>> Should we document that? Where?
> The account creation seems self-explanatory. Or did you want to document
> something else?
I don't know. I was just tossing out a suggestion based on my stumbling.
Yes, it's reasonably obvious, but only after you
I took a look at the Coverity reports for ntpsec.
There are 10 of them. 10 is a small number. We should be able to fix them
all.
The Coverity report that started this thread was actually a bug.
The code I had was
bool once = false;
if (once) return;
once = true;
...
I was so
>> OK, I propose to turn on -Wswitch-enum and fix all the warnings I
>> find. Then I/we fix whatever Coverity complains about. If that is
>> too painful, we can back out of -Wswitch-enum.
> Seems good to me.
OK, I'll start working on it when I get time.
> There are so many Coverity warnings
Thanks.
> Do you have a coverity account?
> https://scan.coverity.com/
> Then go to "My Dashboard" and "Add project".
Should we document that? Where?
It looks like Coverity is running over on github.
Is our copy-to-github stuff documented?
I'm waiting for somebody to approve me.
>>
>> But then Coverity will barf (DEADCODE) at all the defaults.
> What purpose do they still have?
None. But we have -Wswitch-default so it will barf if we remove them.
They would be useful if an illegal value was passed in. At least in the case
that started this thread, the values are
> Sadly some compilers will always complain if there is no default. So I
> always add a default.
We turn on -Wswitch-default
I'd like to turn on -Wswitch-enum
That generates a handful of warnings that I'm willing to fix.
But then Coverity will barf (DEADCODE) at all the defaults.
I think
1439 default: {
1440/* There should be a way for the compiler to check this. */
1441 bool once =3D false;
>>> CID 435753: Possible Control flow issues (DEADCODE)
>>> Execution cannot reach this statement: "return;". =20
1442 if
James Browning said:
>> How about fixing the bug at ithe source rather than patching around it?
> I tried and failed then I came up with that.
Did you get O_NONBLOCK turned on?
Something like this:
err = fcntl(sockfd, F_SETFL, O_NONBLOCK);
--
These are my opinions. I hate spam.
James Browning said:
> I found a problem with input_handler(). If a reference clock passes a
> blocking file descriptor, input_handler can block forever.
Who did that? Which driver?
How about fixing the bug at ithe source rather than patching around it?
--
These are my opinions. I hate
> Clock variables seem not to be working.
Thanks. I don't use that stuff much so didn't test it enough.
> Also sys_var_list outputs the daemon_version variable.
That's one of the rough edges that I fixed. It's been there forever. Now you
see it.
You can also see it with:
rv 0
> On Feb 3, 2023, at 9:06 AM, Pavel Sanda wrote:
>
> On Fri, Feb 03, 2023 at 08:55:09AM -0700, Hal Kierstead wrote:
>>> On Fri, Feb 03, 2023 at 08:34:19AM -0700, Hal Kierstead via lyx-users wrote:
>>>> I use this for most papers in the
> On Feb 3, 2023, at 8:16 AM, Pavel Sanda wrote:
>
> On Wed, Feb 01, 2023 at 04:13:32PM +0100, Jürgen Spitzmüller wrote:
>> Dear all,
>>
>> As you might know, LyX features a theorem type "Acknowledgment" via the
>> "AMS extended" theorems modules. This is a question for people using
>> this.
ntp_control is the code in ntpd that processes mode6 requests from ntpq.
There are 3 types of variables you can read:
global variables (rv 0)
peer (server) variables
refclock variables
I've fixed up the first type. It is now easy to add new global variables.
Most will be a 1 line edit.
Your current code has 2 1/2 memory barriers. That's the same as my 2 counter
proposal.
As long as we are mucking in this area, should we take the opportunity and do
a big jump and convert to a new way of doing things?
Support old and new SHM until we can drop old.
Use 2 counters, read
The 31 bit idea seems strange/ugly to me. How did you decide to do it that
way?
Why is it better than 32 unsigned bits? Is there some case that works with 31
bits that breaks with 32?
I think there is a case that works for 32 unsigned that doesn't work for 31.
Consider code that gets
g...@rellim.com said:
> Sadly, that no longer works on modern CPUs with out of order execution.
> Unless wrapped in a mutex, or atomic, and that is now a no-no.
Do you have a good reference for that?
I'd like something like a nice blog article that explains things.
What is the new/wonderful
Could you explain the process of checking the signature to me, or point me to
an explanation.
Thanks,
Hal
> On Jan 19, 2023, at 2:21 PM, Richard Kimberly Heck wrote:
>
> I guess you have to accept the trust thing. We do not have the ability to
> sign packages for Windows. But y
Anybody recognize this tangle?
I have several machines running FreeBSD 13.1 but only one of them gets that
warning. It gets 7 copies of it, all from
/usr/local/ssl/include/openssl/crypto.h
Ahhh That system is running OpenSSL 3.1.0-beta1
In file included from
the icon, QS sort of freezes up for 5-10 seconds, then the icon will follow the
pointer with a lot of lagging, then when I drop the icon on a new location, it
flies back to the first QS pane.
Anyone having an issue like this?
Hal
Quicksilver 2.4.0
MBPro late 2016
MacOS 12.6.2
--
You received
Does this problem go away (for another 68 years) if on 32 bit systems,
we change the time_t in SHM to uint32_t?
The SHM layout stays the same so all combinations of old/new will continue to
work today.
When the top bit turns on in 2038, recent builds will fill with 0s rather than
sign
Greg via Gary said:
> Does Linux version syscalls? In NetBSD, we change the codepoints when the
> ABI changes, and there is kernel code to implement the old codepoint (but no
> header support) so old binaries still work. I think Solaris does this too.
They do something like that. I'm not
g...@rellim.com said:
> Recent glibc (2.34 and up) and recent Linux kernels, allow 64 bit time_t on
> 32-bit Linux without much work.
> But...
> How to get that 2038 compatible time to ntpd and chronyd? That is a much
> bigger problem.
> This is a problem for glibc on 32 bits. And int is
If we make any changes to SHM, we should switch to a setup where the memory is
read only. The idea is to allow multiple readers.
The trick to implementing that is to have 2 counters.
X and Y are initialized to the same value.
The writer bumps X, updates the data, then bumps Y.
The
Thank you very much. I forgot about rndc stats
--
Hal King - h...@utk.edu
Systems Administrator
Office of Information Technology
Shared Services
The University of Tennessee
103c5 Kingston Pike Building
2309 Kingston Pk. Knoxville, TN 37996
Phone: 974-1599
[cid:d47c2196-1345-4deb-b3ea
That's not bad idea.
--
Hal King - h...@utk.edu
Systems Administrator
Office of Information Technology
Shared Services
The University of Tennessee
103c5 Kingston Pike Building
2309 Kingston Pk. Knoxville, TN 37996
Phone: 974-1599
[cid:f2542891-ff64-48e7-b76e-8dcf8558e0d7
I need to find some answers like queries per second. Any fast ideas folks?
--
Hal King - h...@utk.edu
Systems Administrator
Office of Information Technology
Shared Services
The University of Tennessee
103c5 Kingston Pike Building
2309 Kingston Pk. Knoxville, TN 37996
Phone: 974-1599
I'm cleaning up ntp_control, the code in ntpd that supports ntpq.
My main goal is to make it easy to add new variables.
I'm setting things up so that each variable you might want to read needs one
line in a table. For the common data types, a macro will setup that line with
reasonable type
for the bare
drive.
Ships with just the bare SSD, ready to drop into your laptop. Install in a Pro
or Air is about a 5 minute job.
Asking $100.
--
Hal Widlansky
Salt Lake City, UT 84108
--
You received this message because you are a member of the LEM Swap group.
To post to this group, send email
Fred Wright said:
> If you make it 24 hours, there's the question of whether that means 86400
> seconds or 86401. :-)
That ones easy. It's 86400 smeared seconds and 86401 real seconds.
That's the whole point of smearing. :)
--
These are my opinions. I hate spam.
Fred Wright said:
> Any sane implementation of NTP ought to perform all synchronization on the
> TAI timescale, with conversions between TAI and UTC being part of the I/O.
> Using leap-smeared time on the wire makes this mapping inconsistent.
I agree, but most of the world is stuck with POSIX
Fred Wright said:
> IIRC you put in a Linux-specific hack to allow building against a
> non-default OpenSSL, but it's not very general. If it were fixed to honor
> pkgconfig (which is nontrivial to do correctly), then on any platform all
> one would have to do for an alternate OpenSSL is to
that I can see.
It’s in a clear shell case and has a palmrest protector installed.
It will ship with the hard shell case, a Speck rigid sleeve case for travel,
and a Magsafe 2 AC adapter.
Asking $350 or best offer
--
Hal Widlansky
Salt Lake City, UT 84108
--
You received this message because
> What I'm against is blanket forbidding of FFDHE in TLSv1.2.
The subject says "deprecate". That seems to have caused much of the
discussion.
Would a BCP be a better approach? That might provide a good setting to
discuss the issues. There is no reason to limit a BCP to TLSv1.2 or FFDHE.
> I guess if you don't see the issue I'll have to look more closely; I thought
> you might "just know" the problem.
Does git head work on 3.0?
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
f...@fwright.net said:
> It's 1.1.1s, which is the latest 1.1. I don'think there's anything
> nonstandard besides using versioned install locations so that multiple
> versions can be installed side-by-side.
I poked around some more. I have it building and running on several boxes
using
Richard Laager said:
> I was asked to enable it in Debian, but I did not.
> Note that my understanding was that "enable" meant "compile in the support
> such that users could choose to enable it in the config" not "enable it by
> default".
That would be my expectation. I haven't explored
> but if breaking OpenSSL 1.1 was unintentional, then it needs to be fixed
I'm not aware of any intententional breakage. I'm pretty sure we would have
done it at configure time.
I have git head building on several older systems that are still using 1.1
I'm pretty sure that at least one of
Does anybody use it?
Do any distros build with it enabled?
Should we add an "#warn untested" to the code?
static void
leap_smear_add_offs(l_fp *t) {
t += leap_smear.offset;
}
clang 13 points out:
../../ntpd/ntp_proto.c:2210:27: warning: parameter 't' set but not used
ay_>
or
pageviews.wmcloud.org) to get a sense of the data. I'll be sure to reach
back out once the differentially-private data is released so that you might
be able to check on the relevant pages!
Thanks again for reaching out :)
Hal
On Wed, Dec 21, 2022 at 12:07 PM Dan Andreescu
wrote:
> The
> `curl -o waf https://waf.io/waf-2.0.24` The link on the page said 2.0.23 .
Thanks. Your email said 23 and the text on the waf page said 23 so I hacked
the URL to get 23 which didn't work for me.
Matt has installed 24 which works.
--
These are my opinions. I hate spam.
Merry Christmas! Make sure it is not a transient antenna condition. A solid
state amp is going to detect faults rather quickly. A lot of a log
SWR/Wattmeters may not see these same faults….
> On Dec 19, 2022, at 8:51 PM, Jack Brindle via Elecraft
> wrote:
>
> What is the fault? We see a lot
Received: from mx.ntpsec.org (mx.ntpsec.org [140.211.9.57])
by a.mx.sonic.net (8.14.7/8.14.7) with ESMTP id 2BKAJEQH075190
(version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128
verify=NOT)
for ; Tue, 20 Dec 2022 02:19:16 -0800
Received: from lists.ntpsec.org
> Bumping waf (2.0.23 tested) resolves this, and it only happens for the
> extension because, for some raisin, waf is outputting to the wrong file name
> of ntpc rather than ntpc.cpython-311-x86_64-linux-gnu.so , go figure.
> The default of the FFI library + ctypes is unaffected.
Anybody remember this area?
With a fresh clone on Fedora which uses
Python 3.11.0
test-all/test.log:Trouble with test-all
Looking in test-all/test.log
The build looks clean. It dies in the checking that all the programs run well
enough to print their version info:
running:
on my desk hooked up to a Thunderbolt Display, and hasn’t traveled
much.
It works great, looks great, and is very fast with the 16GB of ram and the
upgraded SSD.
It will ship with the laptop in the hard shell case and an Apple Magsafe 2 AC
adapter.
Asking $600 or best offer.
--
Hal Widlansky
> The commit message for that is lacking the blank line after the summary
> line. This means that some git tools treat the entire commit message as the
> summary, creating obnoxiously long lines in their output. It's too late to
> fix the existing commit message without a forced update, but
I just pushed code to save 10 NTS keys used to make cookies.
That will let clients that only probe once a day work without
going back to NTS-KE to get new cookies.
I don't expect troubles, but please test.
The old code only saved 2 keys, the current one and the previous one. Keys
are rotated
say...@gmail.com said:
> For my part, I'm sick of "IoT" or "SCADA" or "embedded" vendors just
> endlessly keeping old cipher suites alive. The unwise cost-cutting in those
> areas does not constrain the rest of the internet.
Agreeded, but the software maintainers can't just drop support for X
101 - 200 of 27099 matches
Mail list logo
