Timeline for Unexplainable behavior of SQL Server under Windows Authentication
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 27, 2017 at 15:16 | history | tweeted | twitter.com/StackDBAs/status/946037119583244288 | ||
| Jul 11, 2017 at 13:28 | history | edited | sepupic | CC BY-SA 3.0 |
I updated the question with another one reguarding impersonating of non-existing login
|
| Jul 11, 2017 at 13:20 | history | edited | sepupic | CC BY-SA 3.0 |
I updated the question with another one reguarding impersonating of non-existing login
|
| Jul 11, 2017 at 9:35 | comment | added | sepupic | But it can be used to give a "hidden" access to the server and even to databases that is not tracked because according to documentation no login = no access, so it's a security hole | |
| Jul 11, 2017 at 9:24 | comment | added | vonPryz | No, it is not a bug. If the feature is not documented, there is no guarantee that it will work - or even work in consistent a manner. | |
| Jul 11, 2017 at 9:19 | comment | added | sepupic | @Remus Rusanu So I can consider it as a bug? That appeared starting with 2005 and then was fixed because it's a security hole? | |
| Jul 11, 2017 at 9:13 | comment | added | Remus Rusanu | Code behind an undocumented behavior changed. | |
| Jul 11, 2017 at 9:01 | history | asked | sepupic | CC BY-SA 3.0 |