https://bugs.launchpad.net/ubuntu/+source/tcsh/+bug/1213743/comments/1
contains an explanation on why this is not a bug. Stop bothering people.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206370
Sorry, the issue is not related to unlimited local resource overutilization.
$ (yes )
is not a fork bomb or any other kind of resource overutilization. There is only
one subshell and only one subprocess being executed in it.
The issue is with buggy signal handling.
I'm re-opening this BR.
--
Since you've apparently locked down this report, so I can't re-open it,
I'm opening a new one.
This is the third time you've brushed away a security-related bug report
on completely spurious grounds. You're making more work for yourself and
for users of launchpad. Please stop doing that. It is
Thanks for taking the time to report this bug and helping to make Ubuntu
better. This is not a bug, but rather expected behavior:
https://wiki.ubuntu.com/SecurityTeam/Policies#Unlimited_Local_Resource_Utilization
Please feel free to report any other bugs you may find.
** Information type
** Also affects: ksh (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1206370
Title:
subshell that instantly locks up bash, dash, ksh, tcsh, and
