[leaf-devel] What happens now?
Paul Gear wrote: Tom has finally admitted what some of us have thought all along. The day had to come. If you get to the point where you're not happy with your life, something has to give. And since none of us owe you anything, i think you've made the right choice, Tom. Best of luck and God bless. Thank you Paul. Righto, lads! Now what are we going to do about this? I for one am reluctant to lose shorewall, as it is the only firewall i trust. As for the mechanics of shorewall.net going away: we have a functional sourceforge.net project page and web site for shorewall. If Tom is willing, perhaps he could add some of us on the devel list as project admins on his sf.net page, and we could make sure all of the right information is copied over from his site. I will be happy to add additional admins at SF. Am i right in remembering that lists.shorewall.net is hosted elsewhere, Tom? No, lists.shorewall.net is hosted here in my home. It's the same box as http://shorewall.net which is the system that all of the mirrors (including www.shorewall.net) rsync from. I don't mind continuing to host the mailing lists here for a while until mailing lists can be reestablished at SF (they were there once upon a time). - We need to look at the big issues and make sure we've got a good handle on them. For me, these include (in rough order of priority from my perspective): * Multiple ISPs load balancing * Features to enable building a personal firewall with shorewall * IPv6 I think that is a good list. I hope to have the first (multiple ISPs/Load-balancing) completed in release 2.4.0 (it should work in the current CVS code but I have to lash together a test bed to try it). I'll still run a beta/RC-series for that release so it should be fairly solid by the time that I throw it over the wall for good. Netfilter is weak on features for a personal firewall. I have added support for the 'owner' match (including 'owner-cmd') but that isn't a strong enough base to build what most people think of as a personal firewall. IPV6 is a big job -- that will keep folks busy coding for a while :-) -Tom -- Tom Eastep\ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] RE: [Shorewall-users] I quit.
Tom, Your support had been so valuable as the shorewall itself. It has been a pleasure reading your replies on this channel. Shorewall has brought so much credibility to many net admins (and the would be net admins:-))from the Top Management of their organizations. And with shorewall many have made a career in Linux Administration and Networking even if they do not know the ABC of iptables and networking. As an user of the shorewall, My Hats Off to You. If it is possible , we would like to hear from you often in whatever form. Thank You and Hope you enjoy the break. Best Regards Siva -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Tom Eastep Sent: Wednesday, May 18, 2005 8:47 AM To: Shorewall Users; Shorewall Announcements; LEAF; leaf-devel@lists.sourceforge.net; Tarry Eastep Subject: [Shorewall-users] I quit. It is with regret that I announce that Shorewall development and support is officially ended. Sean's post has finally driven it home to me that in the long term, trying to support a project like Shorewall is impossible for a person of my personality and age. Sean -- please believe that this isn't about you or your post -- your post was just the proverbial straw on this old camel's back. Unlike the originators of other successful open source projects, I have not been able to attract a core of people who believe in Shorewall and who are willing to make sacrifices to ensure it's success. That is my weakness and I accept it. But is means that I have been left with trying to develop, document, and support Shorewall almost single-handedly. I cannot do it any more. I have apparently been able to create the illusion of more success than has been achieved. Sean believes that he should be able to ignore the notices on the Shorewall 1.3 web site announcing that support for that release has ceased and thinks that the errata page should still have updated Shorewall components for a release that my 60 year old mind can't remember most of the details about. And he is right to expect that. But I can't deliver it. And I just cannot deal with the support and documentation frustration any more -- support, the documentation and the web site consume an order of magnitude more of my time than does Shorewall development. Apparently, I am completely inept at web site design because people just can't find the information that they need; and I have no more energy to try to fix it. Since I began developing Shorewall: a) I have gained over 60 pounds in weight. b) My lawn and landscaping have become an embarrassment in the neighborhood. c) I have begun exhibiting addictive behavior toward Linux and Shorewall. d) I have developed sleep disorders (I use a breathing aid at night) e) I dislike my life. It's time to get myself cleaned up and re-enter the life of the living. I will leave the Shorewall website and server in place until July 4 in case there is any community interest in picking up the pieces. Please email me privately if you are interested in carrying on; I'll do what I can to help. Tonight I am deleting myself from all of the Shorewall and Leaf mailing lists. I will clean up what I have for a 2.3 release and place it on the server as the last Shorewall release -- Shorewall 2.4.0. I would like to express my appreciation for all who have used Shorewall and who have enriched my life through Shorewall. I especially appreciate: - Steve Cowles who helped me so much in the early days - Francesca Smith who picked up the sample configurations when I had had it with them - Mike Noyes who was always willing to help improve the documentation. I regret letting down those of you who depend on Shorewall. But look at it this way -- you have the source for all of the code that you run and it's all written in a very simple programming language. And there was always the possiblilty that I would walk in front of a bus. ... and you have to admit that the price was right :-) Shorewall will always be a part of my life that I look back on with fondness. As always, -Tom -- Tom Eastep\ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_idt12alloc_id344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] RE: [Shorewall-users] I quit.
All, I am prepared to host the website/domain, is there a group of people that are willing to be active in the ongoing support/development of shorewall? Regards, T -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Eastep Sent: Wednesday, 18 May 2005 1:17 PM To: Shorewall Users; Shorewall Announcements; LEAF; leaf-devel@lists.sourceforge.net; Tarry Eastep Subject: [Shorewall-users] I quit. It is with regret that I announce that Shorewall development and support is officially ended. Sean's post has finally driven it home to me that in the long term, trying to support a project like Shorewall is impossible for a person of my personality and age. Sean -- please believe that this isn't about you or your post -- your post was just the proverbial straw on this old camel's back. Unlike the originators of other successful open source projects, I have not been able to attract a core of people who believe in Shorewall and who are willing to make sacrifices to ensure it's success. That is my weakness and I accept it. But is means that I have been left with trying to develop, document, and support Shorewall almost single-handedly. I cannot do it any more. I have apparently been able to create the illusion of more success than has been achieved. Sean believes that he should be able to ignore the notices on the Shorewall 1.3 web site announcing that support for that release has ceased and thinks that the errata page should still have updated Shorewall components for a release that my 60 year old mind can't remember most of the details about. And he is right to expect that. But I can't deliver it. And I just cannot deal with the support and documentation frustration any more -- support, the documentation and the web site consume an order of magnitude more of my time than does Shorewall development. Apparently, I am completely inept at web site design because people just can't find the information that they need; and I have no more energy to try to fix it. Since I began developing Shorewall: a) I have gained over 60 pounds in weight. b) My lawn and landscaping have become an embarrassment in the neighborhood. c) I have begun exhibiting addictive behavior toward Linux and Shorewall. d) I have developed sleep disorders (I use a breathing aid at night) e) I dislike my life. It's time to get myself cleaned up and re-enter the life of the living. I will leave the Shorewall website and server in place until July 4 in case there is any community interest in picking up the pieces. Please email me privately if you are interested in carrying on; I'll do what I can to help. Tonight I am deleting myself from all of the Shorewall and Leaf mailing lists. I will clean up what I have for a 2.3 release and place it on the server as the last Shorewall release -- Shorewall 2.4.0. I would like to express my appreciation for all who have used Shorewall and who have enriched my life through Shorewall. I especially appreciate: - Steve Cowles who helped me so much in the early days - Francesca Smith who picked up the sample configurations when I had had it with them - Mike Noyes who was always willing to help improve the documentation. I regret letting down those of you who depend on Shorewall. But look at it this way -- you have the source for all of the code that you run and it's all written in a very simple programming language. And there was always the possiblilty that I would walk in front of a bus. ... and you have to admit that the price was right :-) Shorewall will always be a part of my life that I look back on with fondness. As always, -Tom -- Tom Eastep\ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Re: [Shorewall-users] I quit.
Your passion shone through. Thank you. Tom Eastep wrote: It is with regret that I announce that Shorewall development and support is officially ended. Sean's post has finally driven it home to me that in the long term, trying to support a project like Shorewall is impossible for a person of my personality and age. Sean -- please believe that this isn't about you or your post -- your post was just the proverbial straw on this old camel's back. Unlike the originators of other successful open source projects, I have not been able to attract a core of people who believe in Shorewall and who are willing to make sacrifices to ensure it's success. That is my weakness and I accept it. But is means that I have been left with trying to develop, document, and support Shorewall almost single-handedly. I cannot do it any more. I have apparently been able to create the illusion of more success than has been achieved. Sean believes that he should be able to ignore the notices on the Shorewall 1.3 web site announcing that support for that release has ceased and thinks that the errata page should still have updated Shorewall components for a release that my 60 year old mind can't remember most of the details about. And he is right to expect that. But I can't deliver it. And I just cannot deal with the support and documentation frustration any more -- support, the documentation and the web site consume an order of magnitude more of my time than does Shorewall development. Apparently, I am completely inept at web site design because people just can't find the information that they need; and I have no more energy to try to fix it. Since I began developing Shorewall: a) I have gained over 60 pounds in weight. b) My lawn and landscaping have become an embarrassment in the neighborhood. c) I have begun exhibiting addictive behavior toward Linux and Shorewall. d) I have developed sleep disorders (I use a breathing aid at night) e) I dislike my life. It's time to get myself cleaned up and re-enter the life of the living. I will leave the Shorewall website and server in place until July 4 in case there is any community interest in picking up the pieces. Please email me privately if you are interested in carrying on; I'll do what I can to help. Tonight I am deleting myself from all of the Shorewall and Leaf mailing lists. I will clean up what I have for a 2.3 release and place it on the server as the last Shorewall release -- Shorewall 2.4.0. I would like to express my appreciation for all who have used Shorewall and who have enriched my life through Shorewall. I especially appreciate: - Steve Cowles who helped me so much in the early days - Francesca Smith who picked up the sample configurations when I had had it with them - Mike Noyes who was always willing to help improve the documentation. I regret letting down those of you who depend on Shorewall. But look at it this way -- you have the source for all of the code that you run and it's all written in a very simple programming language. And there was always the possiblilty that I would walk in front of a bus. ... and you have to admit that the price was right :-) Shorewall will always be a part of my life that I look back on with fondness. As always, -Tom Subject: Re: [leaf-user] New RFC1918 file needed? From: Sean Covel [EMAIL PROTECTED] Date: Tue, 17 May 2005 22:02:18 -0400 To: Tom Eastep [EMAIL PROTECTED] To: Tom Eastep [EMAIL PROTECTED] CC: LEAF User leaf-user@lists.sourceforge.net Tom, Tom Eastep wrote: Sean Covel wrote: I looked under errata for 1.3.14 and the rfc1918 file that was there was old. I guess that one is more up-to-date. Sean -- There is one up-to-date rfc1918 file for Shorewall versions up to 2.0.1 linked from the top of the errata page. Do you actually think I have enough spare time to prepare separate updated rfc1918 files (which have the same contents) for each of the dozens of Shorewall releases that included Bogon address ranges in that file? Especially Shorewall releases that have not been supported for over two years (Hint: 1.3.14 falls into that category)?? Since I'm not a Shorewall developer, I assumed I should look under the errata for the version of Shorewall I was using. How am I to know that every version of Shorewall from xxx to yyy had exactly the same format for the rfc1918 file? Do you actually believe that the list of "bad" IP addresses is dependent on which verison of Shorewall your are running? Please THINK when you sit down to your computer. Ouch! Having a bad day? Obviously "bad" IP addresses are not Shorewall version dependant, but are rfc1918 files? How should I know? Besides, I
[leaf-devel] Re: [Shorewall-announce] I quit.
Tom Eastep wrote: It is with regret that I announce that Shorewall development and support is officially ended. Tom: Thanks for everything you've done. And stay well. Regards, Micha --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] I quit.
It is with regret that I announce that Shorewall development and support is officially ended. Sean's post has finally driven it home to me that in the long term, trying to support a project like Shorewall is impossible for a person of my personality and age. Sean -- please believe that this isn't about you or your post -- your post was just the proverbial straw on this old camel's back. Unlike the originators of other successful open source projects, I have not been able to attract a core of people who believe in Shorewall and who are willing to make sacrifices to ensure it's success. That is my weakness and I accept it. But is means that I have been left with trying to develop, document, and support Shorewall almost single-handedly. I cannot do it any more. I have apparently been able to create the illusion of more success than has been achieved. Sean believes that he should be able to ignore the notices on the Shorewall 1.3 web site announcing that support for that release has ceased and thinks that the errata page should still have updated Shorewall components for a release that my 60 year old mind can't remember most of the details about. And he is right to expect that. But I can't deliver it. And I just cannot deal with the support and documentation frustration any more -- support, the documentation and the web site consume an order of magnitude more of my time than does Shorewall development. Apparently, I am completely inept at web site design because people just can't find the information that they need; and I have no more energy to try to fix it. Since I began developing Shorewall: a) I have gained over 60 pounds in weight. b) My lawn and landscaping have become an embarrassment in the neighborhood. c) I have begun exhibiting addictive behavior toward Linux and Shorewall. d) I have developed sleep disorders (I use a breathing aid at night) e) I dislike my life. It's time to get myself cleaned up and re-enter the life of the living. I will leave the Shorewall website and server in place until July 4 in case there is any community interest in picking up the pieces. Please email me privately if you are interested in carrying on; I'll do what I can to help. Tonight I am deleting myself from all of the Shorewall and Leaf mailing lists. I will clean up what I have for a 2.3 release and place it on the server as the last Shorewall release -- Shorewall 2.4.0. I would like to express my appreciation for all who have used Shorewall and who have enriched my life through Shorewall. I especially appreciate: - Steve Cowles who helped me so much in the early days - Francesca Smith who picked up the sample configurations when I had had it with them - Mike Noyes who was always willing to help improve the documentation. I regret letting down those of you who depend on Shorewall. But look at it this way -- you have the source for all of the code that you run and it's all written in a very simple programming language. And there was always the possiblilty that I would walk in front of a bus. ... and you have to admit that the price was right :-) Shorewall will always be a part of my life that I look back on with fondness. As always, -Tom -- Tom Eastep\ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ---BeginMessage--- Tom, Tom Eastep wrote: Sean Covel wrote: I looked under errata for 1.3.14 and the rfc1918 file that was there was old. I guess that one is more up-to-date. Sean -- There is one up-to-date rfc1918 file for Shorewall versions up to 2.0.1 linked from the top of the errata page. Do you actually think I have enough spare time to prepare separate updated rfc1918 files (which have the same contents) for each of the dozens of Shorewall releases that included Bogon address ranges in that file? Especially Shorewall releases that have not been supported for over two years (Hint: 1.3.14 falls into that category)?? Since I'm not a Shorewall developer, I assumed I should look under the errata for the version of Shorewall I was using. How am I to know that every version of Shorewall from xxx to yyy had exactly the same format for the rfc1918 file? Do you actually believe that the list of bad IP addresses is dependent on which verison of Shorewall your are running? Please THINK when you sit down to your computer. Ouch! Having a bad day? Obviously bad IP addresses are not Shorewall version dependant, but are rfc1918 files? How should I know? Besides, I went to the Shorewall site, clicked on the version I am running, then clicked on the errata for that version. Is this what I did wrong? Perhaps if that rfc1918 was a link to the one you maintained we wouldn't be having this discussion... And for your other question, I aggregate adjacent ranges whereas the IANA lists them separately. Thanks, good info. Sean -Tom
[leaf-devel] Re: [Shorewall-announce] I quit.
Tom Eastep wrote: It is with regret that I announce that Shorewall development and support is officially ended. Sean's post has finally driven it home to me that in the long term, trying to support a project like Shorewall is impossible for a person of my personality and age. ... Unlike the originators of other successful open source projects, I have not been able to attract a core of people who believe in Shorewall and who are willing to make sacrifices to ensure it's success. That is my weakness and I accept it. But is means that I have been left with trying to develop, document, and support Shorewall almost single-handedly. I cannot do it any more. ... I will leave the Shorewall website and server in place until July 4 in case there is any community interest in picking up the pieces. Please email me privately if you are interested in carrying on; I'll do what I can to help. Tonight I am deleting myself from all of the Shorewall and Leaf mailing lists. I will clean up what I have for a 2.3 release and place it on the server as the last Shorewall release -- Shorewall 2.4.0. Tom has finally admitted what some of us have thought all along. The day had to come. If you get to the point where you're not happy with your life, something has to give. And since none of us owe you anything, i think you've made the right choice, Tom. Best of luck and God bless. Righto, lads! Now what are we going to do about this? I for one am reluctant to lose shorewall, as it is the only firewall i trust. As for the mechanics of shorewall.net going away: we have a functional sourceforge.net project page and web site for shorewall. If Tom is willing, perhaps he could add some of us on the devel list as project admins on his sf.net page, and we could make sure all of the right information is copied over from his site. Am i right in remembering that lists.shorewall.net is hosted elsewhere, Tom? On the more long-term side, we probably need to have a discussion about the direction of shorewall. I have a some of suggestions to start with, which we probably should start a new thread before talking about: - A slightly slower, more conservative release strategy. Tom has been compulsively adding features for the last several years as soon as he gets one request for something that sounds interesting. - We need to look at the big issues and make sure we've got a good handle on them. For me, these include (in rough order of priority from my perspective): * Multiple ISPs load balancing * Features to enable building a personal firewall with shorewall * IPv6 -- Paul http://paulgear.webhop.net -- Did you know? Microsoft Internet Explorer and Outlook have a poor track record for security http://www.kb.cert.org/vuls/id/713878. Why not try one of the more secure alternatives from http://mozilla.org? signature.asc Description: OpenPGP digital signature
Re: [leaf-devel] What happens now?
On Wed, 2005-05-18 at 08:25, Tom Eastep wrote: Paul Gear wrote: As for the mechanics of shorewall.net going away: we have a functional sourceforge.net project page and web site for shorewall. If Tom is willing, perhaps he could add some of us on the devel list as project admins on his sf.net page, and we could make sure all of the right information is copied over from his site. I will be happy to add additional admins at SF. Tom, If you need help with SF, let me know. Am i right in remembering that lists.shorewall.net is hosted elsewhere, Tom? No, lists.shorewall.net is hosted here in my home. It's the same box as http://shorewall.net which is the system that all of the mirrors (including www.shorewall.net) rsync from. I don't mind continuing to host the mailing lists here for a while until mailing lists can be reestablished at SF (they were there once upon a time). The SF staff will even import your pipermail archive, so the content isn't lost. SF will upgrade Mailman shortly too, so the list settings shouldn't need much tweaking. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] What happens now?
Mike Noyes wrote: If you need help with SF, let me know. Am i right in remembering that lists.shorewall.net is hosted elsewhere, Tom? No, lists.shorewall.net is hosted here in my home. It's the same box as http://shorewall.net which is the system that all of the mirrors (including www.shorewall.net) rsync from. I don't mind continuing to host the mailing lists here for a while until mailing lists can be reestablished at SF (they were there once upon a time). The SF staff will even import your pipermail archive, so the content isn't lost. SF will upgrade Mailman shortly too, so the list settings shouldn't need much tweaking. Ok -- I appreciate the offer to help. Let's wait until SF have upgraded then hopefully we can move the lists pretty much intact over there. -Tom -- Tom Eastep\ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] What happens now?
On Wed, 2005-05-18 at 09:22, Tom Eastep wrote: Mike Noyes wrote: I don't mind continuing to host the mailing lists here for a while until mailing lists can be reestablished at SF (they were there once upon a time). The SF staff will even import your pipermail archive, so the content isn't lost. SF will upgrade Mailman shortly too, so the list settings shouldn't need much tweaking. Ok -- I appreciate the offer to help. Let's wait until SF have upgraded then hopefully we can move the lists pretty much intact over there. Tom, That sounds good. Have you considered moving CVS? I believe you haven't migrated to SVN, so CVS tarball import by the SF staff is possible. Maybe tarball the repository after your last release? -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] What happens now?
On Wed, 2005-05-18 at 09:22, Tom Eastep wrote: Mike Noyes wrote: The SF staff will even import your pipermail archive, so the content isn't lost. SF will upgrade Mailman shortly too, so the list settings shouldn't need much tweaking. Tom, Correction: MBOX import is supported. No pipermail support. Sorry for the confusion. Ok -- I appreciate the offer to help. Let's wait until SF have upgraded then hopefully we can move the lists pretty much intact over there. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] I quit.
Tom: My very best wishes for a happy and healthy future for you. And my congrats and appreciation for what you achieved with Shorewall; it remains an excellent implementation. cheers, Scott On May 17, 2005, at 8:17 PM, Tom Eastep wrote: It is with regret that I announce that Shorewall development and support is officially ended. snip --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] What happens now?
Mike Noyes wrote: On Wed, 2005-05-18 at 09:22, Tom Eastep wrote: Mike Noyes wrote: I don't mind continuing to host the mailing lists here for a while until mailing lists can be reestablished at SF (they were there once upon a time). The SF staff will even import your pipermail archive, so the content isn't lost. SF will upgrade Mailman shortly too, so the list settings shouldn't need much tweaking. Ok -- I appreciate the offer to help. Let's wait until SF have upgraded then hopefully we can move the lists pretty much intact over there. Tom, That sounds good. Have you considered moving CVS? I believe you haven't migrated to SVN, so CVS tarball import by the SF staff is possible. Maybe tarball the repository after your last release? Yes -- that will work fine. -Tom -- Tom Eastep\ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Re: what to do about shorewall?
Paul Traina wrote: [Tom, just cc'ing you if you want to chime in about the stability/appropriateness of 2.3] So as you guys know, I made the shorewall packages for BU based on the stable 2.2 branch of shorewall. If shorewall is moved from shorewall.net to sourceforge and taken over by someone else, we can change the buildtool.cfg files to take it from the new place. However, we have more immediate concerns. If Tom shuts down shorewall.net, where should the source files remain? Even more important, for the next version of BU, do you want me to release the shorewall package based upon 2.2 (stable) or 2.3? 2.3 adds native support for upnpd. The current upnpd package also supports shorewall 2.2, but it will be more of a transition for people if we're going to upgrade later for 2.3. IMO, if Tom thinks the core functionality in 2.3 is stable enough, I would like to report to 2.3 and remove my shorewall integration hacks from upnpd. What do you guys want to do? Paul, At this point, 2.3 is only half-baked. The last feature that I'm adding is support for multiple ISPs -- that code is fresh off the press and isn't well tested. I would suggest that you wait until I release 2.4.0 then update the Bering build. I plan to go through a normal Beta cycle for 2.4.0 so it should get some good testing. It is likely that the CVS tree will be moved to Sourceforge after 2.4.0 is released. That seems to me to be the best place to put it to ensure that it is always available. -Tom PS -- I've subscribed myself to the leaf-devel list again so I can help with this transition. -- Tom Eastep\ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] What happens now?
Tom; Many thanks to you from the Bering(-uclibc) developers as well. Shorewall made iptables easy and helped a lot to build a secure box. All the best to you - we will miss you. Am Mittwoch, 18. Mai 2005 17:25 schrieb Tom Eastep: Paul Gear wrote: - We need to look at the big issues and make sure we've got a good handle on them. For me, these include (in rough order of priority from my perspective): * Multiple ISPs load balancing * Features to enable building a personal firewall with shorewall * IPv6 I think that is a good list. I hope to have the first (multiple ISPs/Load-balancing) completed in release 2.4.0 (it should work in the current CVS code but I have to lash together a test bed to try it). I'll still run a beta/RC-series for that release so it should be fairly solid by the time that I throw it over the wall for good. Netfilter is weak on features for a personal firewall. I have added support for the 'owner' match (including 'owner-cmd') but that isn't a strong enough base to build what most people think of as a personal firewall. IPV6 is a big job -- that will keep folks busy coding for a while :-) If someone wants to jump in, the 6wall code, written by Eric de Thouars, is in LEAF Bering-uClibc cvs. kp --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] I quit.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tom Eastep wrote: | It is with regret that I announce that Shorewall development and support is | officially ended. Tom, First, many thanks for creating the firewall that I now use to replace the customized scripts from my earlier LRP/LEAF releases. I know of no better way to say how much I (and many others, I'm sure!) appreciate your work than to let you know it is being used in production environments. Having supported my own LRP/LEAF distributions, I can fully appreciate your reasons for needing to step aside, and the mixture of emotions that creates. I feel it is safe to say that Shorewall will not go quietly into the night, and that it will take many dedicated people to shoulder the burden you've been carrying for quite some time. | I regret letting down those of you who depend on Shorewall. But look at it | this way -- you have the source for all of the code that you run and it's | all written in a very simple programming language. And there was always the | possiblilty that I would walk in front of a bus. | | ... and you have to admit that the price was right :-) You are not letting us down in any way. The contribution you've made to everyone using shorewall is immense, and realized everytime someone downloads a version of shorewall or reads any of the (excellent) online documentation. As others have offered, I can provide any hosting services (via existing CoLo servers) that might be required and cannot be fulfilled by sourceforge. In addition, I am beginning to have a bit more free time and may be able to help with ongoing development. | Shorewall will always be a part of my life that I look back on with fondness. Those of us who use (and will hopefully continue to use) shorewall will always remember your dedication, your tireless responses to queries for help, the quality of your code, and the effort you expended which made our burdens lighter. For all this and more, thank you! - -- Charles Steinkuehler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCi3voLywbqEHdNFwRAvNKAJ9DNjk6SFNoxmsp2o9siqAqqfwXLwCg6M/t laFluaAza/PAuqLzB8BLjoo= =fxpi -END PGP SIGNATURE- --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Re: [Shorewall-announce] I quit.
It is with regret that I announce that Shorewall development and support is officially ended. Hi Tom, All I can say is THANK YOU very much for all the hard work you have put into Shorewall and it's great documentation and the best support I have seen in my life. I hope you will get your life back and relax and enjoy. You really did so much for all of us. Simon --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_idt12alloc_id344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] What happens now?
On Wed, 2005-05-18 at 10:18, Tom Eastep wrote: Mike Noyes wrote: Have you considered moving CVS? I believe you haven't migrated to SVN, so CVS tarball import by the SF staff is possible. Maybe tarball the repository after your last release? Yes -- that will work fine. Tom, SourceForge Site Doc F2 outlines the procedure for import of an existing CVS repository. Introduction to SourceForge.net Project CVS Services for Developers Import of Existing CVS Repositories https://sourceforge.net/docman/display_doc.php?docid=768group_id=1#existingcvsimport -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Re: [Shorewall-devel] What happens now?
Cristian Rodriguez wrote:
2005/5/18, Tom Eastep [EMAIL PROTECTED]:
- We need to look at the big issues and make sure we've got a good
handle on them. For me, these include (in rough order of priority from
my perspective):
* Multiple ISPs load balancing
* Features to enable building a personal firewall with shorewall
* IPv6
My ideas are the following:
1. Declare Shorewall alive but feature frozen,only bug fixes, until
we can organize and get the needed coders,especially some good bash
coders and an iptables geek (¿anyone?)
After 2.4.0 is out...
2.I can take care of a mirror and enrole me to the website and
documentation. team.(please¡)
I think that we already have enough mirrors -- I think that the issue of
where to place the rsync server and how to keep the mirrors and
sourceforge synced needs addressing. Basically, we need someone to be
Webmaster.
Since you are volunteering ...
I've attached the simple scripts that I use to publish to Sourceforge
and to my own server (shorewall.net AKA lists.shorewall.net AKA
cvs.shorewall.net AKA rsync.shorewall.net).
The way that this works currently is that I run 'publish' which:
a) Converts files from XML to HTML if the original file is XML.
b) Uses SCP to copy the file(s) to my server and to sourceforge (you
will need a user account on Sourceforge).
All of the current documentation and the website files are in CVS
(Shorewall-Website/ and Shorewall-docs2/).
Possibly Mike Noyes can help you with coming up with a new arrangement;
he has offered to help with things at the Sourceforge end. I'm uncertain
how to set up a publishing scheme based at Sourceforge that can keep the
mirrors updated.
One of the flukes with the HTML documentation is that part of the files
have an .htm extension and part have .html. The attached 'publish'
script depends on a ../Website directory to be populated with the .htm
files. The script that I use to build Shorewall releases
(http://shorewall.net/pub/shorewall/contrib/makeshorewall.sh) includes a
list of the .htm files -- that's a better approach but I just never got
around to adding it to the publish script (if it ain't broke, don't fix it).
Both the publish and makeshorewall scripts require recent Docbook XML
tools to be installed.
I use XXE (Xmlmind XML Editor -- http://www.xmlbind.com/xmleditor) to
edit the Docbook XML files. The standard version is free and it's a nice
WYSIWYG editor.
Note that there are two different files used for the Left Frame on the
website -- one for Sourceforge and one for the other sites (Sourceforge
has Logo requirements for the sites that they host).
I publish those files using an scp command rather than the publish script.
Example for Sourceforge:
scp Shorewall_sfindex_frame.htm
shorewall.sf.net:/home/groups/s/sh/shorewall/htdocs/Shorewall_index_frame.htm
3. Files,mailist,and cvs stuff should be transfered to SF and a
help needed item opened.
Nod -- we will move the mailing lists when Sourceforge has upgraded
their Mailman installation (I'm currently running a later release of
mailman so our files aren't compatible). CVS will be moved after 2.4.0.
4. creat a more conservative release schema. IMHO shorewall have most
of the needed features,but ipv6 is a good new one.
That is in line with Paul's recommendation.
-Tom
--
Tom Eastep\ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ [EMAIL PROTECTED]
PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
#!/bin/sh
#STYLESHEET=/home/teastep/Shorewall/docbook-xsl-1.62.4//xhtml/docbook.xsl
STYLESHEET=/usr/share/xml/docbook/stylesheet/nwalsh/current/xhtml/docbook.xsl
WEBSITE=/home/teastep/Shorewall/Website
if [ $# -eq 0 ]; then
echo Usage: $(basename $0) XML file ...
exit 2
fi
while [ $# -gt 0 ]; do
case $1 in
*.xml)
b=${1%.*}
if [ -f ../Website/$b.htm ]; then
b=$b.htm
f=$WEBSITE/$b
else
b=$b.html
f=$WEBSITE/$b
fi
echo Converting $1 from XML to HTML ($b) ...
if xmllint --valid --noout $1 xsltproc --output $f --stringparam
html.stylesheet html.css -param toc.section.depth 3 $STYLESHEET $1 ; then
filestocopy=$filestocopy $f
fi
;;
*)
filestocopy=$filestocopy $1
;;
esac
shift
done
if [ -n $filestocopy ]; then
for f in $filestocopy; do
filestoreport=$filestoreport $(basename $f)
done
echo Copying$filestoreport to SourceForge...
scp $filestocopy [EMAIL PROTECTED]:/home/groups/s/sh/shorewall/htdocs
/dev/null
echo Copying$filestoreport to Mail...
scp -p $filestocopy [EMAIL PROTECTED]:/var/www/html /dev/null
fi
#!/bin/sh
scp $@ [EMAIL PROTECTED]:/home/groups/s/sh/shorewall/htdocs/images
scp -p $@ [EMAIL PROTECTED]:/var/www/html/images
# cp -pf $@
Re: [leaf-devel] Re: [Shorewall-devel] What happens now?
On Wed, 2005-05-18 at 11:57, Tom Eastep wrote: Cristian Rodriguez wrote: Possibly Mike Noyes can help you with coming up with a new arrangement; he has offered to help with things at the Sourceforge end. I'm uncertain how to set up a publishing scheme based at Sourceforge that can keep the mirrors updated. Tom, Do you pull or push with rsync? SF doesn't offer public rsync hosting. Only project members with shell access can rsync to/from the shell. I use a script on SF to xslt docbook xml to html. It's not great, but it does work. One good thing, the public uri for docbook xsl files is local to the SF shell. daily.sh http://cvs.sourceforge.net/viewcvs.py/leaf/sourceforge/admin/ Note: cron was just re-enabled by the SF staff. There are some new restrictions to be aware of though. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Re: [Shorewall-devel] What happens now?
Mike Noyes wrote: Do you pull or push with rsync? SF doesn't offer public rsync hosting. Only project members with shell access can rsync to/from the shell. Currently, all of the mirrors pull from rsync.shorewall.net. I use a script on SF to xslt docbook xml to html. It's not great, but it does work. One good thing, the public uri for docbook xsl files is local to the SF shell. Nod. daily.sh http://cvs.sourceforge.net/viewcvs.py/leaf/sourceforge/admin/ Note: cron was just re-enabled by the SF staff. There are some new restrictions to be aware of though. Ok -- I think I have a place where we can host an rsync server for the mirrors; I'll continue this thought in another thread. -Tom -- Tom Eastep\ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Re: [Shorewall-devel] What happens now?
On Wed, 2005-05-18 at 12:28, Cristian Rodriguez wrote: 2005/5/18, Tom Eastep [EMAIL PROTECTED]: I've attached the simple scripts that I use to publish to Sourceforge and to my own server (shorewall.net AKA lists.shorewall.net AKA cvs.shorewall.net AKA rsync.shorewall.net). http://ftp.belnet.be/ and others are providing rsync mirror,what we need is a master rsync server,sadly providing the hardware and bandwith for that is out of my possibilities :( anyone at leaf or Mandriva can help with this issue??? Cristian, Charles may be willing and able to help. He hosts the leaf master rsync site. -- Mike Noyes mhnoyes at users.sourceforge.net http://sourceforge.net/users/mhnoyes/ SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] Re: [Shorewall-devel] What happens now?
Paul Gear wrote: Cristian Rodriguez wrote: ... My ideas are the following: 1. Declare Shorewall alive but feature frozen,only bug fixes, until we can organize and get the needed coders,especially some good bash coders and an iptables geek (¿anyone?) 2.I can take care of a mirror and enrole me to the website and documentation. team.(please¡) 3. Files,mailist,and cvs stuff should be transfered to SF and a help needed item opened. 4. creat a more conservative release schema. IMHO shorewall have most of the needed features,but ipv6 is a good new one. hope it helps. ps: please if you have comments,or help is needed with tech issues,drop me a personal email. That all seems fairly reasonable. Tom, would you mind summarising for the -devel list all of the offers you've received so we can take stock? Ok -- I'll try. I've received several hundred emails today and I'm a bit overwhelmed. I've had many offers for mirror hosting -- I don't see additional mirrors as a priority at this point. I've been trying to steer those with a real interest to the Leaf and Shorewall development lists where they can participate in these discussions. a) You (Paul) have been added as an administrator at SF (Thanks!). b) Mike Noyes who works closely with the SF staff has offered his help on that end. c) Charles Steinkuehler (of Leaf fame) has offered hosting services and may have some time to code (Sorry I haven't gotten back to you Charles -- as you can imagine, this has been a wild day). d) Cristian has offered to help with Documentation/Web site management as has Alex Wilms. e) Jim Richardson has offered to head development. f) Ron Shannon has offered operational support and has surplus storage and bandwidth. g) Ian Allen has offered to help code (He also has two ADSL lines so he can test the Multi-ISP support in 2.3/2.4). I hope that I haven't forgotten anyone -- If I have, please speak up. I think we have a core group here who can carry things forward. I'm available help get things transferred off of my server but I think the less that I have to say about how this plays out from here, the better. -Tom -- Tom Eastep\ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_idt12alloc_id344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Re: [Shorewall-devel] What happens now?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Noyes wrote: | On Wed, 2005-05-18 at 12:28, Cristian Rodriguez wrote: | 2005/5/18, Tom Eastep [EMAIL PROTECTED]: | I've attached the simple scripts that I use to publish to Sourceforge | and to my own server (shorewall.net AKA lists.shorewall.net AKA | cvs.shorewall.net AKA rsync.shorewall.net). | | http://ftp.belnet.be/ and others are providing rsync mirror,what we | need is a master rsync server,sadly providing the hardware and | bandwith for that is out of my possibilities :( | | anyone at leaf or Mandriva can help with this issue??? | | Cristian, | Charles may be willing and able to help. He hosts the leaf master rsync | site. Yes, I can host a master rsync site for shorewall at either of two CoLo locations (100 MBit/s 45 MBit/s) with hardware that's already in place. I'm already doing this for the leaf CVS archives (import the daily SF CVS tarball and make it available via rsync) so users can mirror the Leaf CVS directory w/o having to download the entire tarball (now multiple GBytes). Just let me know what you'd like setup. We can probably get something running on either SF or the rsync server (or both) that auto-magically builds and/or syncs the site and it's mirrors, works like Tom's publish script, or whatever is desired... - -- Charles Steinkuehler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCi7y3LywbqEHdNFwRAoT7AKDQZS6Fmv5p30Cohf89t7tplCKkcwCg7Xq9 6BNfugAxpZTw+E/nytOVF6M= =VPfH -END PGP SIGNATURE- --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] I quit.
On Tuesday 17 May 2005 10:17 pm, Tom Eastep wrote: It is with regret that I announce that Shorewall development and support is officially ended. Tom, The enormous amount of time and energy you have put in to develop, promote, and support Shorewall has been appreciated more than you will likely ever know. I understand the need to put your life back together, as I have been working on doing that myself for an extended amount of time. Thank-you for all you have done, it will not be forgotten. Best wishes on your future! ~Lynn -- ~Lynn Avants Linux Embedded Appliance Firewall Developer http://leaf.sourceforge.net http://guitarlynn.homelinux.org:81 --- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412alloc_id=16344op=click ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
