BTW, I marked this as a security vulnerability not because of any need for
privacy, but because the consequence (in many environments) is that simply
creating a symlink enables a DOS attack.
On Thu, Dec 2, 2010 at 7:34 AM, Jamie Strandboge <email address hidden> wrote:
> ** This bug is no longer flagged as a security vulnerability
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/683938
>
> Title:
> kernel crash on symlink chased from NFS to failing automount
>
> Status in Ubuntu:
> New
>
> Bug description:
> Create an automount indirect map entry to a nfs server that will deny the
> mount with a permission denied error.
> Create a symlink on some mounted NFS partition pointing at the name of that
> automount indirect map entry.
> Chase the symlink with ls, etc.
> Notice that the automounter tries and fails to mount the partition.
> (visible with automount -d -f, say)
>
> In a few minutes, depending on system activity, the kernel will crash with
> the symptoms of a memory corruption error.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+bug/683938/+subscribe
>
BTW, I marked this as a security vulnerability not because of any need for
privacy, but because the consequence (in many environments) is that simply
creating a symlink enables a DOS attack.
On Thu, Dec 2, 2010 at 7:34 AM, Jamie Strandboge <email address hidden> wrote:
> ** This bug is no longer flagged as a security vulnerability /bugs.launchpad .net/bugs/ 683938 /bugs.launchpad .net/ubuntu/ +bug/683938/ +subscribe
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https:/
>
> Title:
> kernel crash on symlink chased from NFS to failing automount
>
> Status in Ubuntu:
> New
>
> Bug description:
> Create an automount indirect map entry to a nfs server that will deny the
> mount with a permission denied error.
> Create a symlink on some mounted NFS partition pointing at the name of that
> automount indirect map entry.
> Chase the symlink with ls, etc.
> Notice that the automounter tries and fails to mount the partition.
> (visible with automount -d -f, say)
>
> In a few minutes, depending on system activity, the kernel will crash with
> the symptoms of a memory corruption error.
>
> To unsubscribe from this bug, go to:
> https:/
>