stevelitt

RossBoylan said on Sun, 25 Apr 2021 16:37:49 -0700 >Somewhat off topic .... > ***@***.*** Do you think *nix has a good outliner now? I split >between using GrandView in...

https://pastebin.com/iNUYMnnN [root@mydesk dovecot]# cat tombclose.txt tomb [D] Identified caller: root (0:0) tomb [D] Tomb command: close tc.tomb tomb [D] Caller: uid[0], gid[0], tty[/dev/pts/4]. tomb [D] Temporary directory: /tmp/zsh tomb [E]...

Where can I find a tomb mailing list or even better a tomb IRC channel?

Thanks for the info. I never would have thought of just using "tc". Thanks!

Thank you for the tomb close -D, tomb close, tomb close tc (in my example) and the tomb list commands. I managed to close the thing with tomb slam (it...

In the preceding, what I meant to say was not "root", but "current user". Which is just as much of a disaster. The following is a patch to make preserve-ownership...

After a week of working with Tomb, I completely understand Jaromil's comment about real use-cases, and in fact I will be using it without -p for my backups. Not having...

I should mention that years ago I commented out: root ALL=(ALL) ALL A person who has that line intact in their /etc/sudoers would not need all the lines for what...

I have two ideas that might possibly work. One is to suid root the tomb executable. Ugly, not all that secure, but I think it would work. The second way...

Arbitrary code execution must be guarded against. First, the daemon must sanitize its input. Second, both the daemon and tomb must demand an identifier from each other, and modify that...