From: Fumitoshi UKAI <ukai@debian.or.jp>
To: linux-hotplug@vger.kernel.org
Subject: Re: Forward: Bug#138975: hotplug: /tmp symlink vulnerability
Date: Tue, 19 Mar 2002 16:51:55 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101655694500823@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101650225509574@msgid-missing>
At Mon, 18 Mar 2002 17:51:17 -0800,
David Brownell wrote:
> Looks right to me, except that some other agent
> scripts had the same general need for writable /tmp
> so maybe a more generic fix, done once, would be]
> a better way to go.
I committed this patch.
But I can't find any reason why this check is in ieee1394.agent only.
Which part of ieee1394.agent requires /tmp is writable?
Doesn't other agent need to check as well?
Regards,
Fumitoshi UKAI
> ----- Original Message -----
> From: "Fumitoshi UKAI" <ukai@debian.or.jp>
> To: <linux-hotplug-devel@lists.sourceforge.net>
> Sent: Monday, March 18, 2002 5:39 PM
> Subject: Forward: Bug#138975: hotplug: /tmp symlink vulnerability
>
>
> > Hi,
> >
> > I received the following bug report.
> > It actually create any files on tye system by dangling symlinking
> > in /tmp/test.<number> (touch follows symlinks).
> >
> > Anyway as report said, I think it's better to touch /tmp itself
> > instead of touch /tmp/test.$$ and remove it.
> > If directory is writable, touch the directory will be success, otherwise
> > touch will be failed.
> >
> > How about this ?
> >
> > Index: etc/hotplug/ieee1394.agent
> > =================================> > RCS file: /cvsroot/linux-hotplug/admin/etc/hotplug/ieee1394.agent,v
> > retrieving revision 1.3
> > diff -u -u -r1.3 ieee1394.agent
> > --- etc/hotplug/ieee1394.agent 4 Jan 2002 18:39:49 -0000 1.3
> > +++ etc/hotplug/ieee1394.agent 19 Mar 2002 01:36:56 -0000
> > @@ -33,9 +33,9 @@
> >
> > # if called too early in booting, things break
> > # (bash creates tempfiles)
> > -if touch /tmp/test.$$ >/dev/null 2>&1
> > +if touch /tmp >/dev/null 2>&1
> > then
> > - rm -f /tmp/test.$$
> > + : ok
> > else
> > mesg Need writable /tmp ...
> > exit 1
> >
> > Regards,
> > Fumitoshi UKAI
> >
> >
>
>
> _______________________________________________
> Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
> Linux-hotplug-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
>
>
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2002-03-19 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-19 1:39 Forward: Bug#138975: hotplug: /tmp symlink vulnerability Fumitoshi UKAI
2002-03-19 1:51 ` David Brownell
2002-03-19 16:51 ` Fumitoshi UKAI [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-101655694500823@msgid-missing \
--to=ukai@debian.or.jp \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).