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 sense
for someone with a bunch of spare already-paid-for netwo
Gesendet: Mittwoch, 09. Mai 2018 um 21:25 Uhr
Von: "Jordan Geoghegan"
> I would recommend looking here to start:
> https://www.openbsd.org/faq/faq13.html
>
> You're going to have to configure sndiod to output to your secondary
> audio(4) device.
>
> To quote from the above faq link:
>
> "To change
On 2018-05-09, Leonid Bobrov wrote:
> Hi!
>
> From https://www.openbsd.org/anoncvs.html:
> CVSROOT=anon...@openbsd.park.rambler.ru:/cvs
> Location: Moscow, Russia.
> Maintained by Dmitry Alenichev.
> Protocols: ssh, ssh port 2022.
>
> mazocomp$ opencvs -d anon...@openbsd.park.rambler.ru:/cvs up
>
Recently I an interesting article on OpenBSD Journal
https://undeadly.org/cgi?action=article;sid=20180427124425
I had a question which is not addressed by man pages
https://man.openbsd.org/smtp.1
but I guess Eric and other developer familiar with code were busy
hacking new cool things.
I was w
Does this
https://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCVE-2018-8897
affect 6.3 stable?
Best,
Predrag
Where can I learn more about the work on the new lpd server aside of
reading the code? I learnt about it from the OpenBSD Journal
https://undeadly.org/cgi?action=article;sid=20180509184829
Thank you!
Predrag
Thank you for your answers.
I did a first test with exporting the variable and it worked fine.
Have a nice week
Le mercredi 9 mai 2018 à 16:17:01 UTC+2, Marc Espie a
écrit :
On Wed, May 09, 2018 at 01:08:49PM +, Mik J wrote:
> Thank you Martijn for this quick answer.So should I d
On Thu, May 10, 2018 at 10:22:48AM -0400, Predrag Punosevac wrote:
> Does this
>
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCVE-2018-8897
>
> affect 6.3 stable?
>
> Best,
> Predrag
>
OpenBSD is not affected.
-ml
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 causality that kept OpenBSD in the clear of this one
that made such headlines ye
On Thu, May 10, 2018 at 10:18:32AM -0400, Predrag Punosevac wrote:
>
> I was wondering if somebody could give me some insight into how is the
> new SMTP client related to OpenSMTPD?
>
Eric wrote code to simplify the SMTP client engine in OpenSMTPD and help
with the cleanup I mentionned at EuroBSD
On May 10, 2018 11:10 AM, Gilles Chehade wrote:
>
> On Thu, May 10, 2018 at 10:18:32AM -0400, Predrag Punosevac wrote:
> >
> > I was wondering if somebody could give me some insight into how is the
> > new SMTP client related to OpenSMTPD?
> >
>
> Eric wrote code to simplify the SMTP client engi
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, it
seems the snapshots packages were actually upd
On Thu, May 10, 2018 at 03:41:59PM +, Ken MacKenzie 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
Hello Mike,
>> OpenBSD does not allow userspace to access the hardware debug registers.
Does it mean that gdb and other debuggers can't use hardware breakpoints?
Then how do they implement memory watch?
AFAIK in other OSes they modify DR* registers using ptrace(2),
but "struct reg” from used by
Thank you. After many of the things I have read about OpenBSD being "overhyped"
online I thought this was a real interesting case that most of the industry gets
slapped with this the other day and OpenBSD is all fine and dandy.
I am glad to get the quantification as to why.
Ken
On Thu, May 10, 2
>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 causality that kept OpenBSD in the clear of this one
>that made such he
On Thu, May 10, 2018 at 5:06 PM, IL Ka wrote:
>
> >> OpenBSD does not allow userspace to access the hardware debug registers.
>
> Does it mean that gdb and other debuggers can't use hardware breakpoints?
>
Correct: gdb is a userspace program, so it can't set hardware breakpoints
on x86.
(I don't
On Thu, 2018-05-10 at 18:54 -0600, 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 jus
18 matches
Mail list logo
