Public bug reported:
[Impact]
The tls bidir test from the network kselftests fails with the ChaCha
cipher:
# RUN tls.12_chacha.bidir ...
# tls.c:845:bidir:Expected ret (-1) == 0 (0)
# bidir: Test terminated by assertion
# FAIL tls.12_chacha.bidir
This is a problem with the test. The test fixture setup configures tls
in one direction on the test socket pair according to the cipher being
tested. The test case configures tls in the other direction, however it
always configures for GCM regardless of the cipher being tested. When
the test cipher is ChaCha the setsockopt() calls fail as the cipher is
required to be the same in both directions.
[Test Plan]
Run the tls test from the net kselftests and confirm that the bidir test
now passes when the test cipher is ChaCha.
[Where problems could occur]
This is a fix for a test case and should have no user impact. A serious
problem in the test case might cause passing test cases to fail or
prevent subsequent test cases from running. Any such issues should be
caught during testing in -proposed before releasing kernels to users.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Fix Committed
** Affects: linux (Ubuntu Hirsute)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: linux (Ubuntu Hirsute)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933268
Title:
net kselftest failures in the tls bidir test case
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
The tls bidir test from the network kselftests fails with the ChaCha
cipher:
# RUN tls.12_chacha.bidir ...
# tls.c:845:bidir:Expected ret (-1) == 0 (0)
# bidir: Test terminated by assertion
# FAIL tls.12_chacha.bidir
This is a problem with the test. The test fixture setup configures tls
in one direction on the test socket pair according to the cipher being
tested. The test case configures tls in the other direction, however
it always configures for GCM regardless of the cipher being tested.
When the test cipher is ChaCha the setsockopt() calls fail as the
cipher is required to be the same in both directions.
[Test Plan]
Run the tls test from the net kselftests and confirm that the bidir
test now passes when the test cipher is ChaCha.
[Where problems could occur]
This is a fix for a test case and should have no user impact. A
serious problem in the test case might cause passing test cases to
fail or prevent subsequent test cases from running. Any such issues
should be caught during testing in -proposed before releasing kernels
to users.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933268/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
