Sebastien Marie writes:
> For me, you are pledging too early (before initialization).
I agree with everything you said regarding pledge(2) technique,
including this statement, but it is worth remembering that the list
of promises can be narrowed later with another pledge call.
It's very important
Lucas Raab writes:
> +Use when a port requires no enforcement of indirect branch targets. Use
New sentence, new line.
> +.Ev USE_NOBTCFI-${MACHINE_ARCH}
> +to apply to specific architectures instead of all architectures.
I would invert the wording: "Applies to all architectures; set
USE_NOBTCFI-
Lucas Raab writes:
> +writes a wrapper script to ${WRKDIR}/bin/ld in
Use:
.Pa ${WRKDIR}/bin/ld
I see it's wrong elsewhere in the manpage, but let's not introduce another.
> +.Cm patch
> +to request that the linker adds an
> +.Dv PT_OPENBSD_NOBTCFI
> +ELF section. Use when a port requires no enf
Lucas Raab writes:
> New version attached
ok bentley@
> diff /usr/src
> commit - 2933f00289463a6d1923d1b9cc5e5c1c5c697ece
> path + /usr/src
> blob - 00ec6c3f81fcf03ea69eabe8de1741a6e562
> file + share/man/man5/bsd.port.mk.5
> --- share/man/man5/bsd.port.mk.5
> +++ share/man/man5/bsd.port.mk.5
address must be less
than or equal to the second address. The first address must be
greater than or equal to the first line of the file, and the last
address must be less than or equal to the last line of the file.
>From that I think trailing +/-, relative line numbers, and ?? regular
expressions should be described too.
> Comments, OK?
Regarding markup: Ar should be used for things that get replaced (start,
end, c, pattern) but literal characters like . $ % should use Cm.
> +.Ar 'c
This ' should be \(aq so it doesn't become a curly quote in groff -Tpdf.
--
Anthony J. Bentley
owever, it's probably worthwhile to use the modern idiom here, which is
--
Anthony J. Bentley
Marc Espie writes:
> > To setup the right alt key as compose, you can either:
> >
> > - run 'setxkbmap -option compose:ralt' somewhere in your session
> > startup script
> >
> > - create /etc/X11/xorg.conf.d/90-keyboard.conf containing
> >
> > --- Cut ---
> > Section "InputClass"
> > I
Hi,
>From /usr/src/games/fortune/Notes:
Underlining is done on a word-by-word basis, with the underlines
preceding the word, e.g., "__^H^Hhi ^H^H^H^Hthere".
Two fortunes, though, do it wrong: "_^H_^Hhi _^H_^H_^H_^H_^Hthere".
This manifests as an underline beneath only the first lette
Andras Farkas writes:
> On Mon, Oct 8, 2018 at 11:04 AM Theo de Raadt wrote:
> > You only checked the clones? You need to compare to the past.
> What you're implying is right: a comment (the one with the AB CD example) in
> https://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/usr.bin/vi/vi/v_
Hi,
RFC 6797 says:
An HSTS Host MUST NOT include the STS header field in HTTP responses
conveyed over non-secure transport.
Is this the correct check? With this I get what I expect: HSTS headers
over TLS, and no HSTS headers over unencrypted HTTP.
Index: server_fcgi.c
listen on * tls port 443" and
"listen on * port 80" in the same server block.
The other TLS-related options only apply to encrypted connections in
such a scenario. Then again, none of them work by injecting headers.
--
Anthony J. Bentley
Florian Obser writes:
> On Sun, Oct 14, 2018 at 07:36:18PM -0600, Anthony J. Bentley wrote:
> > Hi,
> >
> > RFC 6797 says:
> >
> >An HSTS Host MUST NOT include the STS header field in HTTP responses
> >conveyed over non-secure transport.
> >
Stephen Gregoratto writes:
> In the escape sequences section of printf.1, the
> character is represented using "\e\'". In UTF-8 mode, mandoc converts
> this to an acute accent. To fix this I explicitly used "\(aq" as per the
> Accents section of mandoc_char(7), although using "\e'" works as well.
Jesse Alama writes:
> XSLT is a well-established XML-based language for stylesheets. It has been ar
> ound since the late 90s; the most recent version was finalized in 2017 (see
> https://www.w3.org/TR/xslt-30/). The mime.types file bundled with OpenBSD 7.0
> -- typically used with httpd -- does
xplained in the
manpage...
This does leave open the question of how the usage strings in ex_cmd.c
should change, and whether the code there should be rearchitected so
that, e.g., "edit" and "Edit" can have different usage strings.
--
Anthony J. Bentley
Jason McIntyre writes:
> On Fri, Feb 02, 2018 at 08:17:11PM -0700, Anthony J. Bentley wrote:
> > trondd writes:
> > > The manpage for vi(1) has a small error for the :Visual/:visual command.
> The
> > > 'V' can be capital or lowercase, followed by an
Ingo Schwarze writes:
> > and the USD docs to update. so a man page fix will not suffice.
>
> I wouldn't bother. They are not installed, and the base system
> doesn't even provide tools to process them. If we ever decide
> to do anything with them, they will require a full check of accuracy
> any
Ingo Schwarze writes:
> Hi Jason,
>
> Jason McIntyre wrote on Sat, Jul 07, 2018 at 07:17:29AM +0100:
>
> > the 2/3 pages should really reference the most recent standards too.
> > it's just the work hasn;t been done.
>
> According to my understanding, the difference in policy is deliberate.
> Some
Ted Unangst writes:
> There's more to be found in the
> calendar files themselves, but I'll leave that for someone who cares more.
I care.
Index: calendars/calendar.history
===
RCS file: /cvs/src/usr.bin/calendar/calendars/calendar.h
Jason McIntyre writes:
> in the man page you have used Sq. that will make it mark up the same as
> it already does:
>
> (`*')
There's a difference: Ted uses a UTF-8 locale where Sq shows up as
pretty Unicode quotes. Literally typing `' doesn't (not in the terminal,
anyway).
mandoc should re
Diogo Galvao writes:
> On Thu, Jan 2, 2020 at 12:46 PM Oleg Pahl wrote:
> >
> > could you be so kind to revert this commit in FAQ 4?
> >
> > https://cvsweb.openbsd.org/cgi-bin/cvsweb/www/faq/faq4.html.diff?r1=1.495&r
> 2=1.496
> >
>
> Instead of reverting the commit, this change in CSS fixes the p
Diogo Galvao writes:
> On Fri, Jan 3, 2020 at 6:37 PM Anthony J. Bentley wrote:
> >
> > What browser are you using that misrenders the page like that?
>
> Firefox 71.0. It must have something to do with monospace font
> rendering on Windows.
Thanks. These details were ne
> > On Sat, 17 Jul 2010 17:28:30 +0200
> > David Coppa wrote:
> >
> > > Hi,
> > >
> > > I've put the latest snapshot on a MSI Wind U-100 netbook.
> > >
> > > ACPI suspend and resume would work great, even from X, but
> > > unfortunately after resume keyboard and mouse don't work anymore.
> > >
COLUMNS handling in our tree is inconsistent.
POSIX specifies that if COLUMNS is a valid value (read: 1 or greater),
it takes precedence; otherwise, width is handled in an unspecified
manner.
Most programs follow COLUMNS, TIOCGWINSZ if that fails, and use 80 if
that fails. Some do TIOCGWINSZ, th
vi is kind of weird about COLUMNS/LINES handling.
For one, it doesn't do any error checking:
$ COLUMNS=a vi
Floating point exception (core dumped)
The manpage also claims that COLUMNS supersedes everything else. This
is true... unless you ^Z and then unsuspend, at which point it uses
TIOCGWINSZ
Hi,
>From vi(1):
[range] s[ubstitute] [/pattern/replace/] [options] [count] [flags]
[range] & [options] [count] [flags]
[range] ~ [options] [count] [flags]
Make substitutions. The replace field may contain any of the
following sequences:
(..
Hi,
Jason McIntyre writes:
> ok by me. note that posix ex(1) does detail a working [s]ubstitute command,
> so i'm not sure whether we should support this or not.
Hm, so it does. I think I would prefer to follow POSIX in this case.
Here's a diff to allow "substitute" to work.
Annoyingly, there's
is a legal
command equivalent to "&g"; see ex/ex.c:430. Adding a command starting
with "sub" won't affect this, because there's no 'u' flag (plus there's
a command starting with "su" already).
--
Anthony J. Bentley
ed to mimic original vi at the beginning, but
broke the functionality sometime between 1994 and 1996, and nobody
noticed over the next 20 years.
Seeing as POSIX is unclear and everybody's inconsistent anyway, I'm
strongly inclined to just leave things as they are, commit the original
diff that documents the current reality, and leave it at that.
--
Anthony J. Bentley
ok?
Index: share/man/man7/mdoc.7
===
RCS file: /cvs/src/share/man/man7/mdoc.7,v
retrieving revision 1.153
diff -u -p -r1.153 mdoc.7
--- share/man/man7/mdoc.7 10 Jun 2017 16:32:08 - 1.153
+++ share/man/man7/mdoc.7
Ingo Schwarze writes:
> Hi Jason,
>
> Jason McIntyre wrote on Thu, Jun 22, 2017 at 02:07:51PM +0100:
>
> > so do you want to remove the entry for 1003.1-2013 as well?
> > none of our man pages use it.
>
> The decisive point is that even current groff does not support it,
> so deleting it is unli
Hi,
>From vi(1):
lisp [off]
(...) This option is not yet implemented.
modelines, modeline [off]
(...) This option will never be implemented.
optimize, opt [on]
(...) This option is not yet implemented
redraw, re [off]
(...
Christian Weisgerber writes:
> On 2017-06-29, "Anthony J. Bentley" wrote:
>
> > The vi manual is long enough. It doesn't seem very helpful to keep stubs
> > that have been stubs for 20 years.
>
> Should we retain some documentation along the lines of &quo
Matthew Martin writes:
> As far as I can tell, it's never been linked into the build even looking
> in the NetBSD history.
It's junk. ok bentley@ to whomever wants to remove it.
Hi,
"Punctuation followed by backspace" hasn't been the right way to enter
accents for a long time.
ok?
Index: Notes
===
RCS file: /cvs/src/games/fortune/Notes,v
retrieving revision 1.3
diff -u -p -r1.3 Notes
--- Notes 28 Sep
"Ted Unangst" writes:
> Anthony J. Bentley wrote:
> > Hi,
> >
> > "Punctuation followed by backspace" hasn't been the right way to enter
> > accents for a long time.
>
> hard to see what the diff is doing since i coudn't see the back
Ingo Schwarze writes:
> So here is a patch that makes putting UTF-8 characters into
> fortune/datfiles safe.
And here is a patch that retains the accents in the datfiles as UTF-8.
Index: Notes
===
RCS file: /cvs/src/games/fortune/Not
Hi,
This brings /usr/share/misc/getopt in sync with the example in getopt(3).
ok?
Index: getopt
===
RCS file: /cvs/src/share/misc/getopt,v
retrieving revision 1.8
diff -u -p -r1.8 getopt
--- getopt 1 Feb 2006 09:27:28 -
Hi,
eqnchar is a collection of eqn(7) definitions to create mathematical
symbols by constructing them from other characters. Creating circled
plus with O, a backspace, and a plus, for example. The results are
quite ugly in both mandoc and groff if it even works at all.
Nothing in base (or even an
"Ted Unangst" writes:
> Todd C. Miller wrote:
> > On Sun, 04 Sep 2016 11:58:23 -0600, "Anthony J. Bentley" wrote:
> >
> > > This brings /usr/share/misc/getopt in sync with the example in getopt(3).
> >
> > OK, though I wonder if anyone
Hi,
Unlike all the other software in the tree that checks terminal sizes,
ps(1) used to check the stdin and stderr terminal sizes as well as stdout.
When I unified the terminal size checks in the tree in March, I missed
this, and now "ps aux | blah" gets wrapped to 79 characters no matter
how big
documentation, and the meaning is pretty clear.
$ grep daemonize /usr/share/man/man8/* | wc -l
27
--
Anthony J. Bentley
me.h
>
> sys/time.h has the timespec definition. So this appears to be an issue
> specific to NetBSD. Or, at least, not an issue on OpenBSD.
Maybe better to refer to POSIX directly, which states:
The header shall define the timespec structure as
described in .
--
Anthony J. Bentley
ok?
Index: lib/libc/gen/isblank.3
===
RCS file: /cvs/src/lib/libc/gen/isblank.3,v
retrieving revision 1.11
diff -u -p -r1.11 isblank.3
--- lib/libc/gen/isblank.3 6 Jul 2013 17:31:20 - 1.11
+++ lib/libc/gen/isblank.3
Pavel Plamenov writes:
> There are some leftover links to www@, which is gone.
Your patch seems to have gotten broken somehow, by adding extra
space to the beginning of lines. I removed those and committed it;
thanks for sending.
Pavel Plamenov writes:
> Updated patch.
Thanks, I've reviewed and committed this. Your mailer is still adding
extra whitespace to the patch, though... please figure out why that's
happening and fix it.
Alexey Suslikov writes:
> In
>
> wscons(4) works with even more odd trackpads.
> Added pvbus(4) paravirtual device tree root on virtual machines that
> are running on hypervisors.
>
> http://www.openbsd.org/cgi-bin/man.cgi?query=wscons(4)&sec=4
> http://www.openbsd.org/cgi-bin/man.cgi?query=pvbus
Michael Reed writes:
> Hi,
>
> This is in the same vein as [1], which replaced the usage of `Ar' with
> `Cm' where applicable. Besides that, I unindented line 134 because
> `-offset indent' is already being used, but that's it.
>
> Regards,
> Michael
>
> [1]: https://marc.info/?l=openbsd-tech&m
Kevin Zhang writes:
> Using >, & in raw text is invalid HTML.
You're right about &, but > does not need to be escaped.
--
Anthony J. Bentley
ok?
Index: nl_langinfo.3
===
RCS file: /cvs/src/lib/libc/locale/nl_langinfo.3,v
retrieving revision 1.10
diff -u -p -r1.10 nl_langinfo.3
--- nl_langinfo.3 21 Jan 2014 03:15:45 - 1.10
+++ nl_langinfo.3 24 Oct 2015
>From wcrtomb(3):
The wcrtomb() function conforms to ISO/IEC 9899/AMD1:1995 (``ISO C90,
Amendment 1''). The restrict qualifier is added at ISO/IEC 9899/1999
(``ISO C99'').
This wording is confusing. Is it implying that we don't use a restrict
qualifier? (We do.)
If a standard cha
Hi,
The 2015 Chromebook Pixel has a broken ACPI that doesn't support
burst mode and will hang on boot when it's tried.
Rev 1.54 of acpiec.c disabled it for single-byte reads and writes,
which fixed this machine, but broke others. So it got reverted, with
the note:
"A machine/bios-dependent che
"Ted Unangst" writes:
> it only gets deeper and thicker...
Indeed.
Here's a shorter implementation. Like colorls(1), it uses wide
characters (only within the putname() function) but is slightly cleaned
up and simplified.
Index: ls.c
==
Stefan Sperling writes:
> On Mon, Oct 26, 2015 at 03:58:58PM -0600, Anthony J. Bentley wrote:
> > "Ted Unangst" writes:
> > > it only gets deeper and thicker...
> >
> > Indeed.
> >
> > Here's a shorter implementation. Like colorls
"Ted Unangst" writes:
> Fixing citrus is a pretty massive effort in itself. I'd prefer to see the
> replacement code prove itself as a separate API first, then we can remove
> citrus and change the wchar functions to use the new code. I'm less confident
> in a "meet in the middle" effort where we c
Stefan Sperling writes:
> On Tue, Oct 27, 2015 at 04:21:28PM +0100, Vadim Zhukov wrote:
> > Since we're already talking about "s==NULL" case, stating it again is
> > extraneous. IMHO, better would be:
> >
> > .Fa pwc
> > -is completely ignored.
> > +is ignored.
> >
> > > .It pwc == NULL
> > >
es my sdl2 testcase, mupen64plus. Thanks for looking into
this along with Peter.
--
Anthony J. Bentley
dan mclaughlin writes:
> i was writing a script when i ran across this.
Is there a wc that doesn't behave this way? POSIX wc explicitly counts
newline characters. So this is probably the behavior people write their
scripts against.
Gregor Best writes:
> Hi people,
>
> inspired by someone on Hackernews talking about how hard it would be to
> properly pledge an editor, here's a patch to pledge Vi and Ex.
I'd like to investigate the ideas you mentioned: disabling proc/exec with
-S and making -R actually read-only. But both of
Gregor Best writes:
> @@ -229,6 +230,14 @@ editor(GS *gp, int argc, char *argv[])
> }
> if (LF_ISSET(SC_EX) && F_ISSET(gp, G_SCRIPTED))
> silent = 1;
> +
> + if (secure) {
> + if (pledge("stdio rpath wpath cpath fattr flock tty", NULL))
> +
"Anthony J. Bentley" writes:
> Gregor Best writes:
> > @@ -229,6 +230,14 @@ editor(GS *gp, int argc, char *argv[])
> > }
> > if (LF_ISSET(SC_EX) && F_ISSET(gp, G_SCRIPTED))
> > silent =3D 1;
> > +
> > + if (secure) {
When I hit backspace after a backslash, usually I just want to delete
the backslash. I don't think I've ever intended to input a literal ^?.
If I ever did want to insert ^H, ^?, or ^U, I would just type ^V first.
I've passed this diff around privately before and gotten a tepid
response, but it was
Hi,
A simple change (comes from FreeBSD nvi).
ok?
Index: common/options.c
===
RCS file: /cvs/src/usr.bin/vi/common/options.c,v
retrieving revision 1.18
diff -u -p -r1.18 options.c
--- common/options.c14 Nov 2014 20:27:03 -
Gregor Best writes:
> On Mon, Nov 23, 2015 at 01:36:00AM -0700, Anthony J. Bentley wrote:
> > [...]
>
> In addition to this, my ~/.exrc also sets cedit to tab. Would this
> make sense here as well? Currently it's disabled by default, but
> IMHO it's a useful feat
Hi,
As X starts, it will attempt to detect features from the kbd(8)
setting--for example, us.dvorak will enable dvorak in X, and
fr.dvorak will enable French dvorak in X. However, it detects
these features with equality checks, which will fail if multiple
options are set, as in the case of us.dvor
eader from the ISO C standard, a statement to
the effect that "any conflict is unintentional" is included. That is
intended to refer to a direct conflict. POSIX.1-2008 acts in part as
a profile of the ISO C standard, and it may choose to further
constrain behaviors allowed to vary by the ISO C standard.
--
Anthony J. Bentley
.
>> Enable use after free protection for larger allocations.
In addition to what jmc said, if you document these flags they need to
be marked up with the Cm macro instead of ASCII single quotes.
--
Anthony J. Bentley
El
I agree with this logic as well. I would be uncomfortable if it got any
more complicated.
--
Anthony J. Bentley
ms, including
> - * and . If not found, use a large default.
> - */
> -#ifndef MAXHOSTNAMELEN
> -#define MAXHOSTNAMELEN 1024
> -#endif
> char host[MAXHOSTNAMELEN];
>
> gp = sp->gp;
FreeBSD nvi uses sysconf for this. If that's the
in favor of saving it?
--
Anthony J. Bentley
Chrome attempt to
solve this with a preloaded list of domains that they use HSTS for by
default; see https://hstspreload.appspot.com/
--
Anthony J. Bentley
"Ted Unangst" writes:
> spamd(8) quotes the
> pf table name. compress(3) quotes the path.
IMO, these are bugs in the manuals. spamd(8) should be using <> directly.
compress(3) should drop the angle quotes and just use Pa. Or wrap Pa in
<> if people really think it's needed.
> The mandoc chars.i
"Anthony J. Bentley" writes:
> "Ted Unangst" writes:
> > spamd(8) quotes the
> > pf table name. compress(3) quotes the path.
>
> IMO, these are bugs in the manuals. spamd(8) should be using <> directly.
> compress(3) should drop the angle qu
an incorrect display of the regex
> word boundaries `\<' and `\>' in the UTF-8 locale, which surely should
> be rendered as escaped less-than and greater-than signs.
Thanks; the diff was correct so I've applied it.
--
Anthony J. Bentley
Stuart Henderson writes:
> On 2023/04/01 11:27, Jared Harper wrote:
> > For some reason I haven't received the email from Solène (even after
> > requesting it re-sent on lists.openbsd.org; nor is it in spam; I will
> > look further into this issue), so I'm adding my reply in-line here:
>
> Solène's
A federal holiday since 2021.
ok?
Index: usr.bin/calendar/calendars/calendar.usholiday
===
RCS file: /cvs/src/usr.bin/calendar/calendars/calendar.usholiday,v
retrieving revision 1.9
diff -u -p -r1.9 calendar.usholiday
--- usr.bin/cal
ok?
Index: sbin/isakmpd//isakmpd.8
===
RCS file: /cvs/src/sbin/isakmpd/isakmpd.8,v
retrieving revision 1.112
diff -u -p -u -p -r1.112 isakmpd.8
--- sbin/isakmpd//isakmpd.8 14 Jul 2013 16:37:41 - 1.112
+++ sbin/isakmpd//is
ok?
Index: libexec/fingerd/fingerd.8
===
RCS file: /cvs/src/libexec/fingerd/fingerd.8,v
retrieving revision 1.18
diff -u -p -u -p -r1.18 fingerd.8
--- libexec/fingerd/fingerd.8 25 Sep 2007 06:28:13 - 1.18
+++ libexec/finger
On Thu, Feb 13, 2014 at 7:22 PM, Ted Unangst wrote:
> mandoc fortunately has an option -Tlocale, which will pick between
> ascii and utf8 based on environment. Perfect! Let's use it.
>
> Tested to work as expected in uxterm. Tested to change nothing in a
> regular xterm by default (no LC_CTYPE set
On Tue, Oct 4, 2011 at 4:32 PM, Nicholas Marriott
wrote:
> I agree.
>
> Or if we must have compression flags just have one flag and let tar
> figure out the right tool to use. Having -Z -z -J -j etc etc is silly.
GNU tar no longer needs those flags... their "tar xf foo" works just
fine whether fo
My only issue with aucat is a noticeable lag for real-time
applications like games, even when running with a small buffer size as
per FAQ 13.5.
--
Anthony J. Bentley
Hi Alexandre,
On Mon, Oct 10, 2011 at 11:29 AM, Alexandre Ratchov wrote:
> On Mon, Oct 10, 2011 at 11:16:21AM -0600, Anthony J. Bentley wrote:
>> My only issue with aucat is a noticeable lag for real-time
>> applications like games, even when running with a small buffer size as
Hi,
This looks like a typo, almost changes the meaning of the sentence:
Index: lib/libc/stdlib/malloc.3
===
RCS file: /cvs/src/lib/libc/stdlib/malloc.3,v
retrieving revision 1.68
diff -u lib/libc/stdlib/malloc.3
--- lib/libc/stdlib/m
continguous -> contiguous. Or perhaps it was meant to be "continuous."
Index: usr.sbin/bgpd/kroute.c
===
RCS file: /cvs/src/usr.sbin/bgpd/kroute.c,v
retrieving revision 1.186
diff -u usr.sbin/bgpd/kroute.c
--- usr.sbin/bgpd/kroute.c
Sent from a SMCWUSB-N2:
otus0 at uhub0 port 3 "ATHER USB2.0 WLAN" rev 2.00/1.06 addr 2
otus0: MAC/BBP AR9170, RF AR9102, MIMO 2T2R, address 00:22:2d:c0:30:b3
Index: otus.4
===
RCS file: /cvs/src/share/man/man4/otus.4,v
retrieving revi
nding high-bit files
to the list.
--
Anthony J. Bentley
the list before. I think the conclusion was
that xz won't make it into base, and adding new tar flags for stuff not
in base is a bad idea (although we already have -j for bzip2).
--
Anthony J. Bentley
87 matches
Mail list logo
