-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
COMException during relay #9
Comments
Having same problem too. |
also have a config where this issue came up. the same happens if using the original KrbRelay (to LDAP) before getting a successful LDAP relay. perhaps a mitigation setting other than ldap signature enforcement / channel binding? |
Does it work after logout->login? |
I actually run it using Execute Assembly
…On Tue, 10 May 2022 at 12:53, Mor Davidovich ***@***.***> wrote:
Does it work after logout->login?
Or if you use:
*Rubeus.exe asktgt /user:lowprivuser /password:something /ptt*
Just checking something, let me know..
—
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3N7UU7A6FBFQRRVZKIZZTVJHTVTANCNFSM5VCIHFZQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
asktgt works normally for me and I am having the same error stated above with krbrelayup |
I'm getting the same error in corp env, the COM server does not return apRep1 back to the client. In wireshark the |
I get same problem. Did anyone resolve this issue ? |
Hello!
Unable to complete relay (sensitive data removed)
Further debugging via Visual Studio:
The text was updated successfully, but these errors were encountered: