I tried this diff, and it broke the ability to use dynamic addresses.
ie, the following rules should work:
pass in on gre52 inet proto icmp route-to (gre49:peer)
pass in on vmx0 inet proto icmp route-to (gre:peer)
however, other forms of dynamic interface addresses should fail. or do
we want to s
On Fri, Jan 22, 2021 at 12:12:58AM +0100, Alejandro Colomar wrote:
> This is useful for using tee to just write to a file,
> at the end of a pipeline,
> without having to redirect to /dev/null.
> @@ -93,6 +98,7 @@ Copy standard input to each FILE, and also to standard
> output.\n\
> "), stdout);
This is useful for using tee to just write to a file,
at the end of a pipeline,
without having to redirect to /dev/null.
Example:
echo 'foo' | sudo tee -q /etc/foo;
is equivalent to the old (and ugly)
echo 'foo' | sudo tee /etc/foo >/dev/null;
Tools with a similar interface: grep
[CC += mtk, linux-api, freebsd, openbsd]
On 1/21/21 10:26 PM, Alejandro Colomar (man-pages) wrote:
> Hi Berny,
>
> On 1/21/21 10:01 PM, Bernhard Voelker wrote:
>> On 1/21/21 7:39 PM, Alex Henrie wrote:
>>> That said, I would love to see `tee -q` added to a future revision of
>>> POSIX and adopted
On Thu, 21 Jan 2021 19:53:48 +0100, Hiltjo Posthuma wrote:
> Yes please!, I've also run into this issue on OpenBSD with the "catpoint"
> presentation program. I've been meaning to send the exact same backport patch
> .
>
> The upstream snapshot version of ncurses compiles fine on OpenBSD and I've
> We should just ignore any of the special curses keys returned by
> getch() since canfield is not prepared to deal with them.
ok tb
On Thu, Jan 21, 2021 at 11:06:05AM -0700, Todd C. Miller wrote:
> This is a backport of the ncurses 5.9 20120707 patch.
> https://github.com/mirror/ncurses/commit/471bc007361fd4bc8d2fae060c7d5b09828ed541
>
> Previously, getch() would return ERR if SIGWINCH was received but
> the window didn't actu
This is a backport of the ncurses 5.9 20120707 patch.
https://github.com/mirror/ncurses/commit/471bc007361fd4bc8d2fae060c7d5b09828ed541
Previously, getch() would return ERR if SIGWINCH was received but
the window didn't actually change size. This can happen, for
example, when the xterm font is ch
Paul Janzen reported that if you try to resize an xterm while
canfield is running, canfield suspends itself. This is due to the
curses getch() function returning KEY_RESIZE. However, canfield
only expects to read 7-bit ascii characters and so uses a mask of
0x7f. Since KEY_RESIZE & 0x7f == 0x1a (
When unwind(8) learns new autoconf resolvers (from dhcp or router
advertisements) it checks if a DNS64 is present in this network
location and tries to recover the IPv6 prefix used according to
RFC7050.
The learned autoconf resolvers are then prevented from upgrading to
the validating state since
Move resolv_conf string generation for ASR to function; makes
upcomming DNS64 diff simpler.
OK?
diff --git resolver.c resolver.c
index d42d19c1087..2634b95c01f 100644
--- resolver.c
+++ resolver.c
@@ -195,6 +195,7 @@ int running_query_cnt(void);
int*resolvers
Don't just blindly upgrade to VALIDATING if we see a SECURE answer.
This can happen if things improve after we check a strategy, for
example ntpd corrected the time.
Let's go through the check_resolver() / new_resolver() code path
which will also hook up the resovler to the shared cache.
diff --g
I guess so, though I cannot imagine a program-context where bcrypt_newhash
stack's can be leaked in a dangerous way.
Programs that create these hashes end up knowing more, or having more power.
Peter J. Philipp wrote:
> Hi,
>
> On IRC, someone and I were arbitrarily going through bcrypt.c and
January 21, 2021 11:45 AM, gil...@poolp.org wrote:
> January 21, 2021 11:25 AM, "Claus Assmann" wrote:
>
>> On Thu, Jan 21, 2021, Martin Vahlensieck wrote:
>>
>>> I think the backslash at the beginning of the line is an error.
>>
>> Why? Does it fail when used as described?
>>
>>> -\eeric, "|
January 21, 2021 11:25 AM, "Claus Assmann" wrote:
> On Thu, Jan 21, 2021, Martin Vahlensieck wrote:
>
>> I think the backslash at the beginning of the line is an error.
>
> Why? Does it fail when used as described?
>
>> -\eeric, "|/usr/bin/vacation -a allman eric"
>
> Originally this was to a
Hi,
On IRC, someone and I were arbitrarily going through bcrypt.c and I noticed
the following resulting from bcrypt_newhash():
int
bcrypt_newhash(const char *pass, int log_rounds, char *hash, size_t hashlen)
{
char salt[BCRYPT_SALTSPACE];
if (bcrypt_initsalt(log_rounds, salt, siz
> Date: Thu, 21 Jan 2021 12:49:57 +
> From: Jason McIntyre
>
> On Thu, Jan 21, 2021 at 12:47:15PM +, Stuart Henderson wrote:
> > On 2021/01/21 12:43, Jason McIntyre wrote:
> > > On Thu, Jan 21, 2021 at 11:15:48AM +0100, Martin Vahlensieck wrote:
> > > > Hi
> > > >
> > > > I think the bac
Jason McIntyre wrote:
> On Thu, Jan 21, 2021 at 12:47:15PM +, Stuart Henderson wrote:
> > On 2021/01/21 12:43, Jason McIntyre wrote:
> > > On Thu, Jan 21, 2021 at 11:15:48AM +0100, Martin Vahlensieck wrote:
> > > > Hi
> > > >
> > > > I think the backslash at the beginning of the line is an e
On Thu, Jan 21, 2021 at 12:47:15PM +, Stuart Henderson wrote:
> On 2021/01/21 12:43, Jason McIntyre wrote:
> > On Thu, Jan 21, 2021 at 11:15:48AM +0100, Martin Vahlensieck wrote:
> > > Hi
> > >
> > > I think the backslash at the beginning of the line is an error.
> > >
> > > Best,
> > >
> >
On 2021/01/21 12:43, Jason McIntyre wrote:
> On Thu, Jan 21, 2021 at 11:15:48AM +0100, Martin Vahlensieck wrote:
> > Hi
> >
> > I think the backslash at the beginning of the line is an error.
> >
> > Best,
> >
> > Martin
> >
> > Index: vacation.1
> >
On Thu, Jan 21, 2021 at 11:15:48AM +0100, Martin Vahlensieck wrote:
> Hi
>
> I think the backslash at the beginning of the line is an error.
>
> Best,
>
> Martin
>
> Index: vacation.1
> ===
> RCS file: /home/reposync/cvs//src/usr.b
On Thu, Jan 21, 2021, Martin Vahlensieck wrote:
> I think the backslash at the beginning of the line is an error.
Why? Does it fail when used as described?
> -\eeric, "|/usr/bin/vacation -a allman eric"
Originally this was to avoid recursion, i.e.,
\eric
will not be expanded again.
Maybe that
Hi
I think the backslash at the beginning of the line is an error.
Best,
Martin
Index: vacation.1
===
RCS file: /home/reposync/cvs//src/usr.bin/vacation/vacation.1,v
retrieving revision 1.23
diff -u -p -r1.23 vacation.1
--- vacatio
On Wed, 20 Jan 2021 21:42:21 -0600
joshua stein wrote:
> There are no i2c-connected mice and ims(4) will always be a
> touchpad/touchscreen/stylus that just doesn't meet the requirements
> of imt(4).
>
> Presenting it as WSMOUSE_TYPE_TOUCHPAD makes the X server set it up
> as a separate point
24 matches
Mail list logo
