e...@thyrsus.com said:
> I do. But I'm not worried that introducing NTS code will destablized non-NTS
> code, either.
It wouldn't surprise me if we used a routine that wasn't in older versions of
libssl.
--
These are my opinions. I hate spam.
Hal Murray :
>
> Eric said:
> > What would a build option gain us? Is there some specific prerequisite
> > you're worried about?
>
> It seemed like good insurance. If we want to fix a bug, you seem to prefer
> to
> release the current git head rather than making a branch.
I do. But I'm
Eric said:
> What would a build option gain us? Is there some specific prerequisite
> you're worried about?
It seemed like good insurance. If we want to fix a bug, you seem to prefer to
release the current git head rather than making a branch.
There is a specific example. Daniel's
Hal Murray via devel :
>
> To answer the question in the subject...
>
> I think we will want it in the short term in order to keep builds working on
> all current platforms until we get things sorted out.
What would a build option gain us? Is there some specific prerequisite you're
worried
To answer the question in the subject...
I think we will want it in the short term in order to keep builds working on
all current platforms until we get things sorted out.
--
These are my opinions. I hate spam.
___
devel mailing list
Eric S. Raymond via devel writes:
> Generally Mills's design choices can be described as...hm...quirky,
> but pretty tasteful and occasionally quite brilliant considering the
> technology constraints he was working under.
[…]
I get you really wanted to criticize mode 6 design decisions, but your
Hal Murray :
>
> > James, you are correct. Privileged ntpq functions require the crypto.
>
> Not quite.
>
> Privileged operations require a password, but it is sent in the clear. There
> is no crypto on that path. The packet format doesn't support it. We could
> fix that at the cost of
> James, you are correct. Privileged ntpq functions require the crypto.
Not quite.
Privileged operations require a password, but it is sent in the clear. There
is no crypto on that path. The packet format doesn't support it. We could
fix that at the cost of breaking compatibility.
The
James Browning via devel :
> > If we did away with shared key authentication, we could potentially do
> > away
> > with needing libcrypto. Aside from authentication, we also use
> > RAND_bytes()
> > so we would need to substitute something for that.
>
> Funny, I thought -lssl needed libcrypto as
On Wed, Jan 23, 2019, 3:07 AM Hal Murray via devel
> I'm thinking of updating INSTALL and/or devel/hacking.adoc to say
> something
> about pthreads and OpenSSL.
>
> If we did away with shared key authentication, we could potentially do
> away
> with needing libcrypto. Aside from authentication,
I'm thinking of updating INSTALL and/or devel/hacking.adoc to say something
about pthreads and OpenSSL.
If we did away with shared key authentication, we could potentially do away
with needing libcrypto. Aside from authentication, we also use RAND_bytes()
so we would need to substitute
11 matches
Mail list logo
