Almost every program that we run has access to the environment, so nothing stops them from curling our credentials to some nefarious server.

Why don’t we put credentials in files and then pass them to the programs that need them? Maybe coupled with some mechanism that prevents executables from reading any random file except those approved.

You are viewing a single thread.
View all comments View context
15 points

A proper server should have one user per service.

permalink
report
parent
reply
0 points

yay password rotation month

permalink
report
parent
reply
7 points

Service users generally don’t have passwords

permalink
report
parent
reply
3 points

You don’t login as service users, they’re just a means of taking advantage of the user separation features. They have the login shell set to /bin/false typically.

permalink
report
parent
reply
2 points

Not /bin/nologin/?

permalink
report
parent
reply
1 point

true dat; false trends to CVE vs nologin

permalink
report
parent
reply

Linux

!linux@lemmy.ml

Create post

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

  • Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
  • No misinformation
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

Community stats

  • 7.5K

    Monthly active users

  • 6.6K

    Posts

  • 180K

    Comments