Re: Trimming tcpdump a bit

2014-11-25 Thread Stuart Henderson
On 2014/11/24 09:59, Theo de Raadt wrote: > Thing is, in a few cases we have de-forked as well. For instance, in > less(1). Hmm, kind of relevant recently.. Fortunately we don't have ours use lesspipe by default :-)

Re: Trimming tcpdump a bit

2014-11-24 Thread Mike Belopuhov
On 24 November 2014 at 16:42, Mike Belopuhov wrote: > Hi, > > I've been trying to fix a bug in tcpdump but the rottenness > of the current code base with it's horrendous APIs is just > getting in the way. What if we trimmed it a bit, say killed > all those pesky 'register' values, kill protocols

Re: Trimming tcpdump a bit

2014-11-24 Thread Theo de Raadt
> >> I've been trying to fix a bug in tcpdump but the rottenness > >> of the current code base with it's horrendous APIs is just > >> getting in the way. What if we trimmed it a bit, say killed > >> all those pesky 'register' values, That would be cleanup, which then allows the code to be improve

Re: Trimming tcpdump a bit

2014-11-24 Thread Mike Belopuhov
On 24 November 2014 at 18:01, Mike Belopuhov wrote: > On 24 November 2014 at 17:20, Mike Belopuhov wrote: >> On 24 November 2014 at 16:42, Mike Belopuhov wrote: >>> Hi, >>> >>> I've been trying to fix a bug in tcpdump but the rottenness >>> of the current code base with it's horrendous APIs is j

Re: Trimming tcpdump a bit

2014-11-24 Thread Mike Belopuhov
On 24 November 2014 at 17:20, Mike Belopuhov wrote: > On 24 November 2014 at 16:42, Mike Belopuhov wrote: >> Hi, >> >> I've been trying to fix a bug in tcpdump but the rottenness >> of the current code base with it's horrendous APIs is just >> getting in the way. What if we trimmed it a bit, say

Re: Trimming tcpdump a bit

2014-11-24 Thread Theo de Raadt
> On 2014/11/24 16:42, Mike Belopuhov wrote: > > Hi, > > > > I've been trying to fix a bug in tcpdump but the rottenness > > of the current code base with it's horrendous APIs is just > > getting in the way. What if we trimmed it a bit, say killed > > all those pesky 'register' values, kill proto

Re: Trimming tcpdump a bit

2014-11-24 Thread Stuart Henderson
On 2014/11/24 16:42, Mike Belopuhov wrote: > Hi, > > I've been trying to fix a bug in tcpdump but the rottenness > of the current code base with it's horrendous APIs is just > getting in the way. What if we trimmed it a bit, say killed > all those pesky 'register' values, kill protocols that we >

Re: Trimming tcpdump a bit

2014-11-24 Thread Mike Belopuhov
On 24 November 2014 at 16:42, Mike Belopuhov wrote: > Hi, > > I've been trying to fix a bug in tcpdump but the rottenness > of the current code base with it's horrendous APIs is just > getting in the way. What if we trimmed it a bit, say killed > all those pesky 'register' values, kill protocols

Trimming tcpdump a bit

2014-11-24 Thread Mike Belopuhov
Hi, I've been trying to fix a bug in tcpdump but the rottenness of the current code base with it's horrendous APIs is just getting in the way. What if we trimmed it a bit, say killed all those pesky 'register' values, kill protocols that we cannot really test (appletalk, fddi, etc.), kill dissect