On 2020-Jan-27, at 19:53, bob prohaska wrote:
> On Mon, Jan 27, 2020 at 06:22:20PM -0800, Mark Millard wrote:
>>
>> So far as I know, in the past progress was only made when someone
>> already knowledgable got involved in isolating what was happening
>> and how to control it.
>>
> Indeed. One c
On Mon, Jan 27, 2020 at 06:22:20PM -0800, Mark Millard wrote:
>
> So far as I know, in the past progress was only made when someone
> already knowledgable got involved in isolating what was happening
> and how to control it.
>
Indeed. One can only hope said knowledgeables are reading
Thanks
On 1/9/20 2:53 PM, Rick Macklem wrote:
John Baldwin wrote:
On 1/7/20 3:02 PM, Rick Macklem wrote:
Someone once told me they were working on a netgraph node that did TLS
encapsulation of a stream.
I can not remember who it was, but I do remember they were dubious
about being allowed to give
John Baldwin wrote:
>On 1/26/20 8:08 PM, Rick Macklem wrote:
>> John Baldwin wrote:
>> [stuff snipped]
>>> Hmmm, this might be a fair bit of work indeed.
>>>
>>> Right now KTLS only works for transmit (though I have some WIP for receive).
>>>
>>> KTLS does assumes that the initial handshake and key
On 2020-Jan-27, at 12:48, Cy Schubert wrote:
> In message , Mark Millard
> write
> s:
>>
>>
>>
>> On 2020-Jan-27, at 10:20, Cy Schubert wrote:
>>
>>> On January 27, 2020 5:09:06 AM PST, Cy Schubert
>> wrote:
> . . .
Setting a lower arc_max at boot is unlikely to help. Ru
In message , Mark Millard
write
s:
>
>
>
> On 2020-Jan-27, at 10:20, Cy Schubert wrote:
>
> > On January 27, 2020 5:09:06 AM PST, Cy Schubert
> wrote:
> >>> . . .
> >>
> >> Setting a lower arc_max at boot is unlikely to help. Rust was building
> >> on
> >> the 8 GB and 5 GB 4 core machines
On 2020-Jan-27, at 10:20, Cy Schubert wrote:
> On January 27, 2020 5:09:06 AM PST, Cy Schubert
> wrote:
>>> . . .
>>
>> Setting a lower arc_max at boot is unlikely to help. Rust was building
>> on
>> the 8 GB and 5 GB 4 core machines last night. It completed successfully
>> on
>> the 8 G
FreeBSD Project Quarterly Status Report - Fourth Quarter 2019
Here is the last quarterly status report for 2019. As you might
remember from last report, we changed our timeline: now we collect
reports the last month of each quarter and we edit and publish the full
document the next mon
On January 27, 2020 10:19:50 AM PST, "Rodney W. Grimes"
wrote:
>> In message <202001261745.00qhjkuw044...@gndrsh.dnsmgr.net>, "Rodney
>W.
>> Grimes"
>> writes:
>> > > In message <20200125233116.ga49...@troutmask.apl.washington.edu>,
>Steve
>> > > Kargl w
>> > > rites:
>> > > > On Sat, Jan 25, 2
On January 27, 2020 5:09:06 AM PST, Cy Schubert
wrote:
>In message <202001261745.00qhjkuw044...@gndrsh.dnsmgr.net>, "Rodney W.
>Grimes"
>writes:
>> > In message <20200125233116.ga49...@troutmask.apl.washington.edu>,
>Steve
>> > Kargl w
>> > rites:
>> > > On Sat, Jan 25, 2020 at 02:09:29PM -0800
> In message <202001261745.00qhjkuw044...@gndrsh.dnsmgr.net>, "Rodney W.
> Grimes"
> writes:
> > > In message <20200125233116.ga49...@troutmask.apl.washington.edu>, Steve
> > > Kargl w
> > > rites:
> > > > On Sat, Jan 25, 2020 at 02:09:29PM -0800, Cy Schubert wrote:
> > > > > On January 25, 2020
No, it's ok now. I didn't report it earlier, because I wasn't sure which
revision fixed it and jeff didn't reply.
On 20-01-26 16:27:35, Mark Millard wrote:
> Piotr Kubaj listy at anongoth.pl wrote on
> Thu Jan 16 19:56:11 UTC 2020 :
>
> > revision 356776 breaks booting for powerpc64 users. It r
On Mon, Jan 27, 2020 at 8:40 AM Freddie Cash wrote:
> On Sun, Jan 26, 2020 at 12:08 PM Rick Macklem
> wrote:
>
>> Oh, and for anyone out there...
>> What is the easiest freebie way to test signed certificates?
>> (I currently am using a self-signed certificate, but I need to test the
>> "real" v
On Sun, Jan 26, 2020 at 12:08 PM Rick Macklem wrote:
> Oh, and for anyone out there...
> What is the easiest freebie way to test signed certificates?
> (I currently am using a self-signed certificate, but I need to test the
> "real" version
> at some point soon.)
>
Let's Encrypt is what you are
In message <202001261745.00qhjkuw044...@gndrsh.dnsmgr.net>, "Rodney W.
Grimes"
writes:
> > In message <20200125233116.ga49...@troutmask.apl.washington.edu>, Steve
> > Kargl w
> > rites:
> > > On Sat, Jan 25, 2020 at 02:09:29PM -0800, Cy Schubert wrote:
> > > > On January 25, 2020 1:52:03 PM PST,
On 1/26/20 8:08 PM, Rick Macklem wrote:
John Baldwin wrote:
[stuff snipped]
Hmmm, this might be a fair bit of work indeed.
Right now KTLS only works for transmit (though I have some WIP for receive).
KTLS does assumes that the initial handshake and key negotiation is handled by
OpenSSL. OpenS
16 matches
Mail list logo