Showing content from https://greenbytes.de/tech/webdav/draft-ietf-httpbis-http2-encryption-04.xml below:
This document describes a use of HTTP Alternative Services to decouple the URI scheme from the use and configuration of underlying encryption, allowing a http URI to be accessed using TLS opportunistically. Serving https URIs require acquiring and configuring a valid certificate, which means that some deployments find supporting TLS difficult. This document describes a usage model whereby sites can serve http URIs over TLS without being required to support strong server authentication. Opportunistic Security does not provide the same guarantees as using TLS with https URIs; it is vulnerable to active attacks, and does not change the security context of the connection. Normally, users will not be able to tell that it is in use (i.e., there will be no âlock iconâ). By its nature, this technique is vulnerable to active attacks. A mechanism for partially mitigating them is described in . The immediate goal is to make the use of HTTP more robust in the face of pervasive passive monitoring . A secondary goal is to limit the potential for active attacks. It is not intended to offer the same level of protection as afforded to https URIs, but instead to increase the likelihood that an active attack can be detected. A final (but significant) goal is to provide for ease of implementation, deployment and operation. This mechanism is expected to have a minimal impact upon performance, and require a trivial administrative effort to configure. The key words âMUSTâ, âMUST NOTâ, âREQUIREDâ, âSHALLâ, âSHALL NOTâ, âSHOULDâ, âSHOULD NOTâ, âRECOMMENDEDâ, âMAYâ, and âOPTIONALâ in this document are to be interpreted as described in . An origin server that supports the resolution of http URIs can indicate support for this specification by providing an alternative service advertisement for a protocol identifier that uses TLS, such as h2 . A client that receives such an advertisement MAY make future requests intended for the associated origin ( ) to the identified service (as specified by ). A client that places the importance of protection against passive attacks over performance might choose to withhold requests until an encrypted connection is available. However, if such a connection cannot be successfully established, the client can resume its use of the cleartext connection. A client can also explicitly probe for an alternative service advertisement by sending a request that bears little or no sensitive information, such as one with the OPTIONS method. Likewise, clients with existing alternative services information could make such a request before they expire, in order minimize the delays that might be incurred. requires that an alternative service only be used when there are âreasonable assurancesâ that it is under control of and valid for the whole origin. As defined in that specification, one way of establishing this is using a TLS-based protocol with the certificate checks defined in . Clients MAY impose additional criteria for establishing reasonable assurances. For the purposes of this specification, an additional way of establishing reasonable assurances is available when the alternative is on the same host as the origin, using the âhttp-opportunisticâ well-known URI defined in . This allows deployment without the use of valid certificates, to encourage deployment of opportunistic security. When it is in use, the alternative service can provide any certificate, or even select TLS cipher suites that do not include authentication. When the client has a valid http-opportunistic response for an origin, it MAY consider there to be reasonable assurances when: The origin and alternative serviceâs hostnames are the same when compared in a case-insensitive fashion, and The chosen alternative service returns the same response as above. For example, this request/response pair would constitute reasonable assurances for the origin âhttp://www.example.comâ for any alternative service also on âwww.example.comâ: GET /.well-known/http-opportunistic HTTP/1.1 Host: www.example.com HTTP/1.1 200 OK Content-Type: application/json Connection: close { "origins": ["http://example.com", "http://www.example.com:81"] } Note that this mechanism is only defined to establish reasonable assurances for the purposes of this specification; it does not apply to other uses of alternative services unless they explicitly invoke it. When using alternative services, requests for resources identified by both http and https URIs might use the same connection, because HTTP/2 permits requests for multiple origins on the same connection. Since https URIs rely on server authentication, a connection that is initially created for http URIs without authenticating the server cannot be used for https URIs until the server certificate is successfully authenticated. Section 3.1 of describes the basic mechanism, though the authentication considerations in also apply. Connections that are established without any means of server authentication (for instance, the purely anonymous TLS cipher suites), cannot be used for https URIs. Even when the alternative service is strongly authenticated, opportunistically upgrading cleartext HTTP connections to use TLS is subject to active attacks. In particular: Because the original HTTP connection is in cleartext, it is vulnerable to man-in-the-middle attacks, and By default, if clients cannot reach the alternative service, they will fall back to using the original cleartext origin. Given that the primary goal of this specification is to prevent passive attacks, these are not critical failings (especially considering the alternative - HTTP over cleartext). However, a modest form of protection against active attacks can be provided for clients on subsequent connections. When an origin is able to commit to providing service for a particular origin over TLS for a bounded period of time, clients can choose to rely upon its availability, failing when it cannot be contacted. Effectively, this makes the choice to use a secured protocol âstickyâ. An origin can reduce the risk of attacks on opportunistically secured connections by committing to provide an secured, authenticated alternative service. This is done by including the optional commit member in the http-opportunistic well-known resource (see ). This feature is optional due to the requirement for server authentication and the potential risk entailed (see ). The value of the commit member is a number ( , Section 6) indicating the duration of the commitment interval in seconds. { "origins": ["http://example.com", "http://www.example.com:81"], "commit": 86400 } Including commit creates a commitment to provide a secured alternative service for the advertised period. Clients that receive this commitment can assume that a secured alternative service will be available for the indicated period. Clients might however choose to limit this time (see ). The value of the commit member MUST be ignored unless the alternative service can be strongly authenticated. The same authentication requirements that apply to https:// resources SHOULD be applied to authenticating the alternative. Minimum authentication requirements for HTTP over TLS are described in Section 2.1 of and Section 3.1 of . As noted in , clients can impose other checks in addition to this minimum set. For instance, a client might choose to apply key pinning . A client that receives a commitment and that successfully authenticates the alternative service can assume that a secured alternative will remain available for the commitment interval. The commitment interval starts when the commitment is received and authenticated and runs for a number of seconds equal to value of the commit member, less the current age of the http-opportunistic response (as defined in Section 4.2.3 of ). A client SHOULD avoid sending requests via cleartext protocols or to unauthenticated alternative services for the duration of the commitment interval, except to discover new potential alternatives. A commitment only applies to the origin of the http-opportunistic well-known resource that was retrieved; other origins listed in the origins member MUST be independently discovered and authenticated. A commitment is not bound to a particular alternative service. Clients are able to use alternative services that they become aware of. However, once a valid and authenticated commitment has been received, clients SHOULD NOT use an unauthenticated alternative service. Where there is an active commitment, clients SHOULD ignore advertisements for unsecured alternative services. A client MAY send requests to an unauthenticated origin in an attempt to discover potential alternative services, but these requests SHOULD be entirely generic and avoid including credentials. Errors in configuration of commitments has the potential to render even the unsecured origin inaccessible for the duration of a commitment. Initial deployments are encouraged to use short duration commitments so that errors can be detected without causing the origin to become inaccessible to clients for extended periods. To avoid situations where a commitment causes errors, clients MAY limit the time over which a commitment is respected for a given origin. A lower limit might be appropriate for initial commitments; the certainty that a site has set a correct value - and the corresponding limit on persistence - might increase as a commitment is renewed multiple times. This specification defines the âhttp-opportunisticâ well-known URI . An origin is said to have a valid http-opportunistic resource when: The client has obtained a 200 (OK) response for the well-known URI from the origin, or refreshed one in cache , and That response has the media type âapplication/jsonâ, and That responseâs payload, when parsed as JSON , contains an object as the root. The âoriginsâ member of the root object has a value of an array of strings, one of which is a case-insensitive character-for-character match for the origin in question, serialised into Unicode as per , Section 6.1, and This specification defines one additional, optional member of the root object, âcommitâ in . Unrecognised members MUST be ignored. This specification registers a Well-known URI : URI Suffix: http-opportunistic Change Controller: IETF Specification Document(s): [this specification] Related Information: User Agents MUST NOT provide any special security indicia when an http resource is acquired using TLS. In particular, indicators that might suggest the same level of security as https MUST NOT be used (e.g., a âlock deviceâ). A downgrade attack against the negotiation for TLS is possible. With commitment , this is limited to occasions where clients have no prior information (see ), or when persisted commitments have expired. For example, because the Alt-Svc header field likely appears in an unauthenticated and unencrypted channel, it is subject to downgrade by network attackers. In its simplest form, an attacker that wants the connection to remain in the clear need only strip the Alt-Svc header field from responses. Downgrade attacks can be partially mitigated using the commit member of the http-opportunistic well-known resource, because when it is used, a client can avoid using cleartext to contact a supporting server. However, this only works when a previous connection has been established without an active attacker present; a continuously present active attacker can either prevent the client from ever using TLS, or offer its own certificate. Cached alternative services can be used to track clients over time; e.g., using a user-specific hostname. Clearing the cache reduces the ability of servers to track clients; therefore clients MUST clear cached alternative service information when clearing other origin-based state (i.e., cookies). Many existing HTTP/1.1 implementations use the presence or absence of TLS in the stack to determine whether requests are for http or https resources. This is necessary in many cases because the most common form of an HTTP/1.1 request does not carry an explicit indication of the URI scheme. HTTP/1.1 MUST NOT be used for opportunistically secured requests. Some HTTP/1.1 implementations use ambient signals to determine if a request is for an https resource. For example, implementations might look for TLS on the stack or a port number of 443. An implementation that supports opportunistically secured requests SHOULD suppress these signals if there is any potential for confusion.
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4