Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop obsolete comment documenting a feature that does not exists #392

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Dzejrou
Copy link

@Dzejrou Dzejrou commented Oct 31, 2023

Problem

While working on bsc#1216518 [*] where the SUSE docs implied the feature described by this comment existed I encountered this comment that confirmed the implication made by the docs. The docs should be hopefully fixed in the future but the existence of this comment is confusing as it implies this (now?) non-existent feature does exist.

[*] Not relevant to the comment itself so I did not mention the bug in the commit.

Solution

Remove the part of the documenting comment that talks about the feature (random number being generated when '!' is used in the AutoYaST profile with the password declared as not encrypted).

Note: I also removed the second sentence referencing to the encrypted attribute. I did this because that attribute affects how the '!' password is interpreted and the reference was immediately after the removed part (rather than after the description of the user_password attribute) so I assumed the reference existed because of the random password feature. If it should remain, let me know and I will amend the commit.

@@ -89,8 +89,7 @@ def self.attributes
# @return [String,nil] Default shell
#
# @!attribute user_password
# @return [String,nil] User's password. If set to an exclamation mark ('!'),
# a random password is generated. See #encrypted.
# @return [String,nil] User's password.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeap, it is not random, but it disables login with password. Quotation from man page for shadow:

If the password field contains some string that is not a valid result of crypt(3), for instance ! or *, the user will not be able to use a unix password to log in (but the
           user may log in the system by other means).

@coveralls
Copy link

Pull Request Test Coverage Report for Build 6712645153

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 60.824%

Totals Coverage Status
Change from base Build 6299574822: 0.0%
Covered Lines: 3394
Relevant Lines: 5580

💛 - Coveralls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants