I guess, the urgency of the update was reasonable, although I've
received Samba-newsletter around that time only.

But what makes me really disappointed that recently port commiters
took the habbit to intervent into somebody's
else port(s) without even notifying the mantainer.

And in a lot of cases(not this one) without even understanding what
are they changing/breaking.

That whole situation really pisses me off and makes demotivated.

WBR,
Timur Bakeyev.

On Wed, Apr 11, 2012 at 12:33 AM, Xin LI <delp...@freebsd.org> wrote:
> delphij     2012-04-10 22:33:01 UTC
>
>  FreeBSD ports repository
>
>  Modified files:
>    net/samba34          Makefile distinfo
>    net/samba34/files    sernet.patch
>    net/samba35          Makefile distinfo
>    net/samba36          Makefile distinfo
>  Log:
>  Security update to address root credential remote code execution issue
>  (CVE-2012-1182):
>
>   - Update samba36 to 3.6.4;
>   - Update samba35 to 3.5.14;
>   - Update samba34 to 3.4.16;
>
>  All samba users are advised to update.
>
>  Security:       baf37cd2-8351-11e1-894e-00215c6a37bb
>  With hat:       secteam@
>
>  Revision  Changes    Path
>  1.13      +1 -1      ports/net/samba34/Makefile
>  1.6       +2 -2      ports/net/samba34/distinfo
>  1.4       +45 -47    ports/net/samba34/files/sernet.patch
>  1.10      +1 -1      ports/net/samba35/Makefile
>  1.5       +2 -2      ports/net/samba35/distinfo
>  1.5       +1 -1      ports/net/samba36/Makefile
>  1.4       +2 -2      ports/net/samba36/distinfo
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "cvs-all-unsubscr...@freebsd.org"

Reply via email to