From: Yaroslav H. <li...@on...> - 2011-09-28 18:08:28
|
Since there were no objections -- only approvals, and I even got a pull request (against old SVN->GIT clone of mine) -- please welcome new remastered GIT repository (based on the fail2ban-rewritten I have mentioned earlier): https://github.com/fail2ban/fail2ban N.B. chose lower case for consistency -- camel casing still looks awkward for me in the URLs It's master includes already a pull request from Adam Spiers; I will be able to cherry-pick limited number of commits from SVN if there would be any new ones, but altogether please use this GIT repository from now on. To avoid confusion -- I have removed fail2ban-rewritten from my github account and renamed Fail2Ban into Fail2Ban-Old-SVNGIT. I also adjusted wiki.fail2ban.org to point to the GIT repository. N.B. Unfortunately fail2ban's wiki is still a madness of spam -- I have removed some entries and fixed a link to community portal but I am not a mediawiki expert to bring it back to order (nor I think I could alter user groups rights to disallow at least creation of new pages/talks by people to prevent more spam). If you know mediawiki and are willing to help -- please let me know... If you are new to GIT -- WELCOME into the heaven of version control ;) There is loads of docs/tutorials/howtos on the web. http://help.github.com/ has some nice one with "hooks" into specifics of github (pull requests, code review, etc), so should be a good start. So, once again for completeness -- the structure of new GIT repository * master -- tracks what was FAIL2BAN-0.8 branch, ie what we use and love so it would be preferable if that would be the 'default' branch * 0.x -- what was trunk -- some initial changes by Cyril toward not-happened release * all release tags are just plain release numbers (without any prefix) * debian*/* -- tags and branches related to debian packaging later on some branches will be deprecated so it will end up with only debian and debian-releases/* branches * sdist/* tags -- contact source distribution code (was used as origin for debian packages) * pristine-tar -- contains original distributed tarballs, as stored extracted pointed by sdist/* tags. pristine-tar allows to fetch them pristine, with checksums preserved * _tent/* -- some feature branches with my tentative changes... may be eventually would be removed from this official clone and placed into mine ok -- enjoy! send in your pull requests ;) -- =------------------------------------------------------------------= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic |
From: Arturo 'B. B. <bu...@bu...> - 2011-09-28 19:26:12
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Thank you very much Yaroslav for all of this work! On 09/28/2011 03:08 PM, Yaroslav Halchenko wrote: > Since there were no objections -- only approvals, and I even got a pull > request (against old SVN->GIT clone of mine) -- please welcome new remastered > GIT repository (based on the fail2ban-rewritten I have mentioned earlier): > > https://github.com/fail2ban/fail2ban > > N.B. chose lower case for consistency -- camel casing still looks > awkward for me in the URLs > > It's master includes already a pull request from Adam Spiers; I will be able > to cherry-pick limited number of commits from SVN if there would be any new > ones, but altogether please use this GIT repository from now on. To avoid > confusion -- I have removed fail2ban-rewritten from my github account and > renamed Fail2Ban into Fail2Ban-Old-SVNGIT. I also adjusted wiki.fail2ban.org > to point to the GIT repository. > > N.B. Unfortunately fail2ban's wiki is still a madness of spam -- I have removed > some entries and fixed a link to community portal but I am not a mediawiki > expert to bring it back to order (nor I think I could alter user groups rights > to disallow at least creation of new pages/talks by people to prevent > more spam). If you know mediawiki and are willing to help -- please let > me know... > > If you are new to GIT -- WELCOME into the heaven of version control ;) There > is loads of docs/tutorials/howtos on the web. http://help.github.com/ has some > nice one with "hooks" into specifics of github (pull requests, code review, > etc), so should be a good start. > > So, once again for completeness -- the structure of new GIT repository > > * master -- tracks what was FAIL2BAN-0.8 branch, ie what we use and love > so it would be preferable if that would be the 'default' branch > > * 0.x -- what was trunk -- some initial changes by Cyril toward > not-happened release > > * all release tags are just plain release numbers (without any prefix) > > * debian*/* -- tags and branches related to debian packaging > later on some branches will be deprecated so it will end up with only > debian and debian-releases/* branches > > * sdist/* tags -- contact source distribution code (was used as origin > for debian packages) > > * pristine-tar -- contains original distributed tarballs, as stored > extracted pointed by sdist/* tags. pristine-tar allows to fetch them pristine, > with checksums preserved > > * _tent/* -- some feature branches with my tentative changes... may be > eventually would be removed from this official clone and placed into mine > > ok -- enjoy! send in your pull requests ;) > - -- ? Arturo "Buanzo" Busleiman ? - http://soundcloud.com/no-carrier - Independent Linux and Security Consultant - 16+y of IT exp. at your service . OWASPer - http://www.buanzo.com.ar/pro/eng.html ..: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREKAAYFAk6DaGEACgkQAlpOsGhXcE1KeACcDNcosWjX0rVX84qj2MmvRllr qUQAmwU1aqiJrAYhZVnkq/AqGRNqJWpy =XIsA -----END PGP SIGNATURE----- |
From: Cyril J. <cyr...@fa...> - 2011-09-29 10:06:43
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, > N.B. Unfortunately fail2ban's wiki is still a madness of spam -- I > have removed some entries and fixed a link to community portal but > I am not a mediawiki expert to bring it back to order (nor I think > I could alter user groups rights to disallow at least creation of > new pages/talks by people to prevent more spam). If you know > mediawiki and are willing to help -- please let me know... > So here is what I've done: 1/ E-mail address is required in the account creation page. 2/ The e-mail address must have been confirmed by the user in order to create or edit pages. 3/ Captcha have been disabled for simple edition. Still required for account creation, page creation, external URLs, etc. I hope this won't discourage the "good" users to edit the wiki and will decrease the amount of spam. We can still fine-tune the access rights, captcha, groups later is needed. Cheers, Cyril -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6EPy8ACgkQlYy8cEwUMaRNCACfYA+8a5vDlhVF/wpq2ARw2nuQ lxwAoIPaijSPTsOn21+znTFK2QoU1y7F =2atM -----END PGP SIGNATURE----- |
From: Arturo 'B. B. <bu...@bu...> - 2011-09-29 13:10:55
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I was wondering, is there an stopforumspam plugin for mediawiki? On 09/29/2011 06:49 AM, Cyril Jaquier wrote: > Hi all, > >> N.B. Unfortunately fail2ban's wiki is still a madness of spam -- I >> have removed some entries and fixed a link to community portal but >> I am not a mediawiki expert to bring it back to order (nor I think >> I could alter user groups rights to disallow at least creation of >> new pages/talks by people to prevent more spam). If you know >> mediawiki and are willing to help -- please let me know... > > > So here is what I've done: > > 1/ E-mail address is required in the account creation page. > > 2/ The e-mail address must have been confirmed by the user in order to > create or edit pages. > > 3/ Captcha have been disabled for simple edition. Still required for > account creation, page creation, external URLs, etc. > > I hope this won't discourage the "good" users to edit the wiki and > will decrease the amount of spam. > > We can still fine-tune the access rights, captcha, groups later is needed. > > Cheers, > Cyril > - ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Fail2ban-users mailing list Fai...@li... https://lists.sourceforge.net/lists/listinfo/fail2ban-users - -- ? Arturo "Buanzo" Busleiman ? - http://soundcloud.com/no-carrier - Independent Linux and Security Consultant - 16+y of IT exp. at your service . OWASPer - http://www.buanzo.com.ar/pro/eng.html ..: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREKAAYFAk6EblEACgkQAlpOsGhXcE0jCgCfbt7EjueoxB+XlDdUvt1c9pbh losAnA1pZ/DYChFRVRStOt43s3P401Qr =zvF7 -----END PGP SIGNATURE----- |
From: Cyril J. <cyr...@fa...> - 2011-10-03 20:50:34
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I disabled the Subversion repository on SF.net. So Github: https://github.com/fail2ban/fail2ban is now the official place to get the code. Many thanks to Yaroslav for the migration. Hope you will all enjoy Git ;-) Cheers, Cyril On 09/28/2011 08:08 PM, Yaroslav Halchenko wrote: > Since there were no objections -- only approvals, and I even got a > pull request (against old SVN->GIT clone of mine) -- please welcome > new remastered GIT repository (based on the fail2ban-rewritten I > have mentioned earlier): > > https://github.com/fail2ban/fail2ban > > N.B. chose lower case for consistency -- camel casing still looks > awkward for me in the URLs > > It's master includes already a pull request from Adam Spiers; I > will be able to cherry-pick limited number of commits from SVN if > there would be any new ones, but altogether please use this GIT > repository from now on. To avoid confusion -- I have removed > fail2ban-rewritten from my github account and renamed Fail2Ban into > Fail2Ban-Old-SVNGIT. I also adjusted wiki.fail2ban.org to point to > the GIT repository. > > N.B. Unfortunately fail2ban's wiki is still a madness of spam -- I > have removed some entries and fixed a link to community portal but > I am not a mediawiki expert to bring it back to order (nor I think > I could alter user groups rights to disallow at least creation of > new pages/talks by people to prevent more spam). If you know > mediawiki and are willing to help -- please let me know... > > If you are new to GIT -- WELCOME into the heaven of version control > ;) There is loads of docs/tutorials/howtos on the web. > http://help.github.com/ has some nice one with "hooks" into > specifics of github (pull requests, code review, etc), so should be > a good start. > > So, once again for completeness -- the structure of new GIT > repository > > * master -- tracks what was FAIL2BAN-0.8 branch, ie what we use and > love so it would be preferable if that would be the 'default' > branch > > * 0.x -- what was trunk -- some initial changes by Cyril toward > not-happened release > > * all release tags are just plain release numbers (without any > prefix) > > * debian*/* -- tags and branches related to debian packaging later > on some branches will be deprecated so it will end up with only > debian and debian-releases/* branches > > * sdist/* tags -- contact source distribution code (was used as > origin for debian packages) > > * pristine-tar -- contains original distributed tarballs, as > stored extracted pointed by sdist/* tags. pristine-tar allows to > fetch them pristine, with checksums preserved > > * _tent/* -- some feature branches with my tentative changes... may > be eventually would be removed from this official clone and placed > into mine > > ok -- enjoy! send in your pull requests ;) > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6KIA0ACgkQlYy8cEwUMaS47QCfUu9V//xHshFmrzTSL5jHSXZF gWkAnA42LJOirkyn1nvy9VkJm1GltjBQ =I0bv -----END PGP SIGNATURE----- |