[BACK]Return to web_browser.mdwn CVS log [TXT] [DIR] Up to [NetBSD Developer Wiki] / wikisrc / kerberos

Diff for /wikisrc/kerberos/web_browser.mdwn between versions 1.4 and 1.8

version 1.4, 2009/11/05 01:31:01 version 1.8, 2011/07/31 22:29:30
Line 5  First, Kerberize your [[system]]. Then: Line 5  First, Kerberize your [[system]]. Then:
 7. Open Firefox.  7. Open Firefox.
 7. Go to [about:config](about:config).  7. Go to [about:config](about:config).
 7. Filter for `network.negotiate-auth`.  7. Filter for `network.negotiate-auth`.
 7. Set `network.negotiate-auth.trusted-uris` and  7. Set `network.negotiate-auth.trusted-uris` (_not_
 `network.negotiate-auth.delegation-uris` to `netbsd.org`.  `network.negotiate-auth.delegation-uris`) to `netbsd.org`.
   7. **(Windows only)** Filter for `use-sspi`, then set `network.auth.use-sspi` to `false`.
 """]]  """]]
   
 #### [[!toggle id="konqueror" text="Konqueror"]]  #### [[!toggle id="konqueror" text="Konqueror"]]
Line 20  Possibly the same as [[!toggle id="safar Line 21  Possibly the same as [[!toggle id="safar
 7. There is no Step 2.  7. There is no Step 2.
 """]]  """]]
   
   #### [[!toggle id="chrome" text="Google Chrome"]]
   [[!toggleable id="chrome" text="""
   7. Run Chrome [with the `--auth-server-whitelist`
      argument](http://sites.google.com/a/chromium.org/dev/developers/design-documents/http-authentication).
      For example, in Mac OS X:
   
       $ open /Applications/Google\ Chrome.app --args --auth-server-whitelist="*.netbsd.org"
   """]]
   
 #### [[!toggle id="ie" text="Internet Explorer"]]  #### [[!toggle id="ie" text="Internet Explorer"]]
 [[!toggleable id="ie" text="""  [[!toggleable id="ie" text="""
 Internet Explorer can use Microsoft's built-in Kerberos. Anyone know how? Some possibly relevant links:  Internet Explorer can use Microsoft's built-in Kerberos. Anyone know how? Some possibly relevant links:
   
   > Sadly, it seems MS IE can only use tickets cached inside LSA (Local Security Authority), and this cache is only created upon logon through winlogon service. Which means that a `host/<windows_machine>` principal would be needed for each Windows client that wants to cache a TGT. This is only suitable for Intranet-like networks. Maybe there is another way to manage the LSA after login, similar to [[!template id=man name=kinit section=1]]... --[[jym]]
   
 * <http://rc.quest.com/topics/mod_auth_vas/howto.php#iexplore>  * <http://rc.quest.com/topics/mod_auth_vas/howto.php#iexplore>
 * <http://support.microsoft.com/kb/299838>  * <http://support.microsoft.com/kb/299838>
 * <http://technet.microsoft.com/en-us/library/cc779070(WS.10).aspx>  * <http://technet.microsoft.com/en-us/library/cc779070(WS.10).aspx>
Removed from v.1.4  
changed lines
  Added in v.1.8

CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb