…This is a strange answer and on its face seems quite wrong. Bugs in Perl could be serious problems regardless of privileges unless one takes the most pedantic and unlikely view where a DB security hole isn’t a problem since no user has permission to update the DB. Even then, there have been bugs now and then that allow trivial DoS and such. Having a site like Amazon.com down for 1 minute is millions of dollars. That is a huge problem.
| [reply] |
Yes, I suppose I shouldn't have assumed you would read the rest of the thread for context. If you are going to give someone shell access, there are a million ways they could DoS you, so don't give people shell accounts on an important server. But that doesn't have anything to do with perl bugs.
Not entirely sure where you're going with the DB thing. If you have a Perl program that mediates access to a database that's not accessible any other way, then yes, a perl bug could compromise your database. But in that situation, the program has "elevated privileges" in a sense, even if that isn't implemented with OS-level permissions.
| [reply] |
| [reply] |
Ah, well, you did show me wrong on one thing. I thought I was replying to sundialsvc4 posting anonymously. The hand-wavy, half-right schtick is strictly Trªdϵmårkéd®, you know.
| [reply] |
