>
>
>> Then how do they implement memory watch?
>>
>
> Got me, but even the ancient, in-tree gdb is able to do so. Have you
> consulted the gdb source?
>
I read gdb sources and found an asnwer, but later I read docs and here it
is:
https://sourceware.org/gdb/onlinedocs/gdb/Set-Watchpoints.html
On Fri, May 11, 2018 at 08:53:18PM +, Stuart Henderson wrote:
> On 2018-05-10, Xiyue Deng wrote:
> > Hi,
> >
> > I noticed that a few days ago (maybe around Monday) the 6.3 release
> > page[1] has updated mips64el package count:
> >
> > mips64el: 8254
> >
> > A few days have passed however the
On Fri, May 11, 2018 at 08:20:24PM -, Christian Weisgerber wrote:
> On 2018-05-10, Xiyue Deng wrote:
>
> > I noticed that a few days ago (maybe around Monday) the 6.3 release
> > page[1] has updated mips64el package count:
> >
> > mips64el: 8254
>
> Sorry, these are indeed ready, but they ha
On 5:58PM, Thu, May 10, 2018 Theo de Raadt wrote:
>
> >Dare I ask what lead to OpenBSD not being affected.
> >
> >Sorry if it is a dumb question but since this hit FreeBSD as well I am
> >wondering
> >what OpenBSD did differently.
> >
> >Was this caught in an audit?
> >
> >I am just curious about
On 2018-05-10, Xiyue Deng wrote:
> Hi,
>
> I noticed that a few days ago (maybe around Monday) the 6.3 release
> page[1] has updated mips64el package count:
>
> mips64el: 8254
>
> A few days have passed however there is still no
> /pub/OpenBSD/6.3/packages/mips64el available[2]. In the meantime,
On 2018-05-10, Xiyue Deng wrote:
> I noticed that a few days ago (maybe around Monday) the 6.3 release
> page[1] has updated mips64el package count:
>
> mips64el: 8254
Sorry, these are indeed ready, but they haven't been uploaded to
the release directory yet.
--
Christian "naddy" Weisgerber
On 05/06/18 11:39, Stefan Sperling wrote:
> On Sat, May 05, 2018 at 11:03:52PM +0200, Riccardo Mottola wrote:
[…]
> A commit of mine accidentally broke WEP support back in August 2017.
> This was eventually fixed in -current 2 weeks ago. Nobody noticed
> that WEP was broken for 8 months...
[…]
On Fri, May 11, 2018 at 04:56:19PM +0200, Riccardo Mottola wrote:
> Is a backport possible to "stable"?
I don't think it is worth the effort for us.
You are literally the only person I know of who has requested an
official backport of this fix. WEP was already broken in OpenBSD 6.2
which was rele
Hi,
Stefan Sperling wrote:
The keyword 'nwkey' indicates you are using WEP. Is that correct?
Yes!
A commit of mine accidentally broke WEP support back in August 2017.
This was eventually fixed in -current 2 weeks ago. Nobody noticed
that WEP was broken for 8 months...
I did notice that ac
>At the end of a "pass" rule in pf.conf, the author adds:
>
> max‐src‐conn 3, max‐src‐conn‐rate 2/5, overload flush global
>
>which means:
>
> "any source can only have a total of three connections,
> and they may not create them at a rate faster than two
> every five minutes. If
I guess this is the main reason why we all love OpenBSD and an idea and a
philosophy (and people) behind this great OS!
- Bogdan
> On May 11, 2018, at 6:49 AM, andrew fabbro wrote:
>
> "A statement...was mishandled in the development of some or all
> operating-system kernels..."
>
> I think i
On Thu, May 10, 2018 at 9:36 AM, Stuart Henderson
wrote:
On 2018-05-10, Patrick Dohman wrote:
Incidentally why are there no African mirrors aka Kenya etc?
Nobody has offered one; a significant amount of traffic would be used
just keeping it up to date with snapshots, so it would only make
se
"A statement...was mishandled in the development of some or all
operating-system kernels..."
I think it's really "some" and the reason it's "some" and not "all" is
OpenBSD.
On Thu, May 10, 2018 at 9:51 PM, John Long wrote:
> On Thu, 2018-05-10 at 18:54 -0600, Theo de Raadt wrote:
> > > Dare I a
Hello,
I have working ikev2 tunnel between two virtual aliased subnets. But no
traffic over IPsec tunnel from $ext_if on server machine to $ext_if on
client machine and vice-versa. Both machines are using in production and
firewalled by PF.
# cat /etc/hostname.em1
### ser
14 matches
Mail list logo