Oh, yes, actually. You're absolutely right. This was sent over to me this morning as a 'new threat' to deal with, and as such I treated it as news. I hadn't spotted the publication date, in my haste to share it! Oops! Thanks - I'm hopeful that, if all else, this post serves as a useful reminder to patch up!
Ah, a fellow Glasgow-er! Wasn't sure how many I'd bump into on here! :)
We Glaswegians get everywhere it seems ;-) One day the internet will realise what we're like and ban us ;-)
At the moment we're in the process of going from 'docker for qa' to 'docker for production' so your post caught my eye - I was all ready to sigh and start patching - then the cve number caught my eye and thought 'oh, that's familiar' ;-)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Is that not the cve that was patched a while back? The publication date is 11th of February?
Hello from Glasgow btw :: waves :: :-)
Oh, yes, actually. You're absolutely right. This was sent over to me this morning as a 'new threat' to deal with, and as such I treated it as news. I hadn't spotted the publication date, in my haste to share it! Oops! Thanks - I'm hopeful that, if all else, this post serves as a useful reminder to patch up!
Ah, a fellow Glasgow-er! Wasn't sure how many I'd bump into on here! :)
We Glaswegians get everywhere it seems ;-) One day the internet will realise what we're like and ban us ;-)
At the moment we're in the process of going from 'docker for qa' to 'docker for production' so your post caught my eye - I was all ready to sigh and start patching - then the cve number caught my eye and thought 'oh, that's familiar' ;-)