This diff tightens up internal references to exported functions, plus one
pointless syscall.
This is done via a namespace.h and wrapper headers like the hidden/* added
in the libc source. The files are the libpthread directory as that's the
style of arrangement of the rthread source; some day
This diff eliminates the need to _invoke_ syscalls via their aliases with
the '_thread_sys_' prefix, and uses that for a few syscalls that didn't
but should have.
This is done via the REDIRECT_SYSCALL() macro which builds on the same gcc
extensions that the libc cleanup this fall did. Applyin
These pages were never updated for the timecounter changes.
time.9 should move to time_second.9 as well.
Index: time.9
===
RCS file: /cvs/src/share/man/man9/time.9,v
retrieving revision 1.11
diff -u -p -r1.11 time.9
--- time.9 3
On Fri, Apr 01, 2016 at 04:19:46PM -0600, Todd C. Miller wrote:
> The problem is that fopen(tty, "w") uses O_CREAT. If we use open
> + fdopen we can avoid that.
>
> Can you try this diff?
Works well. Thank you!
The problem is that fopen(tty, "w") uses O_CREAT. If we use open
+ fdopen we can avoid that.
Can you try this diff?
- todd
Index: libexec/comsat/comsat.c
===
RCS file: /cvs/src/libexec/comsat/comsat.c,v
retrieving revision 1.44
di
When biff(1) is set to y, comsat opens the tty for write.
if ((tp = fopen(tty, "w")) == NULL) {
dsyslog(LOG_ERR, "%s: %s", tty, strerror(errno));
_exit(1);
}
This aborts:
(gdb) bt
#0 0x0890a441 in open () at :2
#1 0x0897e308 in *_libc_fopen (file
Using 5.9 + openup , amd64 base config
Assuming two interface s
em1 and em5
and a configuration interconnecting interfaces like this
vether10 10.1.2.10 rdomain 10 <--> bridge10 <--> vlan1010 vlan 10<-> em1
<--cable
cable-> em5 <--> vlan1020 vlan 10 <--> bridge50 <--> vether50 10.1.2.50
rdomain 50
Hi,
> Basically - a root of trust is something sacrosanct. If you said "use
> this root of trust" and somehow that fails, trying to run more code
> when you *know* the requested root of trust did not work is very very
> wrong. Do not proceed further, do not pass go, do not try to validate
> the
Yes, I mean the program should exit with an error message if the
requested CA file (either the default, or via -CAfile) can't be
loaded.
On Fri, Apr 1, 2016 at 8:44 AM, Florian Zumbiehl wrote:
> Hi,
>
>> Florian I'm happy to look at this now with you
>>
>> But based on the old discussion I'm not
Basically - a root of trust is something sacrosanct. If you said "use
this root of trust" and somehow that fails, trying to run more code
when you *know* the requested root of trust did not work is very very
wrong. Do not proceed further, do not pass go, do not try to validate
the certificate any
Base install + openup
64 bytes from 8.8.8.8: icmp_seq=1 ttl=49 time=32.923 ms
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 32.008/32.466/32.923/0.457 ms
#
#
# em0: watchdog: head 78 tail 77 TDH 78 TDT 78
em0: watchdog:
Hi,
> Florian I'm happy to look at this now with you
>
> But based on the old discussion I'm not certain I'm happy with the
> final result.
>
> IMO - here's what we need in these:
>
> 1) If you specify nothing, you should get the default.
> 2) If you specify a CAfile, and there is no failure
Florian I'm happy to look at this now with you
But based on the old discussion I'm not certain I'm happy with the
final result.
IMO - here's what we need in these:
1) If you specify nothing, you should get the default.
2) If you specify a CAfile, and there is no failure in loading it,
you shou
Hi,
it occured to me that this patch that I submitted quite a while ago still
hasn't been merged and discussion about it back then got stuck due to a
release being prepared or something--so, here I submit it again, though you
might want to read the discussion on the thread from 2014 that I am
repl
14 matches
Mail list logo
