Re: [Chicken-users] wiki spam merging issue

2008-02-17 Thread Alejandro Forero Cuervo
This makes sense. However, since spam is apparently bypassing authorization --the index page can't be edited anonymously--and also logging, I was concerned there is a more critical underlying problem. It might even affect more than the index page. I have upgraded the version of Svnwiki

Re: [Chicken-users] wiki spam merging issue

2008-02-16 Thread felix winkelmann
On Feb 16, 2008 6:32 AM, Jim Ursetto [EMAIL PROTECTED] wrote: Hi, It appears that authorized, legitimate wiki edits to random pages are causing simultaneous commits to the 'index' page, which consists of spam in the form of an SVN merge conflict. Can someone look into this? I think

Re: [Chicken-users] wiki spam merging issue

2008-02-16 Thread felix winkelmann
On Feb 17, 2008 12:22 AM, felix winkelmann [EMAIL PROTECTED] wrote: On Feb 16, 2008 6:32 AM, Jim Ursetto [EMAIL PROTECTED] wrote: Hi, It appears that authorized, legitimate wiki edits to random pages are causing simultaneous commits to the 'index' page, which consists of spam in the

Re: [Chicken-users] wiki spam merging issue

2008-02-16 Thread Jim Ursetto
This makes sense. However, since spam is apparently bypassing authorization --the index page can't be edited anonymously--and also logging, I was concerned there is a more critical underlying problem. It might even affect more than the index page. On 2/16/08, felix winkelmann [EMAIL PROTECTED]

Re: [Chicken-users] wiki spam merging issue

2008-02-16 Thread Elf
problem is as follows, methinks: when something fails auth, it still is saved to a reject file, just like normal svn. the problem is that once something succeeds in auth, then any rejects are automatically appended. now, we cant just get rid of rejects in the event that someone mistypes

[Chicken-users] wiki spam merging issue

2008-02-15 Thread Jim Ursetto
Hi, It appears that authorized, legitimate wiki edits to random pages are causing simultaneous commits to the 'index' page, which consists of spam in the form of an SVN merge conflict. Check `svn log index` and notice that quite a few recent commits follow this pattern. For example, svn diff

Re: [Chicken-users] wiki spam

2006-08-30 Thread Alejandro Forero Cuervo
1. Other than the latest cialis attack, were most spam attempts automated or not? As far as I know, there hasn't been a single automated attack against a wiki powered by svnwiki (but there's probably going to be one at some point). 2. There's catchpa and there's catchpa. One could use

Re: [Chicken-users] wiki spam

2006-08-29 Thread Alejandro Forero Cuervo
I've contacted Alejandro to see what we can do regarding to this problem. Since this problem obviously affects all installations of svnwiki, not just Galinha, I posted a small wiki article about how to defend against attacks and my thoughts on things svnwiki could do, in the future, to make it

Re: [Chicken-users] wiki spam

2006-08-29 Thread Dan
Just a few remarks -- 1. Other than the latest cialis attack, were most spam attempts automated or not? 2. There's catchpa and there's catchpa. One could use something as simple as What is one plus five minus three? or, at the other end, require the poster to solve a Sudoku puzzle generated by

[Chicken-users] wiki spam

2006-08-28 Thread Hans Bulfone
hi, it seems that some spammer has found the chicken wiki and has put a lot of order cialis online and other links on it :( bye, hans. ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] wiki spam

2006-08-28 Thread Mario Domenech Goulart
Hello Hans, On Mon, 28 Aug 2006 17:27:10 +0200 Hans Bulfone [EMAIL PROTECTED] wrote: it seems that some spammer has found the chicken wiki and has put a lot of order cialis online and other links on it :( Thanks for notifying. I think I could revert most os the vandalism (at least searching

Re: [Chicken-users] wiki spam

2006-08-28 Thread Dan
Thanks for notifying. I think I could revert most os the vandalism (at least searching for cialis doesn't return anything anymore). This will probably turn into a frequent business, from what I've heard about other wikis. Perhaps make the wiki password-protected, and give the password out