Skip to content

Rewrite the pam.md file#3236

Closed
jimcat8 wants to merge 3 commits intorocky-linux:mainfrom
jimcat8:append
Closed

Rewrite the pam.md file#3236
jimcat8 wants to merge 3 commits intorocky-linux:mainfrom
jimcat8:append

Conversation

@jimcat8
Copy link
Copy Markdown
Contributor

@jimcat8 jimcat8 commented Mar 28, 2026

Author checklist (Completed by original Author)

  • Good fit for the Rocky Linux project? Title and Author Metatags inserted ?
  • If applicable, steps and instructions have been tested to work
  • Initial self-review to fix basic typos and grammar completed

Rocky Documentation checklist (Completed by Rocky team)

  • 1st Pass (Document is good fit for project and author checklist completed)
  • 2nd Pass (Technical Review - check for technical correctness)
  • 3rd Pass (Detailed Editorial Review and Peer Review)
  • Final approval (Final Review)

@jimcat8 jimcat8 changed the title Expand the content of PAM documents Rewrite the pam.md file Mar 31, 2026
@github-actions
Copy link
Copy Markdown

Test results for 6f89fca:

Number of broken URLs: 17

URL,RESULT,FILENAME
 https://repocompare.rockylinux.org,failed,release_notes/8_5.md
 https://mirrors.fedoraproject.org/metalink?repo=epel-8&arch=$basearch&infra=$infra&content=$contentdir,failed,books/admin_guide/13-softwares.md
 https://coding.tools/regex-tester,failed,books/sed_awk_grep/1_regular_expressions_vs_wildcards.md
 https://ftp.gnu.org/gnu/hello/hello-2.12.tar.gz,failed,labs/systems_administration_I/lab7-software_management.md
 https://support.torproject.org/glossary/pluggable-transports/,failed,guides/proxies/tor_relay.md
 https://wiki.rockylinux.org/team/release_engineering/debranding/,failed,guides/package_management/package_debranding.md
 http://$(hostname):8080,failed,guides/repositories/pulp_fetch_upload.md
 https://IP:11443/,failed,guides/network/unifi_os.md
 https://git.launchpad.net/cloud-init,failed,guides/virtualization/cloud-init/07_contributing.md
 https://ftp.gnu.org/gnu/tar/,failed,guides/backup/tar.md
 https://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/ipmi-second-gen-interface-spec-v2-rev1-1.pdf,failed,guides/hardware/ipmi_management.md
 https://www.packer.io/docs/builders/vsphere/vsphere-iso,failed,guides/automation/templates-automation-packer-vsphere.md
 https://andyscott.me,failed,guides/contribute/README.md
 https://docs.rockylinux.org/guides/contribute/ai-contribution-policy.md,failed,guides/contribute/README.md
 http://your_ip,failed,guides/cms/mediawiki.md
 https://dl.rockylinux.org/pub/rocky/9.6/live/x86_64/,failed,guides/desktop/kde_installation.md
 https://forums.developer.nvidia.com/t/unix-graphics-feature-deprecation-schedule/60588,failed,desktop/display/installing_nvidia_gpu_drivers.md

@jimcat8 jimcat8 marked this pull request as ready for review March 31, 2026 13:41

This document is *not* designed to teach you exactly how to harden your machine. It is more of a reference guide to show you what PAM *can* do, and not what you *should* do.
**Q: Why is it necessary to use PAM?**

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@jimcat8 I'm not sure about this: If you are asking a Question (line 35) and then giving the "answers" as more questions (lines 37-39), shouldn't they instead be "answers" and not more questions? For example, line 37 could/should be: "To ensure that the users of the applications, services, or tools used in the system, are always themselves." In general, I don't see anything else in the document rewrite that is bothersome. Let me know your justification for this.

@alemorvan
Copy link
Copy Markdown
Contributor

Hello
Since I am the author of this document, I would appreciate it if you, @jimcat8, would respect my decision not to add “bash >” as a command prompt elsewhere, as I have asked you to do before.
Please ensure consistency throughout my documents.

@alemorvan
Copy link
Copy Markdown
Contributor

Also I see you decided to remove that warning:

A misconfigured instance of PAM can compromise the security of your whole system. If PAM is vulnerable, then the whole system is vulnerable. Make any changes with care.

One again, you decided to remove some things very important and to add too much complexity to that doc.

@alemorvan
Copy link
Copy Markdown
Contributor

Why did you remove the "directive" definition:

A **directive** (a complete line) is composed of a **mechanism** (`auth`, `account`, `password` or `session`), a **success check** (`include`, `optional`, `required`, ...), the **path to the module** and possibly **arguments** (like `revoke` for example).

@alemorvan
Copy link
Copy Markdown
Contributor

Hello @sspencerwire
I disagree with that PR.
We are losing many important information and also we are losing the original style.

@alemorvan
Copy link
Copy Markdown
Contributor

You also removed the chapter that describe some usefull pam modules.
That is not understandable.

@jimcat8
Copy link
Copy Markdown
Contributor Author

jimcat8 commented Mar 31, 2026

Hello
Since I am the author of this document, I would appreciate it if you, @jimcat8, would respect my decision not to add “bash >” as a command prompt elsewhere, as I have asked you to do before.
Please ensure consistency throughout my documents.

Ok

@jimcat8
Copy link
Copy Markdown
Contributor Author

jimcat8 commented Mar 31, 2026

Also I see you decided to remove that warning:

A misconfigured instance of PAM can compromise the security of your whole system. If PAM is vulnerable, then the whole system is vulnerable. Make any changes with care.

One again, you decided to remove some things very important and to add too much complexity to that doc.

There is an explanation at the end of the document

@jimcat8
Copy link
Copy Markdown
Contributor Author

jimcat8 commented Mar 31, 2026

Why did you remove the "directive" definition:

A **directive** (a complete line) is composed of a **mechanism** (`auth`, `account`, `password` or `session`), a **success check** (`include`, `optional`, `required`, ...), the **path to the module** and possibly **arguments** (like `revoke` for example).

I will re-add this section.

@jimcat8
Copy link
Copy Markdown
Contributor Author

jimcat8 commented Mar 31, 2026

You also removed the chapter that describe some usefull pam modules.
That is not understandable.

The original document is missing some manual content and basic concepts. Some modules are no longer in use.

@alemorvan
Copy link
Copy Markdown
Contributor

Improving documentation is one thing. Replacing 100% of the content with your own is quite another.
You’re being disrespectful of my work.

@jimcat8
Copy link
Copy Markdown
Contributor Author

jimcat8 commented Mar 31, 2026

Improving documentation is one thing. Replacing 100% of the content with your own is quite another.
You’re being disrespectful of my work.

The author is still you. Since the document is missing too much information, I need to rewrite it.

@jimcat8
Copy link
Copy Markdown
Contributor Author

jimcat8 commented Mar 31, 2026

Improving documentation is one thing. Replacing 100% of the content with your own is quite another.
You’re being disrespectful of my work.

If the author does not agree to the changes, I will, of course, respect your decision.

@jimcat8 jimcat8 closed this Mar 31, 2026
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.

3 participants