Activity log for bug #1389034
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2014-11-04 01:13:01 | Sam Stavinoha | bug | added bug | ||
| 2014-11-04 01:13:44 | Sam Stavinoha | description | It is common to see the following error/log output when trying to communicate with remote windows servers. Impacket v0.9.12 - Copyright 2002-2014 Core Security Technologies Trying protocol 51666/SMB... SMB SessionError: STATUS_LOGON_FAILURE(The attempted logon is invalid. This is either due to a bad username or authenti cation information.) It would be useful to read this output explicitly (if it is the consistent output across most windows servers) and raise a specific authentication failure exception to inform the caller that the supplied credentials were invalid. What currently happens is SubprocessError: subprocess with pid: 12345 has terminated unexpectedly (not informative!) | It is common to see the following error/log output when trying to communicate with remote windows servers: Impacket v0.9.12 - Copyright 2002-2014 Core Security Technologies Trying protocol 51666/SMB... SMB SessionError: STATUS_LOGON_FAILURE(The attempted logon is invalid. This is either due to a bad username or authentication information.) It would be useful to read this output explicitly (if it is the consistent output across most windows servers) and raise a specific authentication failure exception to inform the caller that the supplied credentials were invalid. What currently happens is SubprocessError: subprocess with pid: 12345 has terminated unexpectedly (not informative!) | |
| 2014-11-04 01:14:15 | Sam Stavinoha | description | It is common to see the following error/log output when trying to communicate with remote windows servers: Impacket v0.9.12 - Copyright 2002-2014 Core Security Technologies Trying protocol 51666/SMB... SMB SessionError: STATUS_LOGON_FAILURE(The attempted logon is invalid. This is either due to a bad username or authentication information.) It would be useful to read this output explicitly (if it is the consistent output across most windows servers) and raise a specific authentication failure exception to inform the caller that the supplied credentials were invalid. What currently happens is SubprocessError: subprocess with pid: 12345 has terminated unexpectedly (not informative!) | It is common to see the following error/log output when trying to communicate with remote windows servers: Impacket v0.9.12 - Copyright 2002-2014 Core Security Technologies Trying protocol 51666/SMB... SMB SessionError: STATUS_LOGON_FAILURE(The attempted logon is invalid. This is either due to a bad username or authentication information.) It would be useful to read this output explicitly (if it is the consistent output across most windows servers) and raise a specific authentication failure exception to inform the caller that the supplied credentials were invalid. What currently happens is SubprocessError: subprocess with pid: 12345 has terminated unexpectedly (not informative!) | |
| 2014-11-04 20:19:46 | OpenStack Infra | satori: status | New | In Progress | |
| 2014-11-27 05:53:12 | OpenStack Infra | satori: status | In Progress | Fix Committed |
