| Age | Commit message (Collapse) | Author |
|---|
|
* john/erts/fix-zombie-tcp-ports/ERL-430/OTP-14441:
Unconditionally clear IO buffers on send/shutdown errors
|
|
|
|
|
|
|
|
* lars/xmerl/fragmented-xml-directive/OTP-14430:
[xmerl] Update version
[xmerl] Add test cases
[xmerl] Fix endDocument bug in output backends
[xmerl] Fix fragmented xml directive bug and replace ets table
|
|
* lukas/erts/restore-sigterm-default/OTP-14418:
erts: Add undocumented option to do default SIGTERM
|
|
This fixes a bug where a send/shutdown error on an active-mode socket results
in the port never being properly closed.
|
|
|
|
|
|
* Fix problem of unexpected endDocument in the old_dom and
simple output backends
|
|
* Fix continuation bug if the xml directive is fragmented
* Replace the ENTITY ets table with a map
|
|
This is a stopgap measure before the release of OTP-20 where
that makes it possible for the user to make the vm not do
anything with SIGTERM and instead rely on the OS default.
To enable this behaviour the user should set the environment
variable ERL_ZZ_SIGTERM_KILL="true".
|
|
|
|
|
|
* hans/inets/ftp_recv_chunk_close/OTP-14391:
inets: add testcase to ftp_SUITE Try doing three consecutive chunked receive with some changed timing in the ending sequence
inets: Try fix ftp recv_chunk timing issue
|
|
removed ct:pal call in ssl_connection
|
|
|
|
Try doing three consecutive chunked receive with some changed timing in the ending sequence
|
|
|
|
|
|
|
|
* ingela/fix-inets-releasnote:
inets: Add missing release note
|
|
* hasse/dialyzer/fix_unknown_types/OTP-14368:
dialyzer: Fix a bug regarding unknown types
|
|
* rickard/relnote-fix/OTP-14363:
Fix release note for OTP-14290
|
|
* mikpe/erts-erl_mseg-bad-cache-indexing/OTP-14360:
erl_mseg.c: don't use invalid indices in - > cache_powered_node[]
|
|
|
|
Since commit 12b3790 Dialyzer has not reported unknown types.
|
|
|
|
|
|
|
|
|
|
* rickard/sigterm/OTP-14358:
Do not ignore SIGTERM when VM has been started with +Bi
|
|
|
|
|
|
|
|
|
|
maint-19
* kellymclaughlin/crypto/aes_cfb_128/PR-1393/OTP-14313:
Fix bug with AES CFB 128
Demonstrate the bug with AES CFB 128 encryption
|
|
into maint-19
* raimo/file-read_file-leaks-file-descriptors/ERL-383/OTP-14308:
Close FD after trying to open a directory
|
|
into maint-19
* voltone/inets/httpc_redirect_normalize_host/PR-1381/OTP-14301:
Omit port from Host header on redirect to well-known port
|
|
* ingela/maint-19/active-once/ERL-371/OTP-14300:
ssl: Prepare for release
ssl: Avoid data loss in active once
|
|
* hans/ssh/daemon_info_crash_ip/OTP-14298:
ssh: fixed crash in ssh:daemon_info
|
|
* egil/erts/fix-sigterm/OTP-14290:
erts: Make sigterm signal safe for non-smp beam
|
|
* hans/ftp/recv_chunk/OTP-14242:
inets/ftp: spelling correction
inets/ftp: DBG macro change
inets/ftp: Fixed fault with operations after recv_chunks.
inets/ftp: Testcase for repeating chunked fetch
|
|
Fix a bug with the use of the aes_cfb128 cipher by calling the correct
underlying openssl interface function when the cipher is specified.
|
|
Demonstrate a bug with AES CFB 128 for certain key sizes introduced
with the Erlang 19.0 release. The code in the block_crypt_nif function
in the crypto.c source file incorrectly calls aes_cfb_8_crypt when the
specified cipher is aes_cfb8 or aes_cfb128 and the key size is 24 or
32. The aes_cfb_8_crypt function calls the AES_cfb8_encrypt function
from the openssl interface, but this is incorrect when the cipher is
aes_cfb128.
Unfortunately the test cases in the crypto test suite are insufficient
to detect an issue like this because it exercises the encryption and
decryption roundtrip using the same incorrect underlying function. The
problem was observed when trying to update an application to Erlang 19
that attempted to decrypt data that was encrypted using aes_cfb128 by
another source. In this commit I altered the crypto test suite to
provide a demonstration of this problem.
|
|
|
|
|
|
Emulate active once in such a way that data recived by the TLS
connection process, but not fetch via active once option
by the user, can be delivered at next active once before final close.
|
|
|
|
The signal handler will now schedule a sigterm message instead of sending
the message in the signal handler. The signal handler must refrain from
memory allocations and thus the event is scheduled.
|
