similar to: userv - how to make cron (et al) not setuid

Many of the security problems we''ve had to deal with recently have been where one program invokes another when no good level of trust exists between them. Currently solutions to this requirement are produced on an ad-hoc basis, usually involving set-id programs (often setuid root), superuser daemons calling user programs for `upcalls'', or both. There are problems with this

Hello, I just made available a beta version of a port scan detector that I''ve been working on. The program, called Abacus Sentry, is a port scan/probe detector that offers what I think are a number of unique and useful features: - Runs on TCP or UDP sockets. Configurable by the user to bind to multiples of sockets for increased detection coverage. - Adjustable scan detection value with

Hans van Kranenburg writes ("[PATCH 06/13] sysconfig.xencommons.in: Strip and debianize"): > Strip all options that are for stuff we don't ship, which is 1) > xenstored as stubdom and 2) xenbackendd, which seems to be dead code > anyway. [1] > > It seems useful to give the user the option to revert to xenstored > instead of the default oxenstored if they really

I rather like agedu It probably does what you want. But as Mohammad says you do have to traverse your filesystem. https://www.chiark.greenend.org.uk/~sgtatham/agedu/ agedu: track down wasted disk space - chiark home page<https://www.chiark.greenend.org.uk/~sgtatham/agedu/> www.chiark.greenend.org.uk agedu. a Unix utility for tracking down wasted disk space Introduction. Suppose

Hi Alex, John Thanks for confirming my suspicion that there is no getting away from POSIX tree traversal . I was aware of age-du but not robinhood. Cheers Kashif On Wed, May 2, 2018 at 8:57 AM, JOHE (John Hearns) <JOHE at novozymes.com> wrote: > I rather like agedu It probably does what you want. > > But as Mohammad says you do have to traverse your filesystem. > >

Hi. I was wanting an initial opinion from the Release Team, about the Xen packages. Currently they are in bad shape in stretch and I intend to fix them ASAP. The question is whether I should move to Xen 4.7, or Xen 4.8. Xen 4.8 is currently at RC2 and seems in pretty good shape. I think it's more probable than not that we'll have Xen 4.8.0 by the Debian freeze date, but this is by no

Hans van Kranenburg writes ("[PATCH 09/13] xen init script: move init_dom0 into xenstored start"): > This little xen-init-dom0 program is present in both our 4.8 and 4.11 > packages, so there's no need to keep the if else code. Also, it only > makes sense to run it after starting xenstored, and not all other times > start is called. I think xen-init-dom0 is not in jessie

I am going to submit a proposal for a Xen BOF at DC18. Here is my first cut at a draft abstract: Title: Xen in Debian BoF Format: workshop with 25 min slot The Xen packages in Debian are in need of some work, including some tidying up, upstreaming of some Makefile patches, and updating to new versions. There is a large outstanding bug list. Also with the demise of Alioth and the

Elliott Mitchell writes ("[PATCH 12/12] Partially revert "Cross-compilation fixes.""): > This partially reverts commit 16504669c5cbb8b195d20412aadc838da5c428f7. Wow, that is an upsteam commit from 2005. However, I would like some kind of explanation. Is it in fact now false that | # These don't cross-compile ? Should this patch go upstream ? Ian. -- Ian Jackson

Control: retitle -1 max grant frames problem (domu freeze with linux-image-4.9.0-4-amd64) Control: severity -1 important Control: reassign -1 src:xen 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9 Just gardening here. (i) Bug title should mention grant frames. (ii) This does not affect all use cases and is not, IMO, RC. Although we should certainly see if we can improve it. (iii) Britney is confused

(*Really* switching to my personal address not because I'm not doing work for Citrix, but because the corporate email is not working properly. Sigh. Also, email updated a bit.) Ian Jackson writes ("Re: Updated Xen packages for XSA 216..225"): > Ian Jackson writes ("Re: Updated Xen packages for XSA 216..225"): > > Hi. I was away and am now back. There are a lot

branch xen-unstable xen branch xen-unstable job test-amd64-amd64-xl-pcipt-intel test debian-fixup Tree: linux git://xenbits.xen.org/linux-pvops.git Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git Tree: xen http://xenbits.xen.org/staging/xen-unstable.hg *** Found and reproduced problem changeset *** Bug is in

Processing commands for control at bugs.debian.org: > user debian-qa at lists.debian.org Setting user to debian-qa at lists.debian.org (was anbe at debian.org). > affects 774889 + xfswitch-plugin Bug #774889 [gdm3] gdm3: fails to upgrade squeeze -> wheezy -> jessie - trying to overwrite /usr/share/gdm/BuiltInSessions/default.desktop Added indication that 774889 affects xfswitch-plugin

hey centos long time no hear! :) I'm having a small issue where the backup jobs that I set to run in the crontab of the backup user do not appear to be running. Here's how I set it up (with crontab -e as the backup user): run amanda every night (check at 2:45 and backup at 3) 45 2 * * * /usr/sbin/amcheck /var/log/amanda/crontab/amcheck.log * 3 * * * /usr/sbin/amdump

flight 12922 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12922/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-amd 9 guest-start.2 fail REGR. vs. 12892 Regressions which are regarded as allowable (not blocking): test-amd64-i386-qemuu-rhel6hvm-intel 9

flight 14649 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/14649/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-pvops 2 host-install(2) broken REGR. vs. 14472 build-i386-pvops 2 host-install(2) broken REGR. vs. 14472

flight 17968 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17968/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop

flight 6999 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/6999/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-win 16 leak-check/check fail never pass test-amd64-amd64-xl-win 13 guest-stop fail

flight 13776 linux-mingo-tip-master real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13776/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xend-winxpsp3 5 xen-boot fail REGR. vs. 12678 test-amd64-i386-xl-credit2 5 xen-boot fail REGR. vs. 12678 test-amd64-amd64-pair 8

flight 7124 linux real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/7124/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-pair 16 guest-start fail REGR. vs. 7062 test-amd64-i386-pv 9 guest-start fail REGR. vs. 7062 test-amd64-i386-xl-credit2 9 guest-start fail REGR. vs. 7062