Vulneratbility - Slackware can be compromised - all versions affected
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I suggested twice to the OP to email Patrick Volkerding if he wants that what he considers to be an issue be assessed. I don't know if he did, anyway I wouldn't mind that this thread be closed.
Before closing I would like to hear from either OP, Pat or "chief maintainers" *) whether or not we do indeed have an unsolved problem.... creating a thread like this without proper closure is just evil.
Before closing I would like to hear from either OP, Pat or "chief maintainers" *) whether or not we do indeed have an unsolved problem.... creating a thread like this without proper closure is just evil.
Contact has been made and a dialogue is in progress.
Thank you.
Though it could have saved some posts in this thread, if that was post #2.
@OP: thanks for your work. Looking forward to hear the full story later, but if anyone should stumble upon vulnerabilities in the future, this most certainly is not the way to report it...
Though it could have saved some posts in this thread, if that was post #2.
It would have helped if crts would have contacted Pat instead of posting here first with all the drama. Then perhaps this whole thread would have not happened.
It would have helped if crts would have contacted Pat instead of posting here first with all the drama. Then perhaps this whole thread would have not happened.
But, at least, it is a valid issue report (no matter how less critical it's) or it's just a false alarm?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.