Re: [Mailman-Users] Critical security update for Mailman 2.1.5 and earlier

Can this be applied to any 2.1 release? I am running 2.1 at the moment. Thanks. > Until Mailman 2.1.6 is released, the longer term fix is to apply this > patch: > > http://www.list.org/CAN-2005-0202.txt -- Mailman-Users mailing list Mailm

Re: [Mailman-Users] Critical security update for Mailman 2.1.5 and earlier

OK, thanks. With no modifications it did not apply, but I can probably get it to work. It shouldn't cause any issues w/ 2.1 should it? Thanks. Quoting Ralf Hildebrandt <[EMAIL PROTECTED]>: * AJ <[EMAIL PROTECTED]>: Can this be applied to any 2.1 release? I am running 2.1 at the

Re: [Mailman-Users] Re: Critical security update for Mailman 2.1.5

Patch seems ok on 2.1. Is there a way to test if it's working and we are protected? Maybe someone can respond offlist with a test URL of some kind that would trigger a log in the mischief log. Thanks. On Feb 10, 2005, at 8:17 AM, [EMAIL PROTECTED] wrote: Am I correct in assuming the attack onl

Re: [Mailman-Users] Re: Critical security update for Mailman 2.1.5

How can we test that the patch is working? Is there a way to cause the log message to be written to the mischief log? Just want to make sure the patch is working, any help would be great. Thanks. On Feb 10, 2005, at 8:17 AM, [EMAIL PROTECTED] wrote: Am I correct in assuming the attack only allo

Re: [Mailman-Users] Re: Critical security update for Mailman 2.1.5

This also stripped it down for me. I do not see any logs in error or mischief. How can I get it to actually log the attempt so I know this is working. Thanks. Quoting Tokio Kikuchi <[EMAIL PROTECTED]>: AJ wrote: How can we test that the patch is working? Is there a way to cause the log mess

[Mailman-Users] Problem with list_lists

somewhere, but what list? What order do these programs parse the lists? Running the list_admins command also bombs after going through the same 6 lists. I need to know what the next list is that these commands parse. That is most likely the bad list. Any help would be appreciated. AJ Here

[Mailman-Users] Re: protecting the web interface against subscription spam

lists have custom listinfo.html pages. Any clue on where else to look? Thanks AJ On Fri, Mar 5, 2021 at 9:44 AM Brian Carpenter wrote: > On 3/5/21 9:31 AM, jor...@gmail.com wrote: > > currently we get inundated with abuse complaint mails because our > > mailman instance is tar

[Mailman-Users] Re: protecting the web interface against subscription spam

ee this, with the correct site key:  This form requires JavaScript.https://www.google.com/recaptcha/api.js?hl=en"</a>;> On Fri, Mar 5, 2021 at 4:38 PM Mark Sapiro wrote: > On 3/5/21 1:24 PM, AJ wrote: &g

[Mailman-Users] Re: protecting the web interface against subscription spam

PM, Al Brussey wrote: > > Yes they are v2 keys. > > > >> On Mar 5, 2021, at 5:28 PM, Mark Sapiro wrote: > >> > >> On 3/5/21 2:10 PM, AJ wrote: > >>> > >>> View source of page, i see this, with the correct site key:

[Mailman-Users] Re: protecting the web interface against subscription spam

Sure will do. Thanks so much. On Mon, Mar 8, 2021 at 11:37 AM Brian Carpenter wrote: > On 3/8/21 11:27 AM, AJ wrote: > > Just confirmed, the mailman server can reach the Google reCaptcha URL. > > I also tried different browsers. I do see the ReCaptcha on here: > > ht

[Mailman-Users] Re: protecting the web interface against subscription spam

Just to close this out. It wound up being a Content Security Policy on the apache server. Thanks to all for their help. On Fri, Mar 5, 2021 at 9:32 PM Mark Sapiro wrote: > On 3/5/21 6:14 PM, Al Brussey wrote: > > There is nothing between the digest question and the submit button. > > > > When I

[Mailman-Users] new setup

enSSL/0.9.8 PHP/5.0.5 DAV/2 mod_perl/2.0.1 Perl/v5.8.7 Thanks for the help -AJ Peck PS, i'm not a linux guru, so it's possible I messed up in the install somewhere, but didn't realize it. -- Mailman-Users ma