-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathindex.html
128 lines (100 loc) · 4.6 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content=
"HTML Tidy for Mac OS X (vers 31 October 2006 - Apple Inc. build 10705), see www.w3.org" />
<meta http-equiv="Content-Type" content=
"text/html; charset=us-ascii" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="generator" content="pandoc" />
<title></title>
<style type="text/css">
/*<![CDATA[*/
code{white-space: pre;}
/*]]>*/
</style>
</head>
<body>
<h1>What This Is</h1>
<p>This is a fork of the <a href=
"https://www.openssl.org">OpenSSL library</a>. It started as a
project to only enable QUIC, but as time went on, we believe
OpenSSL strayed further from what their bulk of their community
wants. As such, this has evolved into a a full-fledged fork of
OpenSSL. We are already closely collaborating with the other two
major forks, BoringSSL and Libre, and our longer-range plan is to
turn this over into a viable Apache Software Foundation
project.</p>
<p>This project <em>enables</em> QUIC, it does not
<em>implement</em> it. The API's were first developed by Google
and are now in widespread use, including Microsoft's <a href=
"https://github.com/microsoft/msquic">MsQuic</a>, Google's
<a href=
"https://chromium.googlesource.com/chromium/src/+/master/net/quic/">
Chromium QUIC</a>, and others.</p>
<p>You can find a more minimal set of patches -- just providing
the QUIC API -- at our <a
href="https://github.com/quictls/openssl">OpenSSL repository</a>.
That covers their 1.1 release and the 3.0 stream up through 3.2.
The software here is based on the OpenSSL 3.3 release.</p>
<h1>On to the questions and answers.</h1>
<h2>What about branches?</h2>
<p>We don't want to conflict with OpenSSL branch names. Our
previous plan was to append <code>+quic</code> to upstream tag
names to create our branches. Now that we are indpendant of
OpenSSL we will need to think about this.</p>
<h2>How are you keeping current with OpenSSL?</h2>
<p>We will cherry-pick security and other important fixes from
OpenSSL mainline as they appear. If you see a particular PR of
theirs that is important to you, please <a href=
"https://github.com/quictls/quictls/issues">open an
issue</a>.</p>
<h2>What about library names?</h2>
<p>Library names will be the same, but might use a different
version number eventually. The version numbers for the current
OpenSSL libraries are <code>3</code> (for the 3.0 branch). We
will be prefixing 81 (ASCII for 'Q') to the version numbers to
generate a unique version number.</p>For example:
<ul>
<li>libcrypto.so.81.3 vs libcrypto.so.3</li>
<li>libcrypto.so.81.1.1 vs libcrypto.so.1.1</li>
<li>libssl.so.81.3 vs libssl.so.3</li>
<li>libssl.so.81.1.1 vs libsslo.so.1.1</li>
</ul>
<p>The SONAME of these libraries are all different, guaranteeing
the correct library will be used.</p>
<h2>...and the executable?</h2>
<p>We currently do not have any plans to change the name, for
compatibility.</p>
<p>The <code>openssl version</code> command will report that it
is <code>+quic</code> enabled.</p>
<h2>...and FIPS?</h2>
<p>We are not doing anything with FIPS. This is actually good
news: you should be able to load the OpenSSL 3 FIPS module into
an application built against this fork and everything should Just
Work.</p>
<h2>How can I contribute?</h2>
<p>We want any code here to be acceptable to OpenSSL. For now,
our PR requires a checkbox saying you are authorizing
the contribution under the terms of the ASF license. You might
want to think about signing the appropriate <a href=
"https://www.openssl.org/policies/cla.html">OpenSSL contributor license
agreements</a>.
We want this code to be usable by any and all forks, should they
desire.</p>
<h2>Who are you?</h2>
<p>This is a collaborative effort between <a href=
"https://www.akamai.com">Akamai</a> and <a href=
"https://www.microsoft.com">Microsoft</a>. We welcome anyone to
contribute!</p>To learn more about HTML Tidy see
http://tidy.sourceforge.net Please send bug reports to
[email protected] HTML and CSS specifications are available from
http://www.w3.org/ Lobby your company to join W3C, see
http://www.w3.org/Consortium
</body>
</html>
To learn more about HTML Tidy see http://tidy.sourceforge.net
Please send bug reports to [email protected]
HTML and CSS specifications are available from http://www.w3.org/
Lobby your company to join W3C, see http://www.w3.org/Consortium