Re: Possible break-in attempt?

2018-07-21 Thread Chad Jacob Milios
> On Jul 20, 2018, at 3:05 PM, Jamie Landeg-Jones wrote: > > Dimitry Andric wrote: > >> For each incoming IP address, sshd does a reverse lookup, and if that >> results in a hostname, it does another lookup of that hostname, to see >> if *that* result matches the original incoming IP address.

Re: Possible break-in attempt?

2018-07-21 Thread Grzegorz Junka
On 21/07/2018 11:03, Chad Jacob Milios wrote: On Jul 20, 2018, at 3:05 PM, Jamie Landeg-Jones wrote: Dimitry Andric wrote: For each incoming IP address, sshd does a reverse lookup, and if that results in a hostname, it does another lookup of that hostname, to see if *that* result matches th

Re: Possible break-in attempt?

2018-07-21 Thread Chad Jacob Milios
> On Jul 21, 2018, at 7:57 AM, Grzegorz Junka wrote: > On 21/07/2018 11:03, Chad Jacob Milios wrote: >>> On Jul 20, 2018, at 3:05 PM, Jamie Landeg-Jones wrote: >>> >>> Dimitry Andric wrote: >>> For each incoming IP address, sshd does a reverse lookup, and if that results in a hostnam

Re: Possible break-in attempt?

2018-07-21 Thread Grzegorz Junka
On 21/07/2018 12:05, Chad Jacob Milios wrote: On Jul 21, 2018, at 7:57 AM, Grzegorz Junka wrote: On 21/07/2018 11:03, Chad Jacob Milios wrote: On Jul 20, 2018, at 3:05 PM, Jamie Landeg-Jones wrote: Dimitry Andric wrote: For each incoming IP address, sshd does a reverse lookup, and if that

Re: Possible break-in attempt?

2018-07-21 Thread Miroslav Lachman
Grzegorz Junka wrote on 2018/07/21 21:29: [...] There is no point to this foolishly alarming message. Be mindful of the OTHER ways you must surely have in place to keep your sshd hard against attack. Good to know. But the documentation says setting to no prevents from using DNS in known_hos

Re: Possible break-in attempt?

2018-07-21 Thread Dimitry Andric
On 21 Jul 2018, at 21:29, Grzegorz Junka wrote: > > On 21/07/2018 12:05, Chad Jacob Milios wrote: >>> On Jul 21, 2018, at 7:57 AM, Grzegorz Junka wrote: >>> On 21/07/2018 11:03, Chad Jacob Milios wrote: > On Jul 20, 2018, at 3:05 PM, Jamie Landeg-Jones wrote: ... openssh-portable (in p

Re: Possible break-in attempt?

2018-07-21 Thread Grzegorz Junka
On 21/07/2018 19:59, Miroslav Lachman wrote: Grzegorz Junka wrote on 2018/07/21 21:29: [...] There is no point to this foolishly alarming message. Be mindful of the OTHER ways you must surely have in place to keep your sshd hard against attack. Good to know. But the documentation says sett

Re: Possible break-in attempt?

2018-07-21 Thread John-Mark Gurney
Dimitry Andric wrote this message on Sat, Jul 21, 2018 at 22:30 +0200: > On 21 Jul 2018, at 21:29, Grzegorz Junka wrote: > > > > On 21/07/2018 12:05, Chad Jacob Milios wrote: > >>> On Jul 21, 2018, at 7:57 AM, Grzegorz Junka wrote: > >>> On 21/07/2018 11:03, Chad Jacob Milios wrote: > > On J

Re: Possible break-in attempt?

2018-07-21 Thread Garrett Wollman
< said: > It's from 11.1-RELEASE-p1. I would hope that 11.1p1 is more correct than > 10.4? No, 11.1 predates 10.4. -GAWollman ___ freebsd-security@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, s

Archives of last quarterly package builds?

2018-07-21 Thread grarpamp
Packages are delivered via a single quarterly label here https://pkg.freebsd.org/FreeBSD:11:amd64/quarterly/ which corresponds to the latest quarterly branch label here https://svnweb.freebsd.org/ports/branches/?sortby=date#dirlist However, similar to how the tags here https://svnweb.freebsd.