Skip to content

Conversation

fabienOVH
Copy link
Contributor

No description provided.

@fabienOVH fabienOVH self-assigned this Sep 24, 2025
@fabienOVH fabienOVH marked this pull request as ready for review September 24, 2025 13:23
@benchbzh
Copy link
Collaborator

Hi @tcpdumpfbacke could you proceed DE + EN proof please ?

@benchbzh benchbzh self-requested a review September 25, 2025 15:03
Copy link
Collaborator

@tcpdumpfbacke tcpdumpfbacke left a comment

Choose a reason for hiding this comment

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

@fabienOVH May I inquire as to the point of these changes?

  1. The same info is added twice for no real reason.
  2. The proposed changes are not useful and on top of that will not work:
  • Why would there be confusion as to the logged-in user? It it displayed in the command line at all times.
  • Why would this even matter? The guide is for ppl who have lost the PW of a user account on the server and cannot log in. Why would they not know the name of the account they tried to log in with? If you were unsure about the accounts present on the system in general, use "cat /etc/passwd".
  • The command "passwd" sans argument will try to change the PW of the current user. The current user is "root". This is why the guide tells you to use it specifying the username of the account you want to edit. It can be any account.
  • The output of "whoami" will always be "root" at this point because you are within a root shell you have just created. The entire point is to gain elevated rights on the mounted system in order to overwrite the PW of another account. Checking which account is currently active will do nothing.

--> To improve the guide steps, remove all the edits and add the info re: "cat /etc/passwd" to see all user accounts.

@fabienOVH
Copy link
Contributor Author

@fabienOVH May I inquire as to the point of these changes?

1. The same info is added twice for no real reason.

2. The proposed changes are not useful and on top of that will not work:


* Why would there be confusion as to the logged-in user? It it displayed in the command line at all times.

* Why would this even matter? The guide is for ppl who have lost the PW of a user account on the server and cannot log in. Why would they not know the name of the account they tried to log in with? If you were unsure about the accounts present on the system in general, use "cat /etc/passwd".

* The command "passwd" sans argument will try to change the PW of the current user. The current user is "root". This is why the guide tells you to use it specifying the username of the account you want to edit. It can be any account.

* The output of "whoami" will always be "root" at this point because you are within a root shell you have just created. The entire point is to gain elevated rights on the mounted system in order to overwrite the PW of another account. Checking which account is currently active will do nothing.

--> To improve the guide steps, remove all the edits and add the info re: "cat /etc/passwd" to see all user accounts.

Thanks for your feedbacks. I've updated the fr-fr version. Please tell me if it's ok for you.

@Y0Coss Y0Coss merged commit 263291f into develop Oct 2, 2025
@Y0Coss Y0Coss deleted the FB-get-back-access-server branch October 2, 2025 13:16
@Y0Coss
Copy link
Collaborator

Y0Coss commented Oct 2, 2025

Thank you for your contribution @fabienOVH

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.

4 participants