Re:Consumer key/secret for official Twitter clients
by Spooky23 on Thursday March 07, 2013 @04:26PM
(#5340384)
That's why we have Kerberos.
[ Parent
| on HN ]
Re:Consumer key/secret for official Twitter clients
by vicaya on Thursday March 07, 2013 @05:18PM
(#5340737)
No Kerberos won't help in this case. Once you have the keytab you can impersonate the client. Kerberos doesn't solve the "trusted client" issue.
Re:Consumer key/secret for official Twitter clients
by Spooky23 on Friday March 08, 2013 @09:16AM
(#5343500)
It doesn't help in the Twitter client use case, but it will help in the user/password compromise scenario described in the parent comment.
If I compromise the keytab, I can impersonate the domain member server and presumably the active tickets... but the username/password is on the KDC/DC.