From Fedora Project Wiki

(Created page with "{{Infobox_group | name = <<TEST DAY NAME>> | image = 300px|link=QA/Test Days | date = <<FIXME>> | time = all day | website = QA/Test Days | i...")
 
(manually fix up bug refs to be in result templates)
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Infobox_group
{{Infobox_group
| name = <<TEST DAY NAME>>
| name = Crypto Policies
| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]
| image = [[File:test-days-banner.svg|300px|link=QA/Test Days]]
| date = <<FIXME>>
| date = 2017-03-30
| time = all day
| time = all day
| website = [[QA/Test Days]]
| website = [[QA/Test Days]]
Line 13: Line 13:
== What to test? ==
== What to test? ==


Today's instalment of Fedora Test Day will focus on '''<<FIXME>>'''
Today's instalment of Fedora Test Day will focus on [[Changes/CryptoPolicy|crypto-policies]]


== Who's available ==
== Who's available ==


The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion. In case of problem related to test day organization/wiki/whatever, please reach out to szidek.
* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
* Development - [[User:Nmav|Nikos Mavrogiannopoulos]] (nmav, GnuTLS, crypto-policies), [[User:Tmraz|Tomáš Mráz]] (t8m, OpenSSL), Kai Engert (kaie, NSS), [[User:Rrelyea|Robert Relyea]] (rrelyea, NSS), [[User:Ueno|Daiki Ueno]] (ueno, NSS), [[User:Jjelen|Jakub Jelen]] (jjelen, OpenSSH)
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4)
* Quality Assurance - [[User:Szidek|Stanislav Židek]] (szidek), [[User:Hkario|Hubert Kario]] (hkario)


== Prerequisite for Test Day ==  
== Prerequisite for Test Day ==  
 
* An updated Fedora 26 [https://getfedora.org/workstation/prerelease workstation] or [https://getfedora.org/server/prerelease server] pre-release, or a [https://www.happyassassin.net/nightlies.html Fedora 26 nightly image]
List any prerequisite needs for the test event.  A fresh system, virtualized guest, a blank DVD ... a desire to break software?
* a desire to break software ;)
 
* Usb key
* Usb externally connected HD IDE/SATA
* Empty HD IDE/SATA/SCSI
* Free space on HD
 
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
 
* An updated [https://getfedora.org/workstation/prerelease Fedora XX pre-release], or a [https://www.happyassassin.net/nightlies.html Fedora XX nightly image]


== How to test? ==
== How to test? ==
High level details on how a contributor can get involved.  This can include (but not limited to):
* Areas to target with exploratory testing
* A list of pre-defined test cases to execute
* How to report back results
Here's another common chunk (again, replace XX as above):


=== '''Update your machine''' ===
=== '''Update your machine''' ===


If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
If you're running Fedora 26, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:


=== '''Live image''' ===
=== '''Live image''' ===
Line 54: Line 37:
=== Run the tests ===
=== Run the tests ===


If not using the Test Day app, provide a list of test areas or test cases that you'd like contributors to execute. For examples, see [[:Category:Test_Cases]]. If using the Test Day app, link to it here, with some explanation, e.g.:
Visit the [http://testdays.fedorainfracloud.org/events/16 result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.
 
Visit the [http://testdays.fedorainfracloud.org/events/NUMBER result page] and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the ''Enter result'' button for the test.


== Reporting bugs ==
== Reporting bugs ==
Line 62: Line 43:
Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:


If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=26&component=crypto-policies crypto-policies], or for particular software using crypto-policies. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.


== Test Results ==
== Test Results ==


If you use the [http://testdays.fedorainfracloud.org/events Test Days app], just explain that users should enter results there and they will be transferred to the page later. For e.g.:
Results transferred from the [http://testdays.fedorainfracloud.org/events/16 result page] on 2017-04-10.


Please enter your results on the [http://testdays.fedorainfracloud.org/events/NUMBER result page]. The results will be transferred here after the Test Day is finished.
=== Basic ===
{|
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_CryptoPolicies_Sanity Sanity]
! [http://fedoraproject.org/wiki/QA:Testcase_CryptoPolicies_BogusProfile Switching to bogus profile]
! [http://fedoraproject.org/wiki/QA:Testcase_CryptoPolicies_openssh OpenSSH support]
! [http://fedoraproject.org/wiki/QA:Testcase_CryptoPolicies_Firefox Firefox]
! [http://fedoraproject.org/wiki/QA:Testcase_CryptoPolicies_Java Java]
! References
|-
| [[User:Tenk|Tenk]]
| F26 Alpha 1.7
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|fail||1437213}}
|
| <references/>
|-
| [[User:akashche|akashche]]
| F26 running in Docker
| {{result|pass}}<ref>https://bugzilla.redhat.com/show_bug.cgi?id=1437213 - cannot access rc4.badssl.com, 3des.badssl.com worked as expected</ref>
| {{result|pass}}
|
| {{result|pass}}
| {{result|pass}}
| <references/>
|-
| [[User:coremodule|coremodule]]
|
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}{{result|warn}}<ref>For FUTURE, received this output:
Unable to negotiate with ::1 port 22: no matching cipher found. Their offer: 3des-cbc
</ref>
|
| {{result|pass}}
| <references/>
|-
| [[User:jsedlak|jsedlak]]
|
| {{result|pass}}<ref>Everything that was uncommented ran OK.</ref>
| {{result|pass}}
|
|
|
| <references/>
|-
| [[User:jvanek|jvanek]]
|
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
|
| {{result|warn}}<ref>As mentioned by pmikova and mvala - when FUTURE is selected, nearly no https connection is possible to establish with icedtea-web</ref>
| <references/>
|-
| [[User:krouma|krouma]]
|
| {{result|pass}}
| {{result|pass}}<ref>Passed even with special symbols and Czech characters</ref>
| {{result|pass}}
| {{result|fail}}<ref>Test part 3.: Web pages https://3des.badssl.com/ and https://rc4.badssl.com/ were failing for all 3 profiles.</ref>{{result|fail}}
| {{result|pass}}
| <references/>
|-
| [[User:lzachar|lzachar]]
|
| {{result|fail||1437213|1437209|1437363}}<ref>1437363 not yet mentioned on testcase wiki</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}<ref>with https://koji.fedoraproject.org/koji/taskinfo?taskID=18679218</ref>
| {{result|pass}}
| <references/>
|-
| [[User:mvala|mvala]]
|
|
|
|
|
| {{result|warn}}<ref>SSL missing in FUTURE</ref>{{result|pass}}
| <references/>
|-
| [[User:pkis|pkis]]
|
| {{result|pass}}
| {{result|warn||1437449}}<ref>The test pass, but an usability issue was filed: BZ#1437449</ref>
| {{result|pass}}
|
|
| <references/>
|-
| [[User:pmikova|pmikova]]
|
|
|
|
|
| {{result|warn}}<ref>useSystemPropertiesFile=true sudo update-crypto-policies --set FUTURE
https://www.elsteronline.de/eportal/KonfigurationsAssistentA.tax?requestaction=KonfigurationsAssistentA.tax - Error performing TLS handshake: The signature algorithm is not supported.
java CipherList | wc -l  is 25 on FUTURE but java CipherList | wc -l is 36 on DEFAULT
diff https://gist.github.com/sparkoo/ef37b8624f922b5c08d084dde23bdad4</ref>
| <references/>
|-
| [[User:pschindl|pschindl]]
| Updated F26
| {{result|fail||1437213|1437209|1437363}}
| {{result|pass}}
| {{result|pass}}
|
|
| <references/>
|-
| [[User:zdenek|zdenek]]
|
| {{result|pass}}<ref>Commands were completed without FAIL</ref>
| {{result|pass}}
|
| {{result|fail}}<ref>Test part 3.: Web pages https://3des.badssl.com/ and https://rc4.badssl.com/ were failing for all 3 profiles.</ref>
|
| <references/>


Otherwise, construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results. Include some text to explain reporting. Here is a common setup:
|-
|}


Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
=== User driven ===
{|
{|
! User
! User
! [[QA:Testcase_sample_1|Sample test 1]]
! Profile
! [[QA:Testcase_sample_2|Sample test 2]]
! [http://fedoraproject.org/wiki/QA:Testcase_CryptoPolicies_InTheWildFUTURE FUTURE profile with commonly visited sites]
! [[QA:Testcase_sample_3|Sample test 3]]
! [http://fedoraproject.org/wiki/QA:Testcase_CryptoPolicies_SpecificApps Specific apps]
! [[QA:Testcase_sample_4|Sample test 4]]
! [http://fedoraproject.org/wiki/QA:Testcase_CryptoPolicies_OwnApp Own app]
! References
! References
|-
|-
| [[User:SampleUser|Sample User]]
| [[User:akashche|akashche]]
| {{result|none}}
| F26 in Docker
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
|
| {{result|fail}} <ref>{{bz|12345}}</ref>
| {{result|pass}}<ref>Tried FUTURE with https://github.com/ojdkbuild/contrib_update-notifier , https://github.com/staticlibs/staticlib_httpserver and https://github.com/staticlibs/staticlib_httpclient</ref>
| <references/>
| <references/>
|-
|-
|}
|}


<!-- remove this comment block when creating a real Test Day
[[Category:Fedora 26 Test Days]]
[[Category:Fedora 24 Test Days]]
-->
 
<!-- remove this category when creating a test day page -->
[[Category:QA Templates]]

Latest revision as of 18:44, 10 April 2017

Crypto Policies
Test-days-banner.svg
Date 2017-03-30
Time all day
Website QA/Test Days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

Today's instalment of Fedora Test Day will focus on crypto-policies

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion. In case of problem related to test day organization/wiki/whatever, please reach out to szidek.

Prerequisite for Test Day[edit]

How to test?[edit]

Update your machine[edit]

If you're running Fedora 26, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Or:

Live image[edit]

Instead of testing with an installed system, you may download a non-destructive nightly live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live image links can be found here: please be sure to download one for the correct release.

Run the tests[edit]

Visit the result page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.

Reporting bugs[edit]

Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:

If you have problems with any of the tests, report a bug to Bugzilla usually for the component crypto-policies, or for particular software using crypto-policies. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.

Test Results[edit]

Results transferred from the result page on 2017-04-10.

Basic[edit]

User Profile Sanity Switching to bogus profile OpenSSH support Firefox Java References
Tenk F26 Alpha 1.7
Pass pass
Pass pass
Pass pass
Fail fail [1]
  1. ↑ RHBZ #1437213
akashche F26 running in Docker
Pass pass
[1]
Pass pass
Pass pass
Pass pass
  1. ↑ https://bugzilla.redhat.com/show_bug.cgi?id=1437213 - cannot access rc4.badssl.com, 3des.badssl.com worked as expected
coremodule
Pass pass
Pass pass
Pass pass
Warning warn
[1]
Pass pass
  1. ↑ For FUTURE, received this output: Unable to negotiate with ::1 port 22: no matching cipher found. Their offer: 3des-cbc
jsedlak
Pass pass
[1]
Pass pass
  1. ↑ Everything that was uncommented ran OK.
jvanek
Pass pass
Pass pass
Pass pass
Warning warn
[1]
  1. ↑ As mentioned by pmikova and mvala - when FUTURE is selected, nearly no https connection is possible to establish with icedtea-web
krouma
Pass pass
Pass pass
[1]
Pass pass
Fail fail
[2]
Fail fail
Pass pass
  1. ↑ Passed even with special symbols and Czech characters
  2. ↑ Test part 3.: Web pages https://3des.badssl.com/ and https://rc4.badssl.com/ were failing for all 3 profiles.
lzachar
Fail fail [1] [2] [3]
[4]
Pass pass
Pass pass
Pass pass
[5]
Pass pass
  1. ↑ RHBZ #1437213
  2. ↑ RHBZ #1437209
  3. ↑ RHBZ #1437363
  4. ↑ 1437363 not yet mentioned on testcase wiki
  5. ↑ with https://koji.fedoraproject.org/koji/taskinfo?taskID=18679218
mvala
Warning warn
[1]
Pass pass
  1. ↑ SSL missing in FUTURE
pkis
Pass pass
Warning warn [1]
[2]
Pass pass
  1. ↑ RHBZ #1437449
  2. ↑ The test pass, but an usability issue was filed: BZ#1437449
pmikova
Warning warn
[1]
  1. ↑ useSystemPropertiesFile=true sudo update-crypto-policies --set FUTURE https://www.elsteronline.de/eportal/KonfigurationsAssistentA.tax?requestaction=KonfigurationsAssistentA.tax - Error performing TLS handshake: The signature algorithm is not supported. java CipherList | wc -l is 25 on FUTURE but java CipherList | wc -l is 36 on DEFAULT diff https://gist.github.com/sparkoo/ef37b8624f922b5c08d084dde23bdad4
pschindl Updated F26
Fail fail [1] [2] [3]
Pass pass
Pass pass
  1. ↑ RHBZ #1437213
  2. ↑ RHBZ #1437209
  3. ↑ RHBZ #1437363
zdenek
Pass pass
[1]
Pass pass
Fail fail
[2]
  1. ↑ Commands were completed without FAIL
  2. ↑ Test part 3.: Web pages https://3des.badssl.com/ and https://rc4.badssl.com/ were failing for all 3 profiles.

User driven[edit]

User Profile FUTURE profile with commonly visited sites Specific apps Own app References
akashche F26 in Docker
Pass pass
Pass pass
[1]
  1. ↑ Tried FUTURE with https://github.com/ojdkbuild/contrib_update-notifier , https://github.com/staticlibs/staticlib_httpserver and https://github.com/staticlibs/staticlib_httpclient
Retrieved from "https://fedoraproject.org/w/index.php?title=Test_Day:2017-03-30_CryptoPolicies&oldid=490589"