Re: sshd Connection Failures - 2 June Snapshot (amd64)

On Sun, Jun 5, 2016 at 7:40 AM, Alex Greif wrote: [...] > hash mismatch > debug1: ssh_rsa_verify: signature incorrect > key_verify failed for server_host_key Thanks for the report. We believe we've identified the problem and backed out the offending commit in

Re: FOSS tools for flashing motherboard BIOS?

> Are you sure there is no iso image with self boot and update, ready to > be burned on a cdrom? I don't know for sure, but I think last time I > was using that. I don't own HP gear, but IBM/Lenovo has this kind of > iso image and I've used it a lot. Not as far as I can tell, and the guy at HP

Re: [pf] NAT64 rule for *outgoing* packets

Follow-up: This rule matches outgoing packets to nat64 well-known prefix 64:ff9b::/96: pass out quick on $if_wan inet6 from $if_wan:network to 64:ff9b::/96 af-to inet from ($if_wan) Echo requests do leave $if_wan with translated address family, replies show up in tcpdump on $if_wan:

Re: SYN_RCVD

On 06/07/16 15:33, Claudio Jeker wrote: > On Tue, Jun 07, 2016 at 09:35:39AM +0200, Peter J. Philipp wrote: >> On 06/06/16 21:57, Claudio Jeker wrote: >>> OpenBSD uses the syncache for TCP sockets in the 3 way handshake to save a >>> lot of work to create a full socket in case of synfloods, etc.

Re: SYN_RCVD

On Tue, Jun 07, 2016 at 09:35:39AM +0200, Peter J. Philipp wrote: > On 06/06/16 21:57, Claudio Jeker wrote: > > OpenBSD uses the syncache for TCP sockets in the 3 way handshake to save a > > lot of work to create a full socket in case of synfloods, etc. > > These unhatched sockets do not show up

Re: SYN_RCVD

> >> OpenBSD uses the syncache for TCP sockets in the 3 way handshake to save a > >> lot of work to create a full socket in case of synfloods, etc. > >> These unhatched sockets do not show up in the netstat output. Maybe they > >> should be added but this is the first request that asks for them in

Re: SYN_RCVD

On 07/06/16 10:35, Peter J. Philipp wrote: On 06/06/16 21:57, Claudio Jeker wrote: OpenBSD uses the syncache for TCP sockets in the 3 way handshake to save a lot of work to create a full socket in case of synfloods, etc. These unhatched sockets do not show up in the netstat output. Maybe they

[pf] NAT64 rule for *outgoing* packets

Hi, my setup: [host]--[router]--[internet] [Host] can ping legacy internet hosts via NAT64. Works fine. Corresponding line in pf.conf reads: pass in quick on $if_lan inet6 from $if_lan:network to 64:ff9b::/96 af-to inet from ($if_wan) However, [router] can not ping legacy internet hosts via

Re: SYN_RCVD

On Tue, Jun 7, 2016 at 3:35 AM, Peter J. Philipp wrote: > Thanks for the history of this Claudio. I am not really asking for them > I just wanted to know where they went. It's good to know that a > LISTENING tcp socket goes directly to ESTABLISHED in OpenBSD. I would > have

Re: openbsd book references

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Francois ... Not mine... i collaborate ;) "Bienvenue" > > i am also glad i found stephane huc's site. > > best regards to all, > > francois > - -- ~ " Fully Basic System Distinguish Life! " ~ " Libre as a BSD " +=<<< - Stephane

Re: Joining bridge(4) changes broadcast?

On 07/06/16(Tue) 12:36, Masao Uebayashi wrote: > On Mon, Jun 06, 2016 at 12:50:04PM +0200, Martin Pieuchot wrote: > > On 06/06/16(Mon) 16:23, Masao Uebayashi wrote: > > > On Mon, Jun 06, 2016 at 08:50:49AM +0200, Martin Pieuchot wrote: > > > > On 06/06/16(Mon) 13:04, Masao Uebayashi wrote: > > > >

Re: SYN_RCVD

On 06/06/16 21:57, Claudio Jeker wrote: > OpenBSD uses the syncache for TCP sockets in the 3 way handshake to save a > lot of work to create a full socket in case of synfloods, etc. > These unhatched sockets do not show up in the netstat output. Maybe they > should be added but this is the first