Re: [patch] Re: Possible sasyncd memory leak ?

On Thu, Mar 21, 2019 at 12:51:11AM +0100, Klemens Nanni wrote: > > On Tue, Mar 12, 2019 at 03:19:56PM +0100, Otto Moerbeek wrote: > > > I also fixed a case of parsing IPv6 addresses. > > > > > > Anyone willing to ok? > See comments inline. > > > And now also with a lexer bug fixed. Earlier I

Re: [patch] Re: Possible sasyncd memory leak ?

W dniu 21.03.2019 o 07:21, Otto Moerbeek pisze: On Thu, Mar 21, 2019 at 12:51:11AM +0100, Klemens Nanni wrote: On Tue, Mar 12, 2019 at 03:19:56PM +0100, Otto Moerbeek wrote: I also fixed a case of parsing IPv6 addresses. Anyone willing to ok? See comments inline. And now also with a lexer

Re: [patch] Re: Possible sasyncd memory leak ?

On Thu, Mar 21, 2019 at 09:28:28AM +0100, Michał Koc wrote: > W dniu 21.03.2019 o 07:21, Otto Moerbeek pisze: > > On Thu, Mar 21, 2019 at 12:51:11AM +0100, Klemens Nanni wrote: > > > On Tue, Mar 12, 2019 at 03:19:56PM +0100, Otto Moerbeek wrote: > > > > > I also fixed a case of parsing IPv6

Re: [patch] Re: Possible sasyncd memory leak ?

On Thu, Mar 21, 2019 at 11:52:56AM +0100, Otto Moerbeek wrote: > Meanwhile, I tested a IPv6 setup, it works ok. > So I'm going to commit the diff below, Thanks! OK kn

WE BUY YOUR VPN BUSINESS

Good Morning there! My name is Steven Endrizzi, I am the CEO of BizBroker24, BizBroker24 is the Worldwide Mergers & Acquisitions Leader in Buying & Selling Websites & Internet Businesses. I am reaching you because you are a well known VPN company in the industry. I was wondering if you are

Re: Option for alternative escape character with cu(1)

I will commit this in the next few days unless I hear objections. On Mon, Mar 18, 2019 at 07:39:45AM +, Nicholas Marriott wrote: > > This is OK with me, anyone else? > > > On Fri, Mar 15, 2019 at 06:56:31PM +0200, Artturi Alm wrote: > > On Fri, Mar 15, 2019 at 02:43:04PM +,

Re: [patch] Re: Possible sasyncd memory leak ?

Otto Moerbeek wrote: This lex operation seems ridiculous. Normal one does lex of free-standing digit sequences into a "number token" only if the sequence is fully digits -- see the code around pfctl/parse.y line 5368 Or don't lex numbers instead, but consider them strings (with the correct

Re: pfctl should allow administrator to flush _anchors

Hello, I'm giving up on identifying unreferenced/orphaned rulesets. It seems to me like too much work/complexity, which invites more troubles. I prefer to keep things simple, hence I'm proposing new modifier for Flush option: -F Nuke Flush all rulesets and tables. The option is meant