Summary: | net-fs/samba-3.0.27 causes PANIC (push_ascii - dest_len == -1) in logfiles and prevents clients from accessing samba shares | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Keller <reg> |
Component: | [OLD] Server | Assignee: | Gentoo's SAMBA Team <samba> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | akshayushah, alienpenguin, tec-9 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 197519 |
Description
Thomas Keller
2007-11-17 15:56:38 UTC
Can I add a +1 to this bug. Using the CIFS filesystem instead of the SMBFS filesystem module works on version 3.0.27, however, since the mount options aren't exactly the same, my preference is to use the previous version. Tested as broken on AMD64 client, AMD K7 server, both at gentoo-sources 2.6.22-r9. Hi, I'm having the same problem with my Linux clients. Windows clients work without problems. Mounting the share with mount -t smbfs -o username=nobody //server/share /mnt/myserver works fine. The first "ls /mnt/myserver" however crashes the server and produces a core dump. Ok, samba-3.0.27 has been masked now, please downgrade to samba-3.0.26-r2 which fixes the remote vulnerability until upstream fixes the issue. Sorry. Upstream-Bug: https://bugzilla.samba.org/show_bug.cgi?id=5087 For those interested in helping upstream: there's a fix. We'll wait with releasing a revision bump until the fix gets confirmed. Finally fixed with version 3.0.27a. Users who use an unstable profile can directly update. Users with stable profiles have to either downgrade to 3.0.26a-r2 or wait for 3.0.27a to become stable (won't take long). Cheers. |