Hi Todd,
On Mon, Jun 25, 2018 at 03:43:46PM -0600, Todd C. Miller wrote:
| Actually, it appears that the code accounts for which being one
| less. The problem is the additional linenum++ introduced in rev
| 1.64 along with the getline() changes. We should only be incrementing
| linenum for each
sunil+b...@nimmagadda.net wrote:
> sunil+b...@nimmagadda.net wrote:
> > >Synopsis: apmd(8) poll timer off by 10x
> > >Category: system
> > >Environment:
> > System : OpenBSD 6.3
> > Details : OpenBSD 6.3-current (GENERIC.MP) #54: Wed May 30 23:03:50
> > MDT 2018
> >
On Mon, 25 Jun 2018 22:19:11 +0200, Paul de Weerd wrote:
> As far as I can see, these are all caused by 'the internet' trying to
> log in: I've not had any problems with sshd misbehaving and when I log
> in no such warning is logged. It happened for 'Invalid user' (36x), 'Failed
> password' (8x),
Actually, it appears that the code accounts for which being one
less. The problem is the additional linenum++ introduced in rev
1.64 along with the getline() changes. We should only be incrementing
linenum for each suitable prime, not every line.
- todd
Index: usr.bin/ssh/dh.c
On Mon, 25 Jun 2018 22:19:11 +0200, Paul de Weerd wrote:
> It comes from this bit in usr.bin/ssh/dh.c:
>
> linenum = 0;
> which = arc4random_uniform(bestcount);
"bestcount" is always > 1, but "which" is in the range [0, bestcount)
where we really want it to be [1, bestcount]
I th
Hi all,
Since upgrading my SSH jump host to the latest snap two days ago, its
sshd has been logging these errors:
2018-06-25T19:47:35.716Z tuna.alm.weirdnet.nl tuna sshd[91261]: WARNING: line 6
disappeared in /etc/moduli, giving up
As far as I can see, these are all caused by 'the internet' try
On 2018/06/25 13:51, Albert Martinez wrote:
> Hi,
>
> Find attached the dmesg.
There might be some clues in "sh malloc" or "sh all pools" from ddb,
it would be worth fetching those too.
> Regarding the latest current install I do not see why it may help, we
> triggered the error with 5.9, 6.0,
Hi,
Find attached the dmesg.
Regarding the latest current install I do not see why it may help, we
triggered the error with 5.9, 6.0, 6.1, 6.2 and 6.3 why should be
different with the latest current?
Regards,
Albert Martinez
On 19/06/18 20:40, Hrvoje Popovski wrote:
> On 19.6.2018. 15:14, Alb
