On Wed, May 22, 2019 at 09:41:00PM -0400, Lawrence Teo wrote:
> This syncs the pf(4) man page with the latest net/pfvar.h (r1.490).
>
> ok?
no objections, thanks.
OK sashan
>
>
> Index: pf.4
> ===
> RCS file: /cvs/src/share/m
On Wed, May 22, 2019 at 08:05:50PM -0500, Katherine Rohl wrote:
> Hi,
>
> Adjusted NS8250 behavior in vmd(8) so it gets detected as an 8250 and not a
> 16450 by OpenBSD’s boot process. Also generalized some of the COM1-specific
> I/O address definitions to support adding COM2 (and COM3, and COM4
This syncs the pf(4) man page with the latest net/pfvar.h (r1.490).
ok?
Index: pf.4
===
RCS file: /cvs/src/share/man/man4/pf.4,v
retrieving revision 1.91
diff -u -p -r1.91 pf.4
--- pf.418 Feb 2019 13:11:44 - 1.91
++
Hi,
Adjusted NS8250 behavior in vmd(8) so it gets detected as an 8250 and not a
16450 by OpenBSD’s boot process. Also generalized some of the COM1-specific I/O
address definitions to support adding COM2 (and COM3, and COM4…) in the future.
Tested by logging into my VM with the virtual serial co
> Date: Wed, 22 May 2019 20:02:14 +0200
> From: Alexander Bluhm
>
> On Wed, May 22, 2019 at 05:54:35PM +0200, Mark Kettenis wrote:
> > Should we also fix biosboot? The machines that are affected are all
> > fairly recent and should boot using UEFI by default...
>
> If we change fewer things, we
> Date: Tue, 21 May 2019 21:04:33 +0200 (CEST)
> From: Mark Kettenis
>
> Logic error. If pa->pa_pmemex is NULL we want to try allocating from
> pa->pa_memex. But if both of them are NULL we need to assume that the
> provided base address is correct.
>
> ok?
patrick@ pointed out an issue with
On Wed, 22 May 2019, Mark Lumsden wrote:
Date: Wed, 22 May 2019 18:49:23 + (UTC)
From: Mark Lumsden
To: tech@openbsd.org
Subject: ssh-keygen: interactive comment change
I used the -C command line option of ssh-keygen to change the comment of a
public key and got confused with the output.
I used the -C command line option of ssh-keygen to change the comment
of a public key and got confused with the output. For example, if the
original comment was 'mark@home', this is what would happen trying to
amend the comment to 'mark@work' via -C:
$ ssh-keygen -f test_rsa -c -C mark@work
Ke
On Wed, May 22, 2019 at 08:02:14PM +0200, Alexander Bluhm wrote:
> On Wed, May 22, 2019 at 05:54:35PM +0200, Mark Kettenis wrote:
> > Should we also fix biosboot? The machines that are affected are all
> > fairly recent and should boot using UEFI by default...
>
> If we change fewer things, we ma
On Wed, May 22, 2019 at 05:54:35PM +0200, Mark Kettenis wrote:
> Should we also fix biosboot? The machines that are affected are all
> fairly recent and should boot using UEFI by default...
If we change fewer things, we may have less trouble for 6.4 and 6.5
errata.
Do we know any non-UEFI capabl
> Date: Wed, 22 May 2019 00:40:24 -0700
> From: Mike Larkin
>
> On Tue, May 21, 2019 at 12:33:24AM +0200, Mark Kettenis wrote:
> > > Date: Sat, 18 May 2019 05:58:39 +0200 (CEST)
> > > From: Mark Kettenis
> > >
> > > > Date: Fri, 17 May 2019 17:56:52 -0400
> > > > From: Patrick Wildt
> > > >
>
On 21/05/19(Tue) 20:41, Jasper Lievisse Adriaanse wrote:
> Hi,
>
> This appears to have been wrong from the import, the comment explaining why
> rtcdrain() is needed is in rtcstart() in the same file. OK?
I'd rather kill the reference. It will become outdated next time
somebody refactor the code
Regardless of the decision on which way the behavior should go, it is a
documentation bug either way. (E.g. beginning-of-buffer is missed
entirely). Probably my fault (from a lng time ago.)
On Wed, May 22, 2019 at 8:53 AM Leonid Bobrov wrote:
> On Wed, May 22, 2019 at 01:36:41PM +0200, Jerem
Hi,
unbound-checkconf(8) needs to chdir(2) and then open(2) the config file and
to call getpwnam(3). This means it needs to pledge for rpath and getpw, but
after calling getpwnam(3) the config file was already loaded so we can drop
both promises afterwards.
Comments? OK?
Index: unbound-checkconf
On Wed, May 22, 2019 at 01:36:41PM +0200, Jeremie Courreges-Anglas wrote:
> On Wed, May 22 2019, Leonid Bobrov wrote:
> > It seems that nobody cares about compatibility with GNU Emacs. Besides
> > this behaviour is annoying because when I set a mark, scroll a buffer,
> > and decide to go to the en
On Mon, Apr 15, 2019 at 04:56:52PM +0200, Stefan Sperling wrote:
> The ifconfig mode command is broken; It is supposed to force a wireless
> interface into 11a/b/g/n media mode. This stopped working some time ago,
> probably during my work on background scanning. Problem spotted by mlarkin@
> who n
On Wed, May 22 2019, Leonid Bobrov wrote:
> It seems that nobody cares about compatibility with GNU Emacs. Besides
> this behaviour is annoying because when I set a mark, scroll a buffer,
> and decide to go to the end of buffer that overwrites my mark and I have
> to start over. Also besides that
Hello,
First, sorry for double posting to misc@.
This is a short patch to let acme-client accept ECDSA keys now that
letsencrypt accepts signing certificates with those keys. This
functionality is present in certbot, so it might be a good idea to let
acme-client accept that too.
The key need
Hi,
Like we did on other daemons that cannot be pledged due to forbidden ioctls the
main process can be unveiled to restrict filesystem access. In this case we can
restrict it to only read, although it must be the entire / since the daemon is
able to include config files from anywhere.
Additional
It seems that nobody cares about compatibility with GNU Emacs. Besides
this behaviour is annoying because when I set a mark, scroll a buffer,
and decide to go to the end of buffer that overwrites my mark and I have
to start over. Also besides that you have to figure out this behavior
because manpag
On Tue, May 21, 2019 at 12:33:24AM +0200, Mark Kettenis wrote:
> > Date: Sat, 18 May 2019 05:58:39 +0200 (CEST)
> > From: Mark Kettenis
> >
> > > Date: Fri, 17 May 2019 17:56:52 -0400
> > > From: Patrick Wildt
> > >
> > > Hi,
> > >
> > > claudio@ has a Kaby Lake that exceeds the 128 kB limit,
21 matches
Mail list logo
