| Age | Commit message (Collapse) | Author |
|---|
|
As per RFC 4492 Sec 5.1, the preferred order of selection of named
curves is based on client preferences.
Currently, the SSL application only picks entries according to the
absolute order of entries as tracked in a hardcoded list in code.
This patch changes things so that the client-specified order is
preferred. It also allows a mode where the server can be configured to
override the client's preferred order with its own, although the chosen
ECC must still be within both lists.
The configuration is done through the following options:
- `eccs`, shared by clients and servers alike, allows the specification
of the supported named curves, in their preferred order, and may
eventually support more values for explicit primes and so on.
- `honor_ecc_order`, a server-only option, is similar to
`honor_cipher_order` and will, by default let the server pick the
client-preferred ECC, and otherwise pick the server-preferred one.
The default value for `eccs` is the same as before, although the
server-chosen ECC now defaults to the client rather than previous
choice.
A function `ssl:eccs()` has been added that returns the highest
supported ECCs for the library.
|
|
* gomoripeti/stdlib/ms_fix/PR-1203/OTP-13974:
dbg:fun2ms: allow empty list as head
|
|
* raimo/gen_statem-improvements/OTP-13929:
Fix race condition in cancel_timer/1
Use parameterized types
Implement state timeouts
Improve docs and types
Change state entry events into state enter calls
Improve docs
Improve docs
Implement state entry events
Implement call/3 dirty_timeout
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* egil/erl_docgen/reformat-docgen-encoding/OTP-13971:
Reformat docgen xml encoding
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Running 'dbg:fun2ms(fun([]) -> return_trace() end' resulted in an error
"dbg:fun2ms requires fun with single variable or list parameter"
But the empty list is actually a list and it is a valid value as a
match-spec head (matching on arity-0 functions).
Although its practical use is questionable this commit eliminates a
small limitation of ms_transform which is not present in the match-spec
grammar.
|
|
|
|
|
|
|
|
This tests an illegal client that sends an info line and closes 'immediatly'.
|
|
|
|
* hasse/dialyzer/fix_opaque_bugs/OTP-13693:
dialyzer: Fix opaque bug
dialyzer: Fix opaque bugs
|
|
* xsipewe/dialyzer/doc_cleanup:
Update Dialyzer documentation
|
|
|
|
epp:default_encoding/0 returns 'utf8' and needs to be re-encoded
to "UTF-8" to be correct.
|
|
* github/pr/1199:
Correct a typo in mod_esi documentation
|
|
* ingela/ssl/algo-check/OTP-13959:
Properly filter ssl cipher suites reported as supported
|
|
* ingela/ssl/crl_SUITE:
ssl: Make sure test has correct input
|
|
|
|
Language cleaned up by the technical writer xsipewe from
Combitech. Proofreading and corrections by Hans Bolinder.
|
|
|
|
|
|
This reverts commit 28baf1314b556bb592c24181f6967e1f324f44a7.
|
|
* sverker/load_nif-print-init-error:
crypto: Return source line number from failed load/upgrade
erts: Print error code from failed NIF load/upgrade/reload
|
|
Adapted from commit 675ee6860d2c273bcc6c6a0536634a107e2a3d9f.
Conflicts:
lib/ssl/src/ssl_cipher.erl
|
|
* bjorn/compiler/beam_bsm/ERL-268/OTP-13947:
beam_bsm: Eliminate unsafe optimization
|
|
* ingela/inets/httpc/ERL-253:
inets: httpc improve error handling
|
|
* kostis/inets-reference-record-types/PR-1188:
Replace ref() with reference() in inets files
|
|
* ingela/ssl/cipher-type-spec:
ssl: Adjust cipher type to conform to implementation
|
|
* dgud/wx/fix-unicode-chardata/ERL-270/OTP-13934:
Fix guard test for chardata
|
|
* dgud/mnesia/dirty_select_cont/PR-1184/OTP-13944:
Allow reusing mnesia select continuations
|
|
* dgud/tools/emacs/edoc-support/PR-1195/OTP-13945:
New file erlang-edoc.el to support EDoc in erlang-mode
|
|
Fixes a bug that makes the ftp client end up in
bad state if there is a multi line response from
the server and the response number is in the
message being sent.
|
|
The "decoration" of opaque types works better than before when opaque
types are used by other opaque types.
|
|
t_from_form() sometimes returned a more general type than it should
have done due to a bug in from_form_loop(): it stopped when the limit
was exceeded, which could mean a collapsed type. Returning a type with
smaller depth should fix this.
is_specialization() now handles opaque types before unions, which
should fix another problem.
The bugs reported by Kostis.
|
|
- EDoc markup font-locking and tag completion
- EDoc comment indentation
|
|
|
|
|
|
A continuation returned by mnesia:select/[14] should be reusable in
different, non-transactional activities. Aborting with
wrong_transaction doesn't make sense in a dirty context.
|
