On 12/23 08:36, Jeremy Evans wrote:
> On 11/22 11:15, Jeremy Evans wrote:
> > On 10/19 09:34, Jeremy Evans wrote:
> > > Currently, when creating an archive file with pax(1), pax will attempt
> > > to open a file even if the file will be skipped due to an -s
> > &g
On 11/22 11:15, Jeremy Evans wrote:
> On 10/19 09:34, Jeremy Evans wrote:
> > Currently, when creating an archive file with pax(1), pax will attempt
> > to open a file even if the file will be skipped due to an -s
> > replacement with the empty string. With this change, pax wi
On Fri, Nov 26, 2021 at 5:57 AM Luís Henriques wrote:
> On Sun, Nov 21, 2021 at 03:36:33PM +, Luís Henriques wrote:
> > Hi!
> >
> > I always found it annoying that, in ksh, doing:
> >
> > $ ls ..
> >
> > followed by TAB doesn't allow me to list the options (i.e. show
> files/dirs
> > in '..
On 10/19 09:34, Jeremy Evans wrote:
> Currently, when creating an archive file with pax(1), pax will attempt
> to open a file even if the file will be skipped due to an -s
> replacement with the empty string. With this change, pax will not
> attempt to open files that it knows wil
Currently, when creating an archive file with pax(1), pax will attempt
to open a file even if the file will be skipped due to an -s
replacement with the empty string. With this change, pax will not
attempt to open files that it knows will be skipped.
When doing direct copies to a directory (-rw),
On 10/23 09:13, Theo Buehler wrote:
> On Thu, Oct 22, 2020 at 08:44:29PM -0700, Jeremy Evans wrote:
> > I was trying to diagnose a certificate validation failure in Ruby's
> > openssl extension tests with LibreSSL 3.2.2, and it was made more
> > difficult because the v
I was trying to diagnose a certificate validation failure in Ruby's
openssl extension tests with LibreSSL 3.2.2, and it was made more
difficult because the verification error type was dropped, resulting
in a SSL_R_CERTIFICATE_VERIFY_FAILED error where
SSL_get_verify_result returned X509_V_OK.
I th
The ASN1_dup function prototype was removed from libcrypto on October 24
when the major ASN1 cleanup happened. However, the function itself was
not removed, it is still present in asn1/a_dup.c and the function is
listed in Symbols.list. This results in issues if there is any code
calling the func
On 08/14 04:05, Darren Tucker wrote:
> On 4 August 2018 at 18:15, Jeremy Evans wrote:
> > I think the documentation for -e should be updated to specify it only
> > exports public keys (assuming I'm reading the code correctly), or
> > ssh-keygen should be updated to
On 08/03 09:28, Jeremy Evans wrote:
> The ssh-keygen -o flag wasn't listed in the synopsis, and -a was only
> listed with -T (where it specifies the number of primality tests), not
> for specifying the number of KDF rounds of new-format private key files.
>
> I only tested cr
The ssh-keygen -o flag wasn't listed in the synopsis, and -a was only
listed with -T (where it specifies the number of primality tests), not
for specifying the number of KDF rounds of new-format private key files.
I only tested creating a new private key and conversion of existing
keys with -p. I
On 12/07 12:52, Martin Pieuchot wrote:
> On 05/12/15(Sat) 15:22, Christian Heckendorf wrote:
> > The previous thread[1] discussing these controllers includes two
> > patches but they seem to have been merged for the commit in a way
> > that limits support to only Microsoft controllers. 3rd party Xb
ame(2) system call for restricting
+system operations.
+
+INSTALLATION
+
+To install this module type the following:
+
+ perl Makefile.PL
+ make
+ make test
+ make install
+
+DEPENDENCIES
+
+None.
+
+COPYRIGHT AND LICENCE
+
+Copyright (C) 2015 by Jeremy Evans
+
+This library is free software
On 07/20 09:36, Nicholas Marriott wrote:
> Hi
>
> I'm not sure I can think of many uses for this, tame is not something
> you are intended to just apply blindly, do you have any use cases?
Well, there is the example in the man page. :) But no, currently it's
not very useful, as more complex progr
e tame() system call appeared in OpenBSD 5.8.
$Mdocdate: $ OpenBSD 5.8
tame.c:
/* $OpenBSD: $ */
/*
* Copyright (c) 2015 Jeremy Evans
*
* Permission to use, copy, modify, and distribute this software for any
* purpose with or without f
On 07/16 05:05, Philip Guenther wrote:
> On Thu, Jul 16, 2015 at 4:54 PM, Jeremy Evans wrote:
> > Fix socketpair(2) on Unix datagram sockets that use SOCK_CLOEXEC or
> > SOCK_NONBLOCK.
> >
> > This fixes a failure in the ruby test suite.
> >
> > OK?
&
Fix socketpair(2) on Unix datagram sockets that use SOCK_CLOEXEC or
SOCK_NONBLOCK.
This fixes a failure in the ruby test suite.
OK?
Thanks,
Jeremy
Index: kern/uipc_syscalls.c
===
RCS file: /cvs/src/sys/kern/uipc_syscalls.c,v
retrie
On 10/20 03:52, Martin Pieuchot wrote:
> Hi Jeremy,
>
> On 18/10/13(Fri) 09:11, Jeremy Evans wrote:
> > This was originally submitted by Joe Gidi in November 2010, based on a
> > FreeBSD commit by Ed Schouten from back in December 2005. See
> > http://marc.info/?l=ope
This was originally submitted by Joe Gidi in November 2010, based on a
FreeBSD commit by Ed Schouten from back in December 2005. See
http://marc.info/?l=openbsd-tech&m=128924886803756&w=2 for previous
thread. The only comment was from tedu@, that SMALL_KERNEL should be
added, which I've done but
Currently, install(1) deletes files when you are installing them to the
same directory, if you only specify the directory name and not the full
path:
$ echo foo > foo; install foo .; cat foo
install: ./foo: Bad address
cat: foo: No such file or directory
This goes against the manual page, w
jmc@ and I discussed these man page changes. He's OK with this patch,
but would like another network developer to approve. So, looking for
OKs.
Jeremy
Index: nc.1
===
RCS file: /cvs/src/usr.bin/nc/nc.1,v
retrieving revision 1.56
dif
On 01/07 07:31, Nicholas Marriott wrote:
> On Fri, Jan 07, 2011 at 10:52:18AM -0800, Jeremy Evans wrote:
> > On 01/07 06:21, Nicholas Marriott wrote:
> Two further minor comments:
>
> - Can the mktemp buffer be on the stack rather than malloc()d?
Sure.
> - I think the ma
On 01/07 06:21, Nicholas Marriott wrote:
> On Fri, Jan 07, 2011 at 08:48:20AM -0800, Jeremy Evans wrote:
> > On 01/07 09:31, Nicholas Marriott wrote:
> > > On Thu, Jan 06, 2011 at 03:32:17PM -0800, Jeremy Evans wrote:
> > > > This patch adds unix datagram socket sup
On 01/07 09:31, Nicholas Marriott wrote:
> On Thu, Jan 06, 2011 at 03:32:17PM -0800, Jeremy Evans wrote:
> > This patch adds unix datagram socket support to nc(1). It's basically
> > the same patch I sent last June (see
> > http://marc.info/?l=openbsd-tech&m=127
On 01/06 08:56, Ted Unangst wrote:
> On Thu, Jan 6, 2011 at 7:19 PM, Jeremy Evans wrote:
> > I believe that for unix stream sockets, you don't need to have a sending
> > socket file created, while you do for datagram sockets, as otherwise you
> > can't have a bidi
On 01/06 07:07, Ted Unangst wrote:
> On Thu, Jan 6, 2011 at 6:32 PM, Jeremy Evans wrote:
> > This patch adds unix datagram socket support to nc(1). ?It's basically
> > the same patch I sent last June (see
> > http://marc.info/?l=openbsd-tech&m=127627296925965&
This patch adds unix datagram socket support to nc(1). It's basically
the same patch I sent last June (see
http://marc.info/?l=openbsd-tech&m=127627296925965&w=2), but updated
for -current.
Tested on amd64. Doesn't appear to cause any regressions to existing
support, tested with unix stream and
It's been about two years since I last sent a version of this
patch, which allows you to use unix datagram sockets with nc(1).
Currently nc(1) supports IP datagram sockets and unix stream
sockets, but not unix datagram sockets, and this limitation is
is not mentioned in the man page.
One main impr
28 matches
Mail list logo
