Stack trace:
#0 0x7f70f7618227 in __GI_raise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:55
#1 0x7f70f7619e8a in __GI_abort () at abort.c:89
#2 0x7f70f79bc48f in isc_assertion_failed (
file=file@entry=0x7f70f7a06350 "../../../../lib/isc/unix/socket.c",
Debdiff for Xenial.
** Description changed:
- The fix for bug #11395 / CVE-2015-5252
+ [Impact]
+
+ * User is denied access when trying to access a share "/"
+
+ [Test Case]
+
+ * Setup a Samba server
+
+ * Add a share with path "/"
+
+ * Try to access the share
+
+ [Regression
SRU proposal for Wily.
** Patch added: "wily_samba_4.1.17+dfsg-4ubuntu3.2.debdiff"
https://bugs.launchpad.net/samba/+bug/1545750/+attachment/4572181/+files/wily_samba_4.1.17+dfsg-4ubuntu3.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
SRU proposal for Precise.
** Patch added: "precise_samba_3.6.3-2ubuntu2.14.debdiff"
https://bugs.launchpad.net/samba/+bug/1545750/+attachment/4572183/+files/precise_samba_3.6.3-2ubuntu2.14.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
SRU proposal for Trusty.
** Patch added: "trusty_samba_4.1.6+dfsg-1ubuntu3.14.04.11.debdiff"
https://bugs.launchpad.net/samba/+bug/1545750/+attachment/4572182/+files/trusty_samba_4.1.6+dfsg-1ubuntu3.14.04.11.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1545750
Title:
Access denied if the share path is "/"
To manage notifications about this bug go to:
Public bug reported:
The fix for bug #11395 / CVE-2015-5252
https://git.samba.org/?p=samba.git;a=commitdiff;h=7606c0db257b3f9d84da5b2bf5fbb4034cc8d77d
locked down the path checks in check_reduced_name[_with_privilege]() to prevent
unintended access via wide links.
The new checks do not
I have backported the fix to trusty in my ppa.
Unfortunately I was not able to reproduce this issue (although my tests
are ongoing). With that being said I would really appreciate anyone that
is affected by this issue to give it a try and let me know whether the
backport fixed that for them.
The
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
To manage notifications about this bug go to:
