Imagemagic drupal11/11/2023 And that's fine, some places consider separate processes with different rights good enough security boundaries. What seems more likely is they don't consider containers alone a _good enough_ security boundary. If the security folks at your job truly doesn't consider containers security boundaries then they are wrong. At this point I'm doing following citations but you get the point. The Netflix link also explicitly says containers are a security boundary multiple times and they use additional protections to strengthen that boundary. The Red Hat link doesn't say anything about security boundaries whatsoever but it does say containers aren't perfect protection yet they do provide some protection. Its link and quote from Google say it's not a _strong_ security boundary yet the article claims Google said it wasn't a security boundary at all. Its link to Microsoft's definition of a security boundary explicitly includes containers as a security boundary twice in the tables and offers bounties if you can break out of that security boundary. The article's sources disagree with the article. To be very clear, and to hopefully prevent this continued necro'ing of this post, I was not, talking about this history of image processing, but the specific linux namespace that imagemagick has, and why it has it.Īny other points of debate about this are irrelevant. I'm not sure how you are either not getting that clarifier of "on linux" and seem to be trying to debate something about the history of image processing itself? and being that it was the first mature image processor added to the distro, it is why it has the namespaces it does. When imagemagick was added to linux in the mid 90s (near ImageMagick 4) not a lot of people were doing image processing in the OS. > and was doing image processing on linux before most had considered it. This next part, is the part that seemingly needs clarification > Image magick has been around for a pretty long time Surely we can both agree part below is a fair and accurate statement > Image magick has been around for a pretty long time, and was doing image processing on linux before most had considered it. I don't have any idea why you are going in these seeming random directions, I'm not promoting linux, or whatever else your going on about. It is at relevant, because this is about why imageMagick has such prime namespace on linux. > claiming early Linux image processing with ImageMagick is irrelevant Chevy's are great and all, but there are other things. I'm reading it similarly to saying your Chevy wipers were wiping your windshield before most had considered it when modern wipers were invented 50 years ago and all the techniques for doing so were worked out around the turn of the century. So assuming your Yggdrasil installation was processing images with it in early 1993, that it was "before most had considered it" is hardly knowable. What much does alleged Linux inclusion of any application (/usr/local/*) whatsoever have to do with that application? You're apparently promoting Linux by claiming it's a feat few had considered, or otherwise saying "I am cool," which is fine I guess and I don't doubt it, but also irrelevant.Īs I pointed out, ImageMagick was developed in 1987, and I should have gone on to specify that most digital image manipulation techniques were developed in the 1960's. To be quite clear, in the context of ImageMagick, claiming early Linux image processing with ImageMagick is irrelevant, also, not exactly true. Im really not sure what you are getting at?
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |