N7x@infosec.pub to appsec@infosec.pubEnglish · 1 year agoXML Security in Javasemgrep.devexternal-linkmessage-square4fedilinkarrow-up12arrow-down10
arrow-up12arrow-down1external-linkXML Security in Javasemgrep.devN7x@infosec.pub to appsec@infosec.pubEnglish · 1 year agomessage-square4fedilink
minus-squareN7x@infosec.pubOPlinkfedilinkEnglisharrow-up1·1 year agoHistorical decisions seem to be the most common reasons
minus-squarehimazawa@infosec.publinkfedilinkEnglisharrow-up0·1 year agoYes, but usually “historical decisions” is an acronym for “we are not able to manage that because we designed our systems in the worst possible way”
minus-squareZeno_of_Citium@infosec.publinkfedilinkEnglisharrow-up2·1 year ago… and those decisions are sometimes rooted in “we don’t have the people and/or money to spend on a new development in this module.” And everyone else is stuck either accepting that or spending the resources to ameliorate the situation. :/
Historical decisions seem to be the most common reasons
Yes, but usually “historical decisions” is an acronym for “we are not able to manage that because we designed our systems in the worst possible way”
… and those decisions are sometimes rooted in “we don’t have the people and/or money to spend on a new development in this module.”
And everyone else is stuck either accepting that or spending the resources to ameliorate the situation. :/