Do not resolve hostname when mounting for Kerberos |
|||||
Issue descriptionKerberos relies on hostnames for ticket operations, so resolving the name into an IP Address should not happen for these shares. The hostname will have to be resolved by a DNS controller on the network which presumably exists if trying to mount with kerberos
,
Oct 4
,
Oct 8
,
Oct 11
,
Oct 11
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/08ec72e1da1938eacb5aa832c80890e91bae53e1 commit 08ec72e1da1938eacb5aa832c80890e91bae53e1 Author: Bailey Berro <baileyberro@chromium.org> Date: Thu Oct 11 16:20:58 2018 Do not resolve hostname when mounting share with kerberos - When using chromad kerberos, don't resolve the hostname into an ip address since kerberos service tickets are keyed on the hostname - Previously, we resolved any hostname we could (meaning the share was found during discovery) into an ip address, which could prevent chromad kerberos from working correctly. Bug: chromium:853806 Change-Id: I48feec54defdb2821dee526f9f25cff0260363b6 Reviewed-on: https://chromium-review.googlesource.com/c/1274048 Commit-Queue: Bailey Berro <baileyberro@chromium.org> Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org> Cr-Commit-Position: refs/heads/master@{#598788} [modify] https://crrev.com/08ec72e1da1938eacb5aa832c80890e91bae53e1/chrome/browser/chromeos/smb_client/smb_service.cc
,
Oct 11
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by weifangsun@chromium.org
, Sep 28