Re: more precise O_ACCMODE handling

On Mon, 4 May 2015, Miod Vallat wrote: > > > Index: libc/stdlib/posix_pty.c > > > === > > > RCS file: /cvs/src/lib/libc/stdlib/posix_pty.c,v > > > retrieving revision 1.1 > > > diff -u -p -r1.1 posix_pty.c > > > --- libc/stdlib/posix_

Re: sprinkle some symmetry on uvm_swap_encrypt

> SWAP_KEY_PUT calls swap_key_delete, while SWAP_KEY_GET inlines its > work. > > this shuffles it so the work is in uvm_swap_encrypt.c, and lets us > reduce the scope of some of the globals in uvm_swap_encrypt.c. > > ok? Hmm, I wonder if this was done to limit the amount of stack space we use

[PATCH] relayd.conf man page confusion

Fix a contradiction in the relayd.conf man page in the Protocols, tls section. The definition of TLS client and server is the opposite of what is stated in the "forward" and "listen on" descriptions, and the TLS Relays section. Tim. Index: relayd.conf.5 ==

sprinkle some symmetry on uvm_swap_encrypt

SWAP_KEY_PUT calls swap_key_delete, while SWAP_KEY_GET inlines its work. this shuffles it so the work is in uvm_swap_encrypt.c, and lets us reduce the scope of some of the globals in uvm_swap_encrypt.c. ok? Index: uvm_swap_encrypt.c ===

fifo_poll: use a_fflag to determine valid events

Now that we have a_fflag in struct vop_poll_args we can handle things like POLLOUT on a read-only fd more sensibly. Previously, any poll events could be used regardless of the actual file flags of the descriptor. Rather than call soo_poll() I've created a real fifo_poll() that checks the socket s

getprogname(3) manpage fix

Index: getprogname.3 === RCS file: /cvs/src/lib/libc/gen/getprogname.3,v retrieving revision 1.4 diff -u -p -r1.4 getprogname.3 --- getprogname.3 31 Jul 2013 16:43:27 - 1.4 +++ getprogname.3 4 May 2015 20:34:35 -00

Re: more precise O_ACCMODE handling

> > Index: libc/stdlib/posix_pty.c > > === > > RCS file: /cvs/src/lib/libc/stdlib/posix_pty.c,v > > retrieving revision 1.1 > > diff -u -p -r1.1 posix_pty.c > > --- libc/stdlib/posix_pty.c 3 Dec 2012 20:08:33 - 1.1 > > +++ li

Re: pckbc

On Mon, May 04, 2015 at 08:47:29PM +0500, Alexandr Shadchin wrote: > Less magic number > > For PS/2 - status byte - bit 5: > The bit is '1' if the data on input port 60h came from the AUX port, or '0' if > the data came from the keyboard or from the keyboard controller itself. > > KBS_TERR (kbd t

Re: more precise O_ACCMODE handling

On Sun, 03 May 2015 22:07:33 -0700, Philip Guenther wrote: > The flags passed to open(2) and openat(2) are not a simple bitset. > Instead, the bits in O_ACCMODE are effectively an enumeration, and the > other bits are or'ed onto that. > > For example, a function that wraps open(2), taking a fl

Re: seccomp system call

On Sun, 03 May 2015 20:44:25 -, Loganaden Velvindron wrote: > OpenBSD already has systrace. Last I checked, systrace doesn't work well with multi-threaded programs and was trivial to bypass. The basic design where you have a userland monitor process is flawed. Something where a policy is pu

Re: seccomp system call

On Mon, 04 May 2015 02:38:58 -0600, Theo de Raadt wrote: > Those policies will be wide open, or too strict. If we adopt this > into our world, the next step after that is going to be wide use of > #ifdef within bpf rulesets. I don't see how that follows. Security policies are going to be highly

pckbc

Less magic number For PS/2 - status byte - bit 5: The bit is '1' if the data on input port 60h came from the AUX port, or '0' if the data came from the keyboard or from the keyboard controller itself. KBS_TERR (kbd transmission error) was valid for AT-mode, but not for PS/2-mode. Comment ? OK ?

Re: [patch] security.html page

Hi Roman, Roman Kravchuk wrote on Sun, May 03, 2015 at 12:06:16PM +0300: > This patch for fix security.html page > - cleanup not found link to errata20.html > - add link to errata57.html Committed, thanks. Ingo > Index: security.html >

Re: [patch] rtl8188eu support for urtwn(4)

On Mon, May 04, 2015 at 01:23:59PM +0200, Stefan Sperling wrote: > On Mon, May 04, 2015 at 04:03:01PM +0300, Mikhail wrote: > > Hello, yes, this change, maybe harmless, but not accurate. I inline new > > patch against head with this change incorporated and with fix for USB > > aggregation mode, whi

Re: [patch] rtl8188eu support for urtwn(4)

On Mon, May 04, 2015 at 04:03:01PM +0300, Mikhail wrote: > Hello, yes, this change, maybe harmless, but not accurate. I inline new > patch against head with this change incorporated and with fix for USB > aggregation mode, which Kevin has pushed into FreeBSD[1] to fix > performance issues. > > [1]

Re: [patch] rtl8188eu support for urtwn(4)

On 20:20 26-Apr 2015 Stefan Sperling wrote: > The chunk below is wrong for OpenBSD since it sets the intitial transmit > rate to an 11n rate. 0x13 corresponds to the "MCS7" 11n rate, > see linux/drivers/net/wireless/rtlwifi/rtl8188ee/def.h enum rtl_desc92c_rate. > The value 11 corresponds to OFDM 5

Re: [PATCH] Man pages: usbd_open_pipe(9), usbd_close_pipe(9)

On 02/05/15(Sat) 08:44, attila wrote: > Hi tech@, > > This patch adds man pages for usbd_open_pipe, usbd_open_pipe_intr, > usbd_close_pipe and usbd_abort_pipe, done as two files: > usbd_open_pipe.9 and usbd_close_pipe.9. It also adds these two new .9 > files to the appropriate Makefile and tweaks

Re: seccomp system call

>> I am wondering if the seccomp system call [1] would be welcomed >> in the OpenBSD tree. I remember it was among the subjects of last >> year's Google Summer of Code. If there is still interest in having >> it implemented, I am willing to work on it: I have a diff that >> creates the system call

not all of uvm needs to see uvm_swap_encrypt.h

uvm_meter.c needs it to route the sysctl, uvm_swap.c needs it to use the functionality, and uvm_swap_encrypt.c needs it to for obvious reasons. everything else doesnt and shouldnt care. ok? Index: uvm.h === RCS file: /cvs/src/sys/uv