-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The last release (4.8.1) was back in January. Things have been pretty quiet but we've had a few bugs fixed since then, so it's probably time for another release. Not a lot of major changes with this one -- mostly just bugfixes. The main changes since 4.8.1 are: * Some distros (namely Fedora) are moving to having /etc/mtab be a symlink to /proc/mounts. We automatically skip trying to alter the mtab if it's a symlink. * fix for a bug that could prevent root from mounting onto a directory to which he did not have explicit execute permission. * fix for a bug that caused the mount helper to pass in a corrupt address when someone specified an IPv6 address with a scopeid. * mount.cifs bugfix for an uninitialized variable that could cause a segfault webpage: http://linux-cifs.samba.org/cifs-utils/ tarball: ftp://ftp.samba.org/pub/linux-cifs/cifs-utils/ git: git://git.samba.org/cifs-utils.git gitweb: http://git.samba.org/?p=cifs-utils.git;a=summary Detailed changelog: commit 51e3999b5fcd76502e05325174f34e0428c4742e Author: Jeff Layton <jlayton@xxxxxxxxx> Date: Mon Jan 31 11:54:44 2011 -0500 autoconf: bump release to 4.8.2 for interim builds Signed-off-by: Jeff Layton <jlayton@xxxxxxxxx> commit fba28cfe2f13dd8bdae3cec76178f42b001a40ca Author: Jeff Layton <jlayton@xxxxxxxxx> Date: Mon Jan 31 15:04:35 2011 -0500 mount.cifs: don't try to alter mtab if it's a symlink Some distros replace /etc/mtab with a symlink to /proc/mounts. In that situation, mount.cifs will hang for a while trying to lock the mtab. /bin/mount checks to see if the mtab is a symlink. If it is or if a stat() call on it fails, it doesn't try to to update the mtab. Have mount.cifs do the same. Signed-off-by: Jeff Layton <jlayton@xxxxxxxxx> commit 24093bef78e1e4ea5d541716ebba63e8d4e15c58 Author: Jeff Layton <jlayton@xxxxxxxxx> Date: Tue Feb 1 14:24:30 2011 -0500 mount.cifs: fix possible use of uninitialized variable It's possible to "goto return_i" in this function at several points before line_buf is set. At that point, the NULL pointer check won't work correctly and we can end up with a SIGSEGV. Signed-off-by: Jeff Layton <jlayton@xxxxxxxxx> commit b6d2d91df012f965f29ba26489aca009712a230c Author: Jeff Layton <jlayton@xxxxxxxxx> Date: Tue Feb 8 15:33:09 2011 -0500 mount.cifs: reacquire CAP_DAC_READ_SEARCH before calling mount(2) It's possible that the user is trying to mount onto a directory to which he doesn't have execute perms. If that's the case then the mount will currently fail. Fix this by reenabling CAP_DAC_READ_SEARCH before calling mount(2). That will ensure that the kernel's permissions check for this is bypassed. Reported-by: Erik Logtenberg <erik@xxxxxxxxxxxxx> Signed-off-by: Jeff Layton <jlayton@xxxxxxxxx> Reviewed-by: Steve French <sfrench@xxxxxxxxxx> commit 38eaab88a08a66adb535d0e5cdcaea9859131c5b Author: Jeff Layton <jlayton@xxxxxxxxx> Date: Tue Feb 15 13:30:47 2011 -0500 mount.cifs: fix handling of scopeid in resolve_host We get a pointer to the end of the address string (ipaddr), but the call snprintf and pass in tmpbuf which is a pointer to the beginning of the address string. If someone passes in an address with a scopeid then we end up overwriting the entire address string. Reported-by: Björn JACKE <bj@xxxxxxxxx> Signed-off-by: Jeff Layton <jlayton@xxxxxxxxx> commit cf7d6d481a84fdfc8272e38a6eb49c8a52fa201f Author: Jeff Layton <jlayton@xxxxxxxxx> Date: Fri Mar 4 14:54:18 2011 -0500 autoconf: bump release to 4.9 Signed-off-by: Jeff Layton <jlayton@xxxxxxxxx> - -- Jeff Layton <jlayton@xxxxxxxxx> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk1xSmcACgkQyP0gxQMdzIBRfwCeOuyPL9QXOAbxHJdt+KIZ+jzR fkMAn1/lD47v9CwYsOZ+GLilIfpcgJ8q =RlVa -----END PGP SIGNATURE----- ÿôèº{.nÇ+?·?®??+%?Ëÿ±éݶ¥?wÿº{.nÇ+?·¥?{±ýÈ?³ø§¶?¡Ü¨}©?²Æ zÚ&j:+v?¨þø ¯ù ®w¥þ?à2?Þ?¨èÚ&¢)ß¡«a¶Úÿÿûàz¿äz¹Þ?ú+?ù???Ý¢jÿ?wèþf
