Reply to thread

Message

<blockquote data-quote="JimCatMP" data-source="post: 972224" data-attributes="member: 103549">Everyone contributing to this thread knows EXACTLY what it means to give root access in DB terms.&nbsp;You don't seem to understand the most basic of security principals - security has NO inherent value, it's the ASSET your are protecting that has value and as such sets the benchmark for the security investment (time, effort, code, hardware....&nbsp;&nbsp; do you rate your DB's as important enough to invest in two factor authentication for admin access - yes/no - doesn't matter which as long as your investment matches your risk profile).&nbsp;My TV Server is a TV Server - one function, it matters not that the DB corrupted due to root access or disk failure due to cat having a crafty crap behind the sofa and blocking fan&nbsp; - the same function is compromised, it's only the clean up that's different.&nbsp;You are NOT the sort of person MePo is aimed at, it's target audience is generally computer literate, single or limited function devices NOT core DB servers supporting several projects in real project space - that not that you can't use or can't contribute, you surely could, but your base argument simply does not indicate any willingness to do either. &nbsp;&nbsp;Given the above was your starting point, you've already lost the case where you plead &nbsp;&nbsp;If your intention was to be constructive, would it not have been better not to label MePo dev as lazy Malware artists, make the point that in a multi-service environment the default IS a risk [and a risk by error NOT malign intent] and if you had the level of interest, recommendation on safer path or leave it at that, DavidF provided base info for anyone with the likely skill level on how to progress.&nbsp;JCMP</blockquote>

[QUOTE="JimCatMP, post: 972224, member: 103549"] Everyone contributing to this thread knows EXACTLY what it means to give root access in DB terms. You don't seem to understand the most basic of security principals - security has NO inherent value, it's the ASSET your are protecting that has value and as such sets the benchmark for the security investment (time, effort, code, hardware.... do you rate your DB's as important enough to invest in two factor authentication for admin access - yes/no - doesn't matter which as long as your investment matches your risk profile). My TV Server is a TV Server - one function, it matters not that the DB corrupted due to root access or disk failure due to cat having a crafty crap behind the sofa and blocking fan - the same function is compromised, it's only the clean up that's different. You are NOT the sort of person MePo is aimed at, it's target audience is generally computer literate, single or limited function devices NOT core DB servers supporting several projects in real project space - that not that you can't use or can't contribute, you surely could, but your base argument simply does not indicate any willingness to do either. Given the above was your starting point, you've already lost the case where you plead If your intention was to be constructive, would it not have been better not to label MePo dev as lazy Malware artists, make the point that in a multi-service environment the default IS a risk [and a risk by error NOT malign intent] and if you had the level of interest, recommendation on safer path or leave it at that, DavidF provided base info for anyone with the likely skill level on how to progress. JCMP [/QUOTE]

Verification