[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian LTS Security update of ruby-mail



Hi

Thanks. I'm sending this mail to debian-lts mail list too. I sent to wrong list last time.

Best regards,

// Ola

On Thu, May 19, 2016 at 2:18 PM, Antonio Terceiro <terceiro@debian.org> wrote:
On Thu, May 19, 2016 at 12:59:46PM +0200, Ola Lundqvist wrote:
> Hi ruby-mail maintainers and Debian LTS team
>
> This is my first contribution to Debian LTS so it would be good if someone
> review the change. I'm doing this as a training excercise and this is why
> the maintainer have not been asked to this for me.
>
> I have prepared an update of the ruby-mail package to correct the problem
> described in
> https://security-tracker.debian.org/tracker/TEMP-0000000-8B2928
>
> The prepared package is here:
> http://apt.inguza.net/wheezy-security/ruby-mail
> The debdiff is here:
> http://apt.inguza.net/wheezy-security/ruby-mail/diff-against-previous-version-in-wheezy.patch
> You can see the test.rb file that I wrote to test the update too.
>
> It actually looks like the problem was solved in SMTP::Net so this update
> may not be needed, but on the other hand I just did a very small test so
> I guess the security correction will not hurt either.
>
> The correction is a backport of the patch found here:
> https://github.com/mikel/mail/commit/72befdc4dab3e6e288ce226a7da2aa474cf5be83
>
> I have tested that the described problem is corrected and I have tested
> that it is possible to send an email successfully.
>
> I will upload the correction in four days unless someone objects.

looks ok to me. thanks for taking care of it.



--
 --------------------- Ola Lundqvist ---------------------------
/  opal@debian.org                     Folkebogatan 26          \
|  ola@inguza.com                      654 68 KARLSTAD          |
|  http://inguza.com/                  +46 (0)70-332 1551       |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---------------------------------------------------------------


Reply to: