Two questions:
1) In the heuristics for deciding on the AP, what is used to decide the
best AP.
2) Does the background scan eventually timeout completely requiring a
reboot?
Just attached to an AP from an ethernet connection and can't get it to
change, period. So, need to know if I have to keep r
> >That was also the initial design with substantial priv seperation.
> >It shouldn't be designed to tap another process potentially running
> >with a different uid.
>
> Not wanting to touch processes that run with different user ids, is that
> in order to fully eliminate any influence from the o
That was also the initial design with substantial priv seperation.
It shouldn't be designed to tap another process potentially running
with a different uid.
Not wanting to touch processes that run with different user ids, is that
in order to fully eliminate any influence from the other process/
> On 2017/12/05 12:59, Tim Kuijsten wrote:
> > I think it would be nicer if acme-client is able to start and stop httpd(8)
> > itself with the config mentioned in acme-client(5) so users on
> > non-webservers don't have to be bothered with setting up a web server
> > themselves.
>
> That feels lik
I'll see if I can suss anything out this week. I'll compile and test on
GENERIC as well.
On Tue, Dec 5, 2017 at 10:13 AM, Stefan Sperling wrote:
> On Tue, Dec 05, 2017 at 09:38:07AM -0700, Base Pr1me wrote:
> > Testing environment: 3 APUs with same SSID, 2 5GHz channels and 1 2.4GHz
> channel.
>
On Tue, Dec 05, 2017 at 09:38:07AM -0700, Base Pr1me wrote:
> Testing environment: 3 APUs with same SSID, 2 5GHz channels and 1 2.4GHz
> channel.
>
> Test 1: Boot lappy, connected to 2.4GHz spot that I was closest to. Walked
> to 5GHz spot and waited. It switched fine. Walked to second 5GHz spot
On 2017/12/05 12:59, Tim Kuijsten wrote:
> I think it would be nicer if acme-client is able to start and stop httpd(8)
> itself with the config mentioned in acme-client(5) so users on
> non-webservers don't have to be bothered with setting up a web server
> themselves.
That feels like a huge reach
Testing environment: 3 APUs with same SSID, 2 5GHz channels and 1 2.4GHz
channel.
Test 1: Boot lappy, connected to 2.4GHz spot that I was closest to. Walked to
5GHz spot and waited. It switched fine. Walked to second 5GHz spot and waited.
It did not switch. Waited longer. It did not switch. I
On Fri, Oct 27, 2017 at 01:50:26AM +0200, Jan Engelhardt wrote:
> #include
> int main(void) {
> char salt[3] = {0xf8, 0xd0, 0x00};
> char out[32];
> DES_fcrypt("foo", salt, out);
> }
This program produces a Segmentation fault in OpenBSD current.
> openssl 1.1.x has it fix
On Tue, Dec 05 2017, Scott Cheloha wrote:
> Hey,
>
> Sorry for the delay.
>
> On Sun, Nov 26, 2017 at 07:00:36PM +0100, Jeremie Courreges-Anglas wrote:
>> On Sun, Nov 26 2017, Jeremie Courreges-Anglas wrote:
>> > On Sat, Nov 25 2017, Brent Cook wrote:
>> >> Thanks guys. This will make enabling t
2017-12-05 13:45 GMT+03:00 Vadim Zhukov :
> The third nit in ypldap code, and the most questionable one.
>
> IMHO, there is no reason to dynamically allocate relatively small
> internal structures without buffers in it:
Please disregard this one, I'm an idiot that looks at and doesn't see
the RB_I
On Tue, Dec 05, 2017 at 11:32:53AM +0100, Martin Pieuchot wrote:
> On 04/12/17(Mon) 12:24, Martin Pieuchot wrote:
> > Since SMAP is enabled ddb(4)'s 'trace /u' and 'trace /p' for a userland
> > processes result, as expected, in page faults.
> >
> > Diff below disable SMAP for the duration of the c
Hey,
This patch changes some of the timers in tmux to the
monotonic clock.
None of these are user-facing. Changing them eliminates
the clock jump edge cases with little additional complexity.
To make the changes as unobtrusive as possible I added
a new module, time.c, which contains monotonic a
On Tue, Dec 05, 2017 at 07:51:47AM -0500, Philippe Meunier wrote:
> kshe wrote:
> >If the number `002' is said to have only one digit because the zeros in
> [...]
> >the integer logarithm, thus being nothing but arbitrary, and as such of
> >little practical value.
>
> Yes, yes, but "number of dig
On Mon, Dec 04, 2017 at 03:33:56PM +0100, Martin Pieuchot wrote:
> Diff below change the usage of `sb_flags' and `sb_flagsintr'. The
> former will be protected by the socket lock while the latter will
> be using atomic operations.
I like this plan.
> @@ -381,17 +381,18 @@ sbunlock(struct socket
Hey,
Sorry for the delay.
On Sun, Nov 26, 2017 at 07:00:36PM +0100, Jeremie Courreges-Anglas wrote:
> On Sun, Nov 26 2017, Jeremie Courreges-Anglas wrote:
> > On Sat, Nov 25 2017, Brent Cook wrote:
> >> Thanks guys. This will make enabling this on the odder platforms in
> >> portable easier.
>
kshe wrote:
>If the number `002' is said to have only one digit because the zeros in
[...]
>the integer logarithm, thus being nothing but arbitrary, and as such of
>little practical value.
Yes, yes, but "number of digits" and "integer logarithm" are two different
things. You sound suspiciously li
Hi tech@,
(super-slightly revised mail/patch compared to the one from October 1st,
mainly indent and line-wrap [1])
I'm using acme-client(1) to handle my certificates on a bunch of
mailservers (smtps, imaps, pops) and a dedicated syslogd(8) server with
tls. My daily cron on these machines co
Hi,
this diff changes the config parsing code so that we can specify
multiple ikesa and childsa proposals by using the keywords multiple
times. It needs the other payload parsing diff that I posted as well.
Multiple proposals can be specified like this:
ikesa auth hmac-sha2-256 enc aes-192
> Date: Mon, 4 Dec 2017 21:39:43 -0800
> From: Philip Guenther
>
> On Mon, 4 Dec 2017, Mark Kettenis wrote:
> > The ld.so bits have been committed last week. So here is a new version
> > of the diff. This version exports __cxa_thread_atexit_impl such that
> > gcc picks up our implementation.
The third nit in ypldap code, and the most questionable one.
IMHO, there is no reason to dynamically allocate relatively small
internal structures without buffers in it:
struct userent {
RB_ENTRY(userent)ue_name_node;
RB_ENTRY(userent)
The second nit in ypldap code.
This deduplicates code a bit. Okay?
--
WBR,
Vadim Zhukov
Index: ypldap.c
===
RCS file: /cvs/src/usr.sbin/ypldap/ypldap.c,v
retrieving revision 1.21
diff -u -p -r1.21 ypldap.c
--- ypldap.c20 Jan
Recently I had to start diffing deeper in ypldap. The main problem I'm
trying to solve is that _some_ LDAP attributes are case-insensetive,
including _some_ that could be used as user names. Until I get all
the picture myself, I won't post all the boring details I came with.
But while browsing the
On 04/12/17(Mon) 12:24, Martin Pieuchot wrote:
> Since SMAP is enabled ddb(4)'s 'trace /u' and 'trace /p' for a userland
> processes result, as expected, in page faults.
>
> Diff below disable SMAP for the duration of the command. This allows us
> to see any possible frame corruption.
Updated ve
24 matches
Mail list logo
