File reg_startend patch
Author: matthew Date: 2007-03-04 12:28:29 -0700 (Sun, 04 Mar 2007) New Revision: 7956 snip Upgrade to File-4.20. Fixes #1968. snip +paraApply a patch to fix a bug caused by an undefined constant:/para + +screenuserinputpatch -Np1 -i ../file-reg_startend-patch;/userinput/screen Umm, why are you applying this patch? Just because it appears on the ftp site? AFAICT it does nothing for us. It applies only to those platforms who don't define REG_STARTEND in their system headers eg: Solaris. You can easily confirm it does nothing on Linux/Glibc by compiling with and without the patch then diffing the binaries. They are identical (except for usual date stamps in the *.a archive). Regards Greg -- http://www.diy-linux.org/ -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: File reg_startend patch
On Saturday 07 April 2007 13:35, Greg Schafer wrote: Umm, why are you applying this patch? Just because it appears on the ftp site? Nope, I did actually take a look at the source code and erroneously concluded it was necessary as REG_STARTEND wasn't defined. Obviously, I forgot to take into account system headers. /usr/include/regex.h defines REG_STARTEND, and this file is included by src/file.h, which, in turn, is included by src/softmagic.c. Thanks Greg, I'll remove the patch some time this week. Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Spam in trac tickets
I deleted spam from lfs-book and blfs-book, both mail and trac tickets, this morning. Do we need to make the books ticket system so only authorized (vice registered) users can create or modify tickets? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
[new XSL] Ready for inputs.
Hi, Looks like the stylesheets revision for LFS is done for now, until have DocBook-xsl-1.72.1 available. The unique visible change in the XHTML output is that chapters TOC has been added, as was suggested. An on-line version is available here: http://www.lfs-es.info/new-lfs-book/ In PDF output there are several changes. To can compare it, both the current PDF and the new one can be downloaded from here: http://www.lfs-es.info/new-lfs-book/fop0-lfs-book.pdf current PDF http://www.lfs-es.info/new-lfs-book/fop1-lfs-book.pdf new PDF I'm awaiting your comments, sugestions and complaints, not only about the outputs look but also about the documentational comments in the stylesheets, before start working on the BLFS stylesheets update. -- Manuel Canales Esparcia Usuario de LFS nÂș2886: http://www.linuxfromscratch.org LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info TLDP-ES: http://es.tldp.org -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Spam in trac tickets
On Sat, Apr 07, 2007 at 12:03:36PM -0500, Bruce Dubbs wrote: I deleted spam from lfs-book and blfs-book, both mail and trac tickets, this morning. Do we need to make the books ticket system so only authorized (vice registered) users can create or modify tickets? You did? I also deleted a bunch of spammish comments from the LFS trac database about an hour ago. The corresponding messages still appear in the mailman archives, though, and I'm not sure how to get rid of them. For example: http://linuxfromscratch.org/pipermail/lfs-book/2007-April/062123.html As far as the LFS ticket system goes, it's already set so that only authorized users can modify tickets. However, I think it's open to anyone to register. I'm not sure how the BLFS system is set up. -- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Spam in trac tickets
On Saturday 07 April 2007 18:03, Bruce Dubbs wrote: I deleted spam from lfs-book and blfs-book, both mail and trac tickets, this morning. Do we need to make the books ticket system so only authorized (vice registered) users can create or modify tickets? Bruce, The LFS Trac is already configured to only allow authenticated users to modify or create tickets. I've not seen any ticket spam in lfs-book, maybe it's just mail-spam that you had to delete this morning? Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Spam in trac tickets
Matthew Burgess wrote: On Saturday 07 April 2007 18:03, Bruce Dubbs wrote: I deleted spam from lfs-book and blfs-book, both mail and trac tickets, this morning. Do we need to make the books ticket system so only authorized (vice registered) users can create or modify tickets? Bruce, The LFS Trac is already configured to only allow authenticated users to modify or create tickets. I've not seen any ticket spam in lfs-book, maybe it's just mail-spam that you had to delete this morning? The bots register and leave a comment. I cleaned 3 spam items out of the clfs trac this morning. I was hoping someone might have some helpful insight on libtool when i saw the email, but it was just spam :(. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Spam in trac tickets
Jeremy Huntwork wrote: On Sat, Apr 07, 2007 at 12:03:36PM -0500, Bruce Dubbs wrote: I deleted spam from lfs-book and blfs-book, both mail and trac tickets, this morning. Do we need to make the books ticket system so only authorized (vice registered) users can create or modify tickets? You did? I also deleted a bunch of spammish comments from the LFS trac database about an hour ago. The corresponding messages still appear in the mailman archives, though, and I'm not sure how to get rid of them. For example: http://linuxfromscratch.org/pipermail/lfs-book/2007-April/062123.html As far as the LFS ticket system goes, it's already set so that only authorized users can modify tickets. However, I think it's open to anyone to register. I'm not sure how the BLFS system is set up. Yes, I did. There were several in blfs-book and lfs-book that were made this morning. They were from a user named 'zlgdgzl' which was the most recent registered 'user'. The comments were copied from another legitimate ticket and had a spammish link attached. The first comment looked legitimate (except for the link), but all the others were exact copies. You are right about the registration. Anyone can register and then spam away on both the lfs and blfs trac ticket systems. About the only thing I can think of is to require an admin to verify and explicitly allow the creation or update capabilities for new registrations. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: Spam in trac tickets
On Sat, 07 Apr 2007 19:05:51 -0500, Bruce Dubbs [EMAIL PROTECTED] wrote: Yes, I did. There were several in blfs-book and lfs-book that were made this morning. They were from a user named 'zlgdgzl' which was the most recent registered 'user'. The comments were copied from another legitimate ticket and had a spammish link attached. The first comment looked legitimate (except for the link), but all the others were exact copies. Odd. Those were the same ones I deleted. So one of us missed some or we were working on top of each other. :) -- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Fighting spam via greylisting
Greetings All, Inspired by an email from Richard Downing, I decided to look into using greylisting to help fight spam. If you haven't heard of it before see: http://www.greylisting.org The basic idea is that whenever a new MTA (one that is not in the greylisting database) attempts to deliver mail, the mail is automatically rejected. If the MTA is a valid MTA, it will retry to deliver the mail after a few minutes. At this point the greylisting server recognizes the MTA from a previous attempt and assumes that it is valid mail. The address of the sending MTA is added to the database and future messages from that server are automatically allowed (at least for a while). I tried a Postfix implementation called Postgrey on my own personal server and the results were very good. (See http://postgrey.schweikert.ch/). Based on those results it was decided to implement this service on Quantum. Quantum already had SpamAssassin installed and it uses some nice Postfix reject rules to keep a good deal of spam at bay. Combine that with the fact that the mailing lists require a valid subscription to post and the result is that most spam never reaches the end users. Even so, a good deal of spam gets past SpamAssassin and Postfix and hits Mailman. And therein lies the problem we wish to avoid. Even though mailman rejects the message, the processing time mailman spends is expensive. Our hope is to eliminate a good deal of spam before it even 'enters' the system, so to speak. Be advised that your first post to a mailing list might be delayed by a few minutes. If it takes a considerably long time, or if you receive an undeliverable message from your MTA, please let us know at server-admin AT linuxfromscratch DOT org so that we can adjust our whitelisting files. If you have a linuxfromscratch.org mail account and you would rather not have greylisting applied to your personal mail at all, please send a message to server-admin and we can add your account to the whitelisting rules as well. -- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page