Bug 207826 - [UPDATE] audio/teamspeak3-server: to 3.0.12.3
Summary: [UPDATE] audio/teamspeak3-server: to 3.0.12.3
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Kurt Jaeger
URL:
Keywords: easy, patch-ready
Depends on:
Blocks:
 
Reported: 2016-03-09 02:46 UTC by Ultima
Modified: 2016-03-09 21:16 UTC (History)
4 users (show)

See Also:
bugzilla: maintainer-feedback? (hirner)

Attachments
ts3.diff (1.39 KB, patch)
2016-03-09 02:46 UTC, Ultima 		hirner: maintainer-approval+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ultima 2016-03-09 02:46:47 UTC 
Created attachment 167886 [details]
ts3.diff

Simple update patch

* Updated to 3.0.12.3
* Updated distinfo

poudriere bulk -Ct: 102amd64:ok 102i386:ok 93amd64:ok 93i386:ok


tested on amd64 10-STABLE r296377 and is working as expected
Comment 1 hirner 2016-03-09 08:48:16 UTC 
Are you sure no files were added/removed?
Comment 2 Ultima 2016-03-09 11:32:07 UTC 
(In reply to hirner from comment #1)

> Are you sure no files were added/removed?

Poudriere didn't catch any, its usually pretty good that that. From the changelog its just a bugfix release.
Comment 3 commit-hook freebsd_committer freebsd_triage 2016-03-09 21:15:12 UTC 
A commit references this bug:

Author: pi
Date: Wed Mar  9 21:14:56 UTC 2016
New revision: 410727
URL: https://svnweb.freebsd.org/changeset/ports/410727

Log:
  audio/teamspeak3-server: 3.0.12.2 -> 3.0.12.3

  - fixed an other server crashes on malicious input

  PR:		207826
  Submitted by:	Ultima1252@gmail.com
  Approved by:	hirner@bitfire.at (maintainer)

Changes:
  head/audio/teamspeak3-server/Makefile
  head/audio/teamspeak3-server/distinfo
Comment 4 Kurt Jaeger freebsd_committer freebsd_triage 2016-03-09 21:16:36 UTC 
Testbuild OK.

Now, looking at the changelog, this looks like one can interpret it as a security fix. I'm not asking for VUXML entries yet (too lazy), but ... 8-)

Committed, thanks!