On Thu, Feb 11, 2016 at 2:54 AM, Martin Pieuchot wrote:
> There's only one symbol table since we no longer support LKMs. So this
> function is useless.
>
> Ok to kill it?
Burn it down
Michael Savage wrote:
> I found an integer overflow in syslogd which can be triggered by
> compiling and running:
>
> #include
> #include
> #include
>
> int main( int argc, char ** argv ) {
> const char * msg = "<> hello";
> return sendsyslog( msg, strlen( msg ) );
>
Hi Gilles,
Please find my diff inline to enable "listen on socket" feature that we have
discussed. I have tested the diff with currently two supported listen options
for this listener, mask-sender and filter. Everything seems to be working OK.
These are the summary of the changes:
* Parser was ad
On 20:24:02, 11.02.16, Nicholas Marriott wrote:
> Hi
>
> On Thu, Feb 11, 2016 at 08:05:54PM +0100, Michal Mazurek wrote:
> > Hello,
> >
> > I know the code is now locked, but I'd like to ask for comments on the
> > following diff.
> >
> > I believe that page-up and halfpage-up should have the sa
On 2016/02/11 13:34, Todd C. Miller wrote:
> On Thu, 11 Feb 2016 10:39:53 +, Stuart Henderson wrote:
>
> > I updated some firewalls to -current yesterday (from somewhere between
> > 5.6 and 5.7) and am now seeing a lot of "arp: attempt to add entry"
> > logged, see below. (Looks like someone h
I found an integer overflow in syslogd which can be triggered by
compiling and running:
#include
#include
#include
int main( int argc, char ** argv ) {
const char * msg = "<> hello";
return sendsyslog( msg, strlen( msg ) );
}
The problematic code is a hand-rolled
On Thu, 11 Feb 2016 10:39:53 +, Stuart Henderson wrote:
> I updated some firewalls to -current yesterday (from somewhere between
> 5.6 and 5.7) and am now seeing a lot of "arp: attempt to add entry"
> logged, see below. (Looks like someone has put a machine on the wrong
> vlan and it's sending
Hi
On Thu, Feb 11, 2016 at 08:05:54PM +0100, Michal Mazurek wrote:
> Hello,
>
> I know the code is now locked, but I'd like to ask for comments on the
> following diff.
>
> I believe that page-up and halfpage-up should have the same effect as
> running scroll-up (^Y) the equivalent number of tim
Sebastien Marie writes:
> Hi,
>
> I noted that calling traceroute with -nA result to pledge to abort.
>
> $ traceroute -nA openbsd.org
> traceroute to openbsd.org (129.128.5.194), 64 hops max, 40 byte packets
> Abort trap (core dumped)
>
> It is due because with -n we don't request for "dns" pro
Hi,
I noted that calling traceroute with -nA result to pledge to abort.
$ traceroute -nA openbsd.org
traceroute to openbsd.org (129.128.5.194), 64 hops max, 40 byte packets
Abort trap (core dumped)
It is due because with -n we don't request for "dns" promise, whereas
-A (Look up the AS number f
Hello,
I know the code is now locked, but I'd like to ask for comments on the
following diff.
I believe that page-up and halfpage-up should have the same effect as
running scroll-up (^Y) the equivalent number of times. There are two
differences:
- with line select active ('V' by default) pgup/pgd
On Thu, Feb 11, 2016 at 01:09:27PM -0500, Michael Reed wrote:
> nvi2[1]'s man page has diverged a bit from our own. I think many of the
> changes are for the better, although not all; because of that I'll be sending
> a patch to nvi2 after this.
>
> To ease review, this patch only includes the lo
nvi2[1]'s man page has diverged a bit from our own. I think many of the
changes are for the better, although not all; because of that I'll be sending
a patch to nvi2 after this.
To ease review, this patch only includes the low hanging fruit--primarily typo
fixes and using correct macros.
[1]: h
The current A-MPDU reordering code is being fed with not just QoS data
frames but also QoS "no data" frames. Such frames do not contain sequence
numbers and our reordering buffer logic will treat them as if they did.
QoS frame subtype fields (in binary) and their corresponding names are:
1000 QoS
I ran into this issue when setting up my public_html folder using this
configuration.
prefork 2
server "default" {
listen on * port 80
location match "/~*" {
root "/users"
}
}
types {
text/csscss
text/html html htm
text/txtt
On 2016/02/11 10:39, Stuart Henderson wrote:
> Other examples of the splitting:
And an extra-special blank one here :-)
Feb 11 12:51:50 fw1 /bsd: arp: attempt to add entry for 192.168.43.131 on
carp432 by 00:26:b9:5d:24:e7 on vlan411
Feb 11 12:51:50 fw1 /bsd: arp: attempt to add entry for 192.16
Alexander Bluhm writes:
> On Mon, Feb 08, 2016 at 01:53:20PM +0100, Christian Ehrhardt wrote:
>> The diff was initially done for 5.7, bluhm@ did the forward port
>> to current. The resulting diff is below.
>
> I am running this diff with my Thinkpad T430s, no problems so far.
>
> em0 at pci0 dev
There's only one symbol table since we no longer support LKMs. So this
function is useless.
Ok to kill it?
Index: ddb/db_sym.c
===
RCS file: /cvs/src/sys/ddb/db_sym.c,v
retrieving revision 1.43
diff -u -p -r1.43 db_sym.c
--- ddb/db_
I updated some firewalls to -current yesterday (from somewhere between
5.6 and 5.7) and am now seeing a lot of "arp: attempt to add entry"
logged, see below. (Looks like someone has put a machine on the wrong
vlan and it's sending out broadcast arp replies for conflict detection
which are triggerin
19 matches
Mail list logo