public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: gshan <gshan@alcatel-lucent.com>
To: Bernd Eckenfels <ecki@lina.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: do_coredump and O_NOFOLLOW
Date: Wed, 15 Aug 2007 16:03:39 +0800	[thread overview]
Message-ID: <46C2B35B.5080709@alcatel-lucent.com> (raw)
In-Reply-To: <E1ILCwJ-0003th-00@calista.eckenfels.net>

Bernd Eckenfels wrote:
> In article <46C290F6.2090309@alcatel-lucent.com> you wrote:
>   
>> I found that O_NOFOLLOW is used for opened core file in Linux 2.6.10. 
>>     
>
> I think that is for security reasons, otherwise one has to (atomically)
> check who is the owner of the symlink and where it points to. If you dont
> have hostile users on your system you might be able to remove it, but it is
> not a good idea in the general public.
>
> Maybe we need a coreadm tool like Solaris has, where you can put the
> corefiles where you want. That would change the corepattern to include a
> path and be specific to a process (tree).
>
> Gruss
> Bernd
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>   
Bernd, Thanks for your reply. I don't think there are any hostile users 
on the system. So it's relatively of security. I didn't hear of coreadm 
tool before, Linux will become more powerful with coreadm.

  reply	other threads:[~2007-08-15  8:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15  5:36 do_coredump and O_NOFOLLOW gshan
2007-08-15  7:05 ` Bernd Eckenfels
2007-08-15  8:03   ` gshan [this message]
2007-08-15 15:12     ` Valdis.Kletnieks
2007-08-15 23:41 ` Andy Isaacson

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=46C2B35B.5080709@alcatel-lucent.com \
    --to=gshan@alcatel-lucent.com \
    --cc=ecki@lina.inka.de \
    --cc=linux-kernel@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