summaryrefslogtreecommitdiffstats
path: root/chrome/browser/internal_auth.h
Commit message (Collapse)AuthorAgeFilesLines
* extensions: Remove chrome.webSocketProxyPrivate APIsatorux@chromium.org2013-08-021-8/+0
| | | | | | | | | | | | The private API is no longer in use. BUG=244359 TEST=none R=asargent@chromium.org, dpolukhin@chromium.org, thestig@chromium.org Review URL: https://codereview.chromium.org/21115004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@215190 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the rest of #pragma once in one big CL.ajwong@chromium.org2012-07-111-1/+0
| | | | | | | | | For context see this thread: https://groups.google.com/a/chromium.org/forum/?fromgroups#!topic/chromium-dev/RMcVNGjB4II TBR=thakis,pkasting,jam git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146163 0039d316-1c4b-4281-b951-d872f2087c98
* browser: Move more files into chrome namespace.tfarina@chromium.org2012-07-021-16/+18
| | | | | | | | | BUG=133088 TBR=ben@chromium.org Review URL: https://chromiumcodereview.appspot.com/10694060 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145220 0039d316-1c4b-4281-b951-d872f2087c98
* Moving web_socket_proxy_private into a sub-dir in api/vabr@chromium.org2012-05-251-3/+5
| | | | | | | | | | | | and including it into extensions namespace. BUG=101244 TEST=ExtensionWebSocketProxyPrivateApiTest Review URL: https://chromiumcodereview.appspot.com/10445013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139011 0039d316-1c4b-4281-b951-d872f2087c98
* Support SSL connections in websocket-to-TCP proxy.dilmah@chromium.org2011-10-141-0/+2
| | | | | | | | | | | | | | | | | For historical reasons current implementation of WS-to-TCP proxy was implemented as standalone libevent-based server. Then it was integrated into chromium as is. In order to support SSL we need to connect libevent-based proxy with MessageLoopForIO-based chromium network stack. We do it using pipes. It is intended as temporary solution until we will have new shiny implementation of WS-to-TCP proxy integrated into network stack. BUG=chromium-os:15533 TEST=Manual Review URL: http://codereview.chromium.org/8087001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@105515 0039d316-1c4b-4281-b951-d872f2087c98
* Private API for extensions like ssh-client that need access to ↵dilmah@chromium.org2011-05-181-0/+74
websocket-to-tcp proxy. Access to TCP is obtained in following way: (1) extension requests authentication token via call to private API like: chrome.webSocketProxyPrivate.getPassportForTCP('netbsd.org', 25, callback); if API validates this request then extension obtains some string token (in callback). (2) open websocket connection to local websocket-to-tcp proxy ws://127.0.0.1:10101/tcpproxy (3) pass header containing hostname, port and token obtained at step (1) (4) communicate (in base64 encoding at this moment). Proxy (running in chrome process) verifies those tokens by calls to InternalAuthVerification::VerifyPassport Passports are one-time; no passport can be reused. Passports expire in short period of time (20 seconds). BUG=chromium-os:9667 TEST=unit_test,apitest Review URL: http://codereview.chromium.org/6683060 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@85757 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-03-31 21:45:12 +0000