Re: [mantisbt-dev] 1.2.18 release

[Robert M. <rob...@gm...>]

(Sorry for asking but not contributing to this fix, but .... ) do we
need to wait for Paul's patches or can someone come up with a security
fix?

I think it's not reponsibile towards our users to wait for someone to
produce a security fix for such a long time.

Cheers,

Robert

On Sun, Oct 19, 2014 at 2:09 AM, P Richards <pa...@ma...> wrote:
> Apparently your email address doesn't work correctly - at least (rather
> amusingly) google isn't allowing a google user to email another google user:
>
> Delivery to the following recipient failed permanently:
>
>      dr...@ma...
>
> Technical details of permanent failure:
> Message rejected by Google Groups. Please visit
> http://mail.google.com/support/bin/answer.py?hl=en&answer=188131 to review
> our Bulk Email Senders Guidelines.
>
> ----- Original message -----
>
> X-Received: by 10.180.85.102 with SMTP id g6mr8889617wiz.54.1413672671965;
>         Sat, 18 Oct 2014 05:51:11 -0700 (PDT)
> Return-Path: <pa...@ma...>
> Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com.
> [209.85.212.175])
>         by mx.google.com with ESMTPS id
> r8si3539198wiy.73.2014.10.18.15.51.11
>         for <dr...@ma...>
>         (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
>         Sat, 18 Oct 2014 05:51:11 -0700 (PDT)
> Received-SPF: none (google.com: pa...@ma... does not designate
> permitted sender hosts) client-ip=209.85.212.175;
> Authentication-Results: mx.google.com;
>        spf=neutral (google.com: pa...@ma... does not designate
> permitted sender hosts) smtp.mail=pa...@ma...
> Received: by mail-wi0-f175.google.com with SMTP id d1so4483466wiv.14
>         for <dr...@ma...>; Sat, 18 Oct 2014 05:51:11 -0700 (PDT)
>
> -----Original Message-----
> From: Damien Regad [mailto:dr...@ma...]
> Sent: 18 October 2014 23:23
> To: Man...@li...
> Subject: [mantisbt-dev] 1.2.18 release
>
> Paul,
>
> As you know we have several open security issues including some fairly
> critical ones. I have fixes ready to go for the most recent ones, and to
> close the loop I want to release 1.2.18 as soon as possible.
>
> *I remind you that you owe us a series of security fixes since May*, and you
> agreed earlier this week on IRC [1] to send them to me via e-mail by Friday.
>
> It is now late Saturday (early Sunday actually), and I still haven't
> received anything from you. To be blunt:
>
> YOU ARE BLOCKING A SECURITY RELEASE
>
> This is really unprofressional. Please act responsibly, and put on hold some
> of the trivialities you've been working on for the past few weeks/months for
> the few minutes it will take to send me patches. And please don't give me
> any of that shit again about your SSH access.
>
> Damien
>
> [1]
> http://www.mantisbt.org/irclogs/mantisbt/2014/mantisbt.2014-10-15.log.html
>
>
> ----------------------------------------------------------------------------
> --
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> mantisbt-dev mailing list
> man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> mantisbt-dev mailing list
> man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev



-- 
http://robert.muntea.nu/