On Thu, Jan 11, 2007 at 02:42:48PM +0900, Ken'ichi Ohmichi wrote:
>
> Hi Neil,
>
> 2007/01/10 09:31:29 -0500, Neil Horman <[EMAIL PROTECTED]> wrote:
> >This all seems great to me, although at this point it needs to wait until
> >RHEL5.1 for us to integrate it. Not that it changes much, but I would
> >recommend
> >that you make the initramfs command look like this
> >makedumpfile -S -cd31 -i /tmp/makedumpfile.config /proc/vmcore | ssh [EMAIL
> >PROTECTED] "cat | makedumpfile -R dumpfile"
> >That way no temporary file is ever seen by anyone, and the resultant file
> >stored on the target is in an
> >appropriate format.
>
> My idea is the same as yours.
> But there is one problem. On RHEL5.0-beta2, a normal user (no root)
> cannot run makedumpfile directly due to no path of /sbin/makedumpfile.
What? Why can't a non-root user run makedumpfile? I assume this is some sort
of selinux targeted policy? I would think the fast answer would be to update
the policy and submit it for inclusion. I can't see any rason why letting any
user run makedumpfile would be a risk
> It is not secure to require a root login of a remote host to transport
> a dumpfile. It is necessary to change makedumpfile directory, or run
> /sbin/makedumpfile on a remote host:
>
> # makedumpfile -S -cd31 -i /tmp/makedumpfile.config /proc/vmcore | ssh [EMAIL
> PROTECTED] "/sbin/makedumpfile -R dumpfile"
>
> Thanks
> Ken'ichi Ohmichi
> _______________________________________________
> fastboot mailing list
> [email protected]
> https://lists.osdl.org/mailman/listinfo/fastboot
_______________________________________________
fastboot mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/fastboot
