1 # A record of formal votes in reverse chronological order.
3 # To vote, add one of the following entries next to your name:
5 # [+1] I vote in favour of the proposal
6 # [ 0] I abstain from the vote
7 # [-1] I vote against the proposal
9 # If you are abstaining, you can indicate a tendency as follows:
11 # [+0] I abstain but with a slight lean towards a vote in favour
12 # [ 0] I abstain with no stated preference
13 # [-0] I abstain but with a slight lean towards a vote against
15 # A template for voting (alphabetical by surname) follows.
23 accepted: yes/no (for: X, against: Y, abstained: Z, not voted: T)
38 topic: Hold online weekly OTC meetings starting on Tuesday 2020-10-13
39 and until 3.0 beta1 is released, in lieu of the weekly "developer
41 Proposed by Nicola Tuveri
45 accepted: yes/no (for: X, against: Y, abstained: Z, not voted: T)
60 topic: The PR #11359 (Allow to continue with further checks on
61 UNABLE_TO_VERIFY_LEAF_SIGNATURE) is acceptable for 1.1.1 branch
62 As the change is borderline on bug fix/behaviour change OTC needs
63 to decide whether it is acceptable for 1.1.1 branch.
64 Proposed by Tomas Mraz
68 accepted: yes/no (for: X, against: Y, abstained: Z, not voted: T)
83 topic: The following items are required prerequisites for the first beta release:
84 1) EVP is the recommended API, it must be feature-complete compared with
85 the functionality available using lower-level APIs.
86 - Anything that isn’t available must be put to an OTC vote to exclude.
87 - The apps are the minimum bar for this, subject to exceptions noted below.
88 2) Deprecation List Proposal: DH_, DSA_, ECDH_, ECDSA_, EC_KEY_, RSA_,
90 - Does not include macros defining useful constants (e.g.
91 SHA512_DIGEST_LENGTH).
92 - Excluded from Deprecation: `EC_`, `DSA_SIG_`, `ECDSA_SIG_`.
93 - There might be some others.
94 - Review for exceptions.
95 - The apps are the minimum bar to measure feature completeness for the EVP
96 interface: rewrite them so they do not use internal nor deprecated
97 functions (except speed, engine, list, passwd -crypt and the code to handle
98 the -engine CLI option). That is, remove the suppression of deprecated
100 - Proposal: drop passwd -crypt (OMC vote required)
101 - Compile and link 1.1.1 command line app against the master headers and
102 library. Run 1.1.1 app test cases against the chimera. Treat this as an
103 external test using a special 1.1.1 branch.
104 - Deprecated functions used by libssl should be moved to independent file(s),
105 to limit the suppression of deprecated defines to the absolute minimum
107 3) Draft documentation (contents but not pretty)
108 - Need a list of things we know are not present - including things we have
110 - We need to have mapping tables for various d2i/i2d functions.
111 - We need to have a mapping table from “old names” for things into the
113 - Documentation addition to old APIs to refer to new ones (man7).
114 - Documentation needs to reference name mapping.
115 - All the legacy interfaces need to have their documentation pointing to
116 the replacement interfaces.
117 4) Review (and maybe clean up) legacy bridge code.
118 5) Review TODO(3.0) items #12224.
119 6) Source checksum script.
120 7) Review of functions previously named _with_libctx.
121 8) Encoder fixes (PKCS#8, PKCS#1, etc).
122 9) Encoder DER to PEM refactor.
123 10) Builds and passes tests on all primary, secondary and FIPS platforms.
124 11) Query provider parameters (name, version, ...) from the command line.
125 12) Setup buildbot infrastructure and associated instructions.
126 13) Complete make fipsinstall.
127 14) More specific decoding selection (e.g. params or keys).
128 15) Example code covering replacements for deprecated APIs.
129 16) Drop C code output options from the apps (OMC approval required).
130 17) Address issues and PRs in the 3.0beta1 milestone.
135 accepted: yes/no (for: X, against: Y, abstained: Z, not voted: T)
150 topic: We should accept the Fully Pluggable TLSv1.3 KEM functionality as shown
151 in PR #13018 into the 3.0 release
152 Proposed by Matt Caswell
156 accepted: yes/no (for: X, against: Y, abstained: Z, not voted: T)
171 topic: OTC meeting will be called for next Tuesday (2020-10-06)
172 Proposed by Matthias St. Pierre
176 accepted: yes (for: 7, against: 0, abstained: 0, not voted: 4)
179 Mark [+1] # 2020-09-30
185 Tomas [+1] # 2020-09-30
186 Kurt [+1] # 2020-09-30
191 topic: Accept the OTC voting policy as defined:
193 The proposer of a vote is ultimately responsible for updating the votes.txt
194 file in the repository. Outside of a face to face meeting, voters MUST reply
195 to the vote email indicating their preference and optionally their reasoning.
196 Voters MAY update the votes.txt file in addition.
198 The proposed vote text SHOULD be raised for discussion before calling the vote.
200 Public votes MUST be called on the project list, not the OTC list and the
201 subject MUST begin with “VOTE:”. Private votes MUST be called on the
202 OTC list with “PRIVATE VOTE:” beginning subject.
204 Proposed by Matthias St. Pierre (on behalf of the OTC)
208 accepted: yes (for: 9, against: 0, abstained: 0, not voted: 2)
223 topic: Adopt the coding style policy on function arguments as shown in chapter
224 6.1 of web PR 194 (commit f37f8a9000)
225 Proposed by Matt Caswell
229 accepted: no (for: 2, against: 5, abstained: 2, not voted: 2)
244 topic: Adopt the coding style policy on extending existing functions as shown
245 in chapter 6.2 of web PR 194 (commit f37f8a9000)
246 Proposed by Matt Caswell
250 accepted: yes (for: 5, against: 3, abstained: 2, not voted: 1)
254 Pauli [+1] # Vote changed 2020-09-21
266 topic: The performance improvements provided in PR11188 should be considered a
267 bug fix and therefore acceptable for backport to 1.1.1
268 Proposed by Matt Caswell
272 accepted: no (for: 0, against: 8, abstained: 3, not voted: 0)
288 topic: Rename OSSL_SERIALIZER / OSSL_DESERIALIZER to OSSL_ENCODER / OSSL_DECODER
290 The rationale is that it makes things easier on programmers
291 (encode / decode is easier to write than serialize / deserialize),
292 and also avoids disputes on what is and isn't serialization.
294 Associated issues and PRs: #12455, #12659 and #12660
299 accepted: yes (for: 5, against: 1, abstained: 4, not voted: 1)
307 Shane [-0] # Shane's vote was actually --0
314 topic: Rename OPENSSL_CTX to OSSL_LIB_CTX (as proposed by pull request #12621)
316 The main rationale behind this change is consistency, because many of the new
317 OpenSSL 3.0 types have an OSSL_ prefix, and OPENSSL_CTX is a notable exception.
318 More details can be found in the description and thread of pull request #12621.
320 There was a discussion on openssl-committers ('Rename OPENSSL_CTX to OSSL_WHAT?')
321 and an initial poll on doodle about the favourite replacements for OPENSSL_CTX
322 (https://doodle.com/poll/drku9ziwvkp6tw25).
324 Proposed by Matthias St. Pierre
328 accepted: yes (for: 5, against: 0, abstained: 4, not voted: 2)
343 topic: For change requests which target both the master and the
344 OpenSSL_1_1_1-stable branch, the following procedure should be followed:
345 - First, a pull request needs to be opened against the master branch for
346 discussion. Only after that pull request has received the necessary
347 amount of approvals, a separate pull request can be opened against the
348 OpenSSL_1_1_1-stable branch.
349 - A separate pull request against the OpenSSL_1_1_1-stable branch is
350 required. This holds - contrary to common practice - even if the change
351 can be cherry-picked without conflicts from the master branch. The only
352 exception from this rule are changes which are considered 'CLA: trivial',
353 like e.g. typographical fixes.
354 Proposed by Matt Caswell
358 accepted: no (for: 4, against: 4, abstained: 3, not voted: 0)
374 topic: Accept and merge #11577.
375 comment: #11577 reduces the maximum length of TLS labels.
376 It also breaks standards compliance.
381 accepted: no (for: 0, against: 9, abstained: 1, not voted: 1)
391 Kurt [-1] # 2020-06-09
396 topic: Keep FIPS_mode() as emulated by EVP_default_properties_is_fips_enabled(NULL)
397 Proposed by Tomas Mraz
401 accepted: no (for: 2, against: 5, abstained: 3, not voted: 1)
416 topic: approve PR#8300 statem: fix the alert sent for too large messages
417 Proposed by Tim Hudson
421 accepted: no (for: 1, against: 4, abstained: 6, not voted: 0)