Project

General

Profile

action #49331

coordination #49244: YaST Command Line Options TRACKER

Regression test yast security

Added by vpelcak over 2 years ago. Updated 11 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
2019-03-14
Due date:
% Done:

0%

Estimated time:

Description

Verify ability to:

  • specify the security level of the host
  • set the value of specific options
  • display a summary of the current security configuration

Reference:
https://www.suse.com/documentation/sles-15/singlehtml/book_sle_admin/book_sle_admin.html#id-1.3.3.6.13.6.29

History

#1 Updated by pstivanin over 2 years ago

  • Due date set to 2019-05-10
  • Status changed from New to In Progress
  • Assignee set to pstivanin
  • Start date changed from 2019-03-14 to 2019-04-30
  • Estimated time set to 24.00 h

#2 Updated by pstivanin over 2 years ago

  • Start date changed from 2019-04-30 to 2019-05-02

#3 Updated by pstivanin over 2 years ago

  • % Done changed from 0 to 40
  • Estimated time changed from 24.00 h to 16.00 h

#4 Updated by pstivanin over 2 years ago

  • % Done changed from 40 to 60

#5 Updated by pstivanin over 2 years ago

  • % Done changed from 60 to 80

Code has been implemented, now testing it everywhere

#6 Updated by pstivanin over 2 years ago

  • Target version changed from QAM tests - future to QAM tests - current
  • % Done changed from 80 to 100

#7 Updated by pstivanin over 2 years ago

Changing the security level of the host doesn't work, so I opened a bug for that: https://bugzilla.suse.com/show_bug.cgi?id=1134013

#8 Updated by pstivanin over 2 years ago

YaST2 security is not 'integrated' with passwd, so in order to verify that the 'min passwor' feature works, the 'Users' module should be used.
This could be a thing to keep in mind if we want to increase the test coverage

#9 Updated by pstivanin over 2 years ago

  • Estimated time changed from 16.00 h to 10.00 h

#10 Updated by pstivanin over 2 years ago

  • Status changed from In Progress to Resolved

#11 Updated by vpelcak over 2 years ago

  • Status changed from Resolved to In Progress

Test does something completely different than described in the reference:
https://www.suse.com/documentation/sles-15/singlehtml/book_sle_admin/book_sle_admin.html#id-1.3.3.6.13.6.29

https://progress.opensuse.org/issues/49244 is about yast in cli, not gui.

Testcase is very useful, but doesn't test CLI at all.

#12 Updated by pstivanin over 2 years ago

  • Due date changed from 2019-05-10 to 2019-06-10
  • Start date changed from 2019-05-02 to 2019-05-30
  • % Done changed from 100 to 0
  • Estimated time changed from 10.00 h to 8.00 h

#13 Updated by pstivanin over 2 years ago

@Vit: changing the security level does not work at the moment. See the bug I opened above.
Should we proceed anyway to develop this test?

#14 Updated by pstivanin over 2 years ago

  • Start date set to 2019-03-14

due to changes in a related task

#15 Updated by pstivanin over 2 years ago

  • Due date deleted (2019-06-10)
  • Status changed from In Progress to Workable
  • Assignee deleted (pstivanin)
  • Start date deleted (2019-05-30)
  • Estimated time deleted (8.00 h)

#16 Updated by pstivanin over 2 years ago

Until the aforementioned bug is solved there's not much we can do on our side.
Using the CLI, the only available commands are:

  • level (which does not work)
  • set
  • summary (which displays only "custom settings" due to the bug) There's no "get" command, so even if we developed a test that sets somethings we would have no way to know whether the settings has been correctly applied.

#17 Updated by brhavel almost 2 years ago

  • Subject changed from [qam] Regression test yast security to [qam][maint][yast2-security] - Regression test yast security
  • Status changed from Workable to Feedback

#18 Updated by tjyrinki_suse over 1 year ago

  • Status changed from Feedback to Blocked

The bug is still open.

#19 Updated by tjyrinki_suse 11 months ago

  • Project changed from QAM to qe-yast
  • Target version deleted (QAM tests - current)

#20 Updated by tjyrinki_suse 11 months ago

  • Status changed from Blocked to New

#21 Updated by riafarov 11 months ago

  • Subject changed from [qam][maint][yast2-security] - Regression test yast security to Regression test yast security
  • Target version set to future

Also available in: Atom PDF