The one good reason to not put 3.1.0.1 in hardy is that hardy is released and
frozen, and doesn't accept new upstream releases (there are exceptions, but
this one wouldn't be a good candidate anyway).
If the security issue concerns you, please open a separate bug report, and
someone (you?) may b
Filezilla release 3.1.0.1 should also be available in hardy as well, since it's
a LTS (and people will be using it a long time) and this is a security advisory!
Therefor I have set the status back to Confirmed. If there is (are) good
argument(s) to not update the hardy-version then you can set it
This bug was fixed in the package filezilla - 3.1.0.1-0ubuntu1
---
filezilla (3.1.0.1-0ubuntu1) intrepid; urgency=low
* New upstream release (LP: #251950), new features since 3.0.11.1 include:
- IPv6 support
- SOCKS5 and HTTP/1.1 proxy support
* debian/control: updated p
I'll update the package in intrepid. FYI I will also do what is necessary to
prepare an eventual sync of the package with Debian.
After talking with upstream about the security issue, the issue is that an
attacker could make a transfer fail (sending some special packets) and
filezilla wouldn't n
** Changed in: filezilla (Ubuntu)
Assignee: (unassigned) => Adrien Cunin (adri2000)
Status: New => Confirmed
--
Please update filezilla to 3.1.0.1
https://bugs.launchpad.net/bugs/251950
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subsc
** Visibility changed to: Public
--
Please update filezilla to 3.1.0.1
https://bugs.launchpad.net/bugs/251950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
