![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1205094 http://bugzilla.opensuse.org/show_bug.cgi?id=1205094#c13 Milachew <milachew@mail.lv> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #13 from Milachew <milachew@mail.lv> --- (In reply to William Brown from comment #11)
I did not make the change. I highlighted that the default targetpw mode in SUSE and OpenSUSE in insecure and involved the needed parties.
Please be careful when you make accusations like this, especially when they are incorrect.
Yes, you're right. I took a closer look at the changes on build.opensuse.org and I realized that I was wrong. You are not directly involved in what happened to the sudo package in TW. I apologize for finding you to blame for this.
As a result, my input to Jason would be that:
* We revert the change. * We attempt to understand why this error was missed in AutoQA and how that impacted the a new install. * That the Yast2 team is involved in the next time we attempt this update.
I am glad that this particular change is really recognized as a mistake. I hope that the necessary changes will be made in openQA to prevent such things as soon as possible. By the way, rolling back the changes has already been proposed : https://build.opensuse.org/request/show/1033735 I will share your answer to dispel the opinion that such changes are normal in this way. Also, I will mark this bug report "IN_PROGRESS" mark and close it as soon as the sudo behavior is fixed to working. If you think this is a duplicate of the original bug report, let me know or mark it. Thank you for your reply! -- You are receiving this mail because: You are on the CC list for the bug.