Re: Shorewall-nft

Dave Kempe <[email protected]> Mon, 20 Jul 2026 09:24:24 +1000
Newsgroups gmane.comp.security.shorewall
Message-ID <CAEc_UVRP2Wyw90bRxomxvF5oHN29A2LRvw4e92Qe=x6QH6Oj+Q@mail.gmail.com>
--===============1438927837916750285==
Content-Type: multipart/alternative; boundary="000000000000e675380656ff17e8"

--000000000000e675380656ff17e8
Content-Type: text/plain; charset="UTF-8"

Thanks Tom. I want to thank you for all your efforts over the years. We
have built a small but enduring business in part thanks to you.
If we can give back by maintaining a suitable replacement, that would be
great. We can only hope to aspire to the determination and dedication you
have shown.

I will be in touch if there is anything we need to clarify. At this time,
the subject I'm most curious about is how you determined which features to
support or not?
Some of the shorewall features are pretty obscure, so I spose it comes down
to demand. I'm keen to make sure the power and simplicity of shorewall are
maintained.

Thanks
DavId Kempe


On Mon, 20 Jul 2026 at 07:43, Tom Eastep <[email protected]> wrote:

> Hello All,
>
> For some reason, I did not receive David's initial posting on this
> subject, so I am commenting outside of the existing email thread.
>
> It is gratifying to hear that Shorewall will live on in this new form,
> and I am grateful to David and his team for their efforts in this regard.
>
> David: Please feel free to contact me if you think that there is
> anything that I could contribute to your efforts.
>
> Regards,
>
> -Tom
>
>
>
> _______________________________________________
> Shorewall-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/shorewall-users
>

--000000000000e675380656ff17e8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks Tom. I want to thank you for all your efforts =
over the years. We have built a small but enduring business in part thanks =
to you.=C2=A0</div><div>If we can give back by maintaining a suitable repla=
cement, that would be great. We can only hope to aspire to the determinatio=
n and dedication you have shown.</div><div><br></div><div>I will be in touc=
h if there is anything we need to clarify. At this time, the subject I&#39;=
m most curious about is how you determined which features to support or not=
?=C2=A0</div><div>Some of the shorewall features are pretty obscure, so I s=
pose it comes down to demand. I&#39;m keen to make sure the power and simpl=
icity of shorewall are maintained.</div><div><br></div><div>Thanks</div><di=
v>DavId Kempe</div><div><br></div></div><br><div class=3D"gmail_quote gmail=
_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, 20 Jul 2026=
 at 07:43, Tom Eastep &lt;<a href=3D"mailto:[email protected]">teastep@=
shorewall.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">Hello All,<br>
<br>
For some reason, I did not receive David&#39;s initial posting on this <br>
subject, so I am commenting outside of the existing email thread.<br>
<br>
It is gratifying to hear that Shorewall will live on in this new form, <br>
and I am grateful to David and his team for their efforts in this regard.<b=
r>
<br>
David: Please feel free to contact me if you think that there is <br>
anything that I could contribute to your efforts.<br>
<br>
Regards,<br>
<br>
-Tom<br>
<br>
<br>
<br>
_______________________________________________<br>
Shorewall-users mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">=
[email protected]</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/shorewall-users" re=
l=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/list=
info/shorewall-users</a><br>
</blockquote></div>

--000000000000e675380656ff17e8--


--===============1438927837916750285==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============1438927837916750285==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline