As far as I can tell, all of the calls to memset(3) in
lib/libc/crypt/arc4random.c are intended to wipe memory to avoid having
the randomly generated data in memory twice, so it would seem good
practice to use explicit_bzero(3) to avoid this being optimized out.
Index: lib/libc/crypt/arc4random.c
On 12/18/19 5:46 AM, Theo Buehler wrote:
> The diff modifies the CA section, not ENC. I need to check if we can
> do something about the weak defaults there, but the diff is not
> correct.
That's my bad.
New diff inline.
> For ENC, it's indeed correct that the default was changed from md5 to
>
This diff changes the documentation of openssl(1) enc to note the
default value (sha256) and replace the "hardcoded" list of md5, sha1
with instructions to use list-message-digest-algorithms instead.
Inspired by a conversation on misc@ a few weeks ago ("LibreSSL vs.
OpenSSL enc command").
Perhaps
ppt(6) seems to have had an interesting history.
It seems to have been mentioned in the V1 manual as ppt(I),
seemingly actually doing something related to paper tape.
Then it vanished as far as I could tell.
In V7, it seems to have found its current form as a game
and got documented on bcd(6)
This patch fixes a newline in proot.1 preventing LOCKDIR from
being rendered correctly.
Note that this causes the input line to be very long, which
seemed okay to me because dhcp-options.5 does the same (e.g. on
line 184).
Index: share/man/man1/proot.1
I've taken a stab at improving kqueue.2 formatting.
Most of the changes are markup fixes.
I used ".Dv NULL" over plain "null" in accordance with
lib/libc/stdlib/malloc.3 rev. 1.113.
I also added a note to the HISTORY section that kqueue()/kevent() have
been available in OpenBSD since 2.9;
the
On 4/24/19 4:15 PM, Florian Obser wrote:
> On Wed, Apr 24, 2019 at 09:34:57AM -0400, Bryan Steele wrote:
>> On Wed, Apr 24, 2019 at 03:08:59PM +0200, Fabio Scotoni wrote:
>>> [...]
>>
>> Isn't RF C8555 ACMEv2? acme-client(1) only supports ACMEv1, so I don't
>> t
This diff updates the acme-client(1) STANDARDS section.
Currently, it lists an RFC draft for the ACME protocol.
Since March of this year, there is a proposed standard with an actual
RFC number.
While at it, make the format match ssh(1) STANDARDS by providing .%A and
.%D entries.
Index:
Dear Ingo,
On 4/23/19 9:30 PM, Ingo Schwarze wrote:
>>> Index: rcsfile.5
> [...]
>>> +.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
>>> +.\"
>
>> Nitpick: The other man pages in the usr.bin/rcs/ tree do not have a
>> trailing .\" -- except for rcs(1).
>> You may wish to make
===========
> RCS file: rcsfile.5
> diff -N rcsfile.5
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ rcsfile.5 23 Apr 2019 17:04:55 -
> @@ -0,0 +1,154 @@
> +.\" $OpenBSD$
> +.\"
> +.\" Copyright
cal time with no
timezone information anywhere in the file.)
.\" $OpenBSD$
.\"
.\" Copyright (c) 2019 Fabio Scotoni
.\"
.\" Permission to use, copy, modify, and distribute this software for any
.\" purpose with or without fee is hereby granted, provided that the abov
While familiarizing myself with OpenRCS,
I noticed that there's no rcsfile(5).
This may be handy for people whose RCS file got corrupted for whatever
reasons.
Other *NIXes that ship SCCS tend to have a sccsfile(4),
so I figured it could be worthwhile to have something of that nature for
OpenRCS.
This patch cleans up some minor punctuation issues in the hack(6) man page.
The placement of the comma in an Ev list matches crontab(1) and sysmerge(8) now.
It also introduces .Dq for double quotes to the hack(6) man page.
Index: games/hack/hack.6
On 1/20/19 3:11 PM, Ingo Schwarze wrote:
> Hi Fabio,
>
> Fabio Scotoni wrote on Sun, Jan 20, 2019 at 12:52:18PM +0100:
>
>> The what(1) man page has a BUGS section,
>> which mdoc(7) says is discouraged in OpenBSD.
>
> What? Using BUGS sections is perfectly fine
The what(1) man page has a BUGS section,
which mdoc(7) says is discouraged in OpenBSD.
The contents of the BUGS section is mostly unhelpful anyway.
Talking about BSD not being able to distribute SCCS doesn't help
anyone;
not behaving like the original SCCS is obvious considering the
STANDARDS
The cvsintro(7) man page uses ".Bx -licensed",
which is rendered as "-licensedBSD".
This patch fixes this to correctly read "BSD-licensed"
in both mandoc and groff.
I'm not entirely sure if .Bx should even be used here,
though apparently that decision has been made deliberately.
Index: cvsintro.7
16 matches
Mail list logo
