On Thu, Apr 16, 1998 at 02:54:45AM -0700, Darren/Torin/Who Ever... wrote:
> Eloy A. Paris, in an immanent manifestation of deity, wrote:
> >an easy one: why when root runs a program that faults core is not
> >dumped but when a normal user runs the same program a core is dumped?
>
> My educated gue
> My educated guess on this is that there could be sensitive data in the
> root core dump. I remember this was true on some unix I've worked on in
That's often true if the program is *setuid* (or setgid) [to anything,
not just root] - most, perhaps all unices will fail to dump core in
that case
-BEGIN PGP SIGNED MESSAGE-
Eloy A. Paris, in an immanent manifestation of deity, wrote:
>an easy one: why when root runs a program that faults core is not
>dumped but when a normal user runs the same program a core is dumped?
My educated guess on this is that there could be sensitive data
On 15 Apr 1998, Eloy A. Paris wrote:
> Nope, ulimit -c also outputs "unlimited". What about the output of "set
> -o", how does yours look like?
allexport off
braceexpand on
errexit off
hashall on
histexpand on
keyword off
monitor on
noclobber o
Hi,
Brandon Mitchell <[EMAIL PROTECTED]> wrote:
: I'd check the ulimit,
Nope, ulimit -c also outputs "unlimited". What about the output of "set
-o", how does yours look like?
Thanks,
E.-
--
Eloy A. Paris
Information Technology Department
Rockwell Automation de Venezuela
Telephone: +58-2-943
On 15 Apr 1998, Eloy A. Paris wrote:
> an easy one: why when root runs a program that faults core is not
> dumped but when a normal user runs the same program a core is dumped?
[EMAIL PROTECTED](p5):cs315# cat core-test.c
void main(void)
{
* (char *) 0 = 0;
}
[EMAIL PROTECTED](p5):cs315#
6 matches
Mail list logo
