Unix Zip Password

1 view
Skip to first unread message

Honorato Winkel

unread,
Aug 3, 2024, 5:29:30 PM8/3/24
to slumdeoliger

So, after installing this packages it works as expected. The Internet's long term memory just brings partial information sometimes. So in order to fight this I am publishing here the correct link how to sync samba passwords with unix passwords, and also my own test.

libpam-smbpass is deprecated. It seems what replaced it is pam_winbindd. You can install the package libpam-winbind to get it. This however, still does not sync samba passwords with your unix passwords.Instead it allows you to authenticated to unix with a Windows Authentication server (AD). You can find info on that here: _up_Samba_as_an_Active_Directory_Domain_Controller

Wanted to comment on previous answer but could not do it for lack of reputation points. Tried to put the full content on this answer but could not as it said that looked like spam. here is the access to the full content on the wayback machine, and following is the brief version of main points:

This will create a Samba user, if it doesn't already exist, and change it's password to the Unix password, whenever the user logs in using SSH or any other service that uses default system (common-auth) authentication.

Caveat: This will not work if the user logs in via SSH or other services without using a password (for example by using public/private key authentication). In this case, PAM won't have the plain-text password, which is needed to create the Samba password.

Notice: When you modify common-password to also require Samba passwords updates, any currently logged in users will not be able to change their password using "passwd" until they re-login, unless they already have an existing Samba account with a password equal to their Unix password.

In addition to inserting existing passwords, pass can also generate new onesusing pass generate. Just provide the password path, and optionally thelength of the password. Pass will then generate a random password, spit it outon screen, and insert the entry to the password-store.

Generating passwords is great, but being a forgetful person, I like to keep additional informationin my pass entries (username, email, website url). This is where pass edit comes in. When called,pass edit will open up the contents of the entry in the default editor. From there, make thechanges, and save.

Lastly, to retrieve stored passwords, call pass with thepassword entry. Optionally, use the -c flag to copy the password(first line if a multi-line entry) to the clipboard instead of spewing it intothe terminal.

On all my computers, I bind the command passmenu to the keys SUPER + SHIFT + P. Whenever Ineed a password, I just hit those three keys, and dmenu pops up so I can search for the password Iwant. After typing in my master passphrase, I can paste the password wherever I need it. Passmenumakes pass much more reasonable to use.

Somewhere around 2014 I found an /etc/passwd file in some dumpsof the BSD 3 source tree, containing passwords of all the old timerssuch as Dennis Ritchie, Ken Thompson, Brian W. Kernighan, Steve Bourneand Bill Joy.

Hi When I setup a new F5, I got anthentication issue. Please see below. After I was required to change password, I created new password, but I got authentication issue. I do not know what is wrong? Anyone can provide suggestion? Thank you

Password management should be simple and follow Unix philosophy. With pass, each password lives inside of a gpg encrypted file whose filename is the title of the website or resource that requires the password. These encrypted files may be organized into meaningful folder hierarchies, copied from computer to computer, and, in general, manipulated using standard command line file management utilities.

You can edit the password store using ordinary unix shell commands alongside the pass command. There are no funky file formats or new paradigms to learn. There is bash completion so that you can simply hit tab to fill in names and commands, as well as completion for zsh and fish available in the completion folder. The very active community has produced many impressive clients and GUIs for other platforms as well as extensions for pass itself.

If the password store is a git repository, since each manipulation creates a git commit, you can synchronize the password store using pass git push and pass git pull, which call git-push or git-pull on the store.

Here, ZX2C4 Password Storage Key is the ID of my GPG key. You can use your standard GPG key or use an alternative one especially for the password store as shown above. Multiple GPG keys can be specified, for using pass in a team setting, and different folders can have different GPG keys, by using -p.

The password store does not impose any particular schema or type of organization of your data, as it is simply a flat text file, which can contain arbitrary data. Though the most common case is storing a single password per entry, some power users find they would like to store more than just their password inside the password store, and additionally store answers to secret questions, website URLs, and other sensitive information or metadata. Since the password store does not impose a scheme of it's own, you can choose your own organization. There are many possibilities.

One approach is to use the multi-line functionality of pass (--multiline or -m in insert), and store the password itself on the first line of the file, and the additional information on subsequent lines. For example, Amazon/bookreader might look like this:

This is the preferred organzational scheme used by the author. The --clip / -c options will only copy the first line of such a file to the clipboard, thereby making it easy to fetch the password for login forms, while retaining additional information in the same file.

Another approach is to use folders, and store each piece of data inside a file in that folder. For example Amazon/bookreader/password would hold bookreader's password inside the Amazon/bookreader directory, and Amazon/bookreader/secretquestion1 would hold a secret question, and Amazon/bookreader/sensitivecode would hold something else related to bookreader's account. And yet another approach might be to store the password in Amazon/bookreader and the additional data in Amazon/bookreader.meta. And even another approach might be use multiline, as outlined above, but put the URL template in the filename instead of inside the file.

The point is, the possibilities here are extremely numerous, and there are many other organizational schemes not mentioned above; you have the freedom of choosing the one that fits your workflow best.

To free password data from the clutches of other (bloated) password managers, various users have come up with different password store organizations that work best for them. Some users have contributed scripts to help import passwords from other programs:

This is a very active project with a healthy dose of contributors. The best way to contribute to the password store is to join the mailing list and send git formatted patches. You may also join the discussion in #pass on Libera.Chat.

How am I supposed to proceed? I'm pretty new to this whole web development thing, so I'm following a tutorial on how to launch an app with Digital Ocean. This isn't how it is supposed to respond, so I'm really lost here.

The password being asked here is your droplet's password and yes it is a Linux distribution, namely Ubuntu. Prompt clearly says that you are required to change the password here. So, when the system asks to provide a password just enter your droplet's current password then for the second time provide the password you want.

The computer will prompt you for your old password, ask for a newpassword, and ask that you repeat your new password for verification.You should choose a password of at least eight characters, two ofwhich must be non-alphabetic characters. Unix is case sensitive, andUITS recommends that you use lowercase characters. This command willchange the password only on the computer you are currently using.

Multitasking refers to an operating system in which multiple processes, also called tasks, can execute (i.e., run) on a single computer seemingly simultaneously and without interfering with each other. Each process has the illusion that it is the only process on the computer and that it has exclusive access to all the services of the operating system.

Because there could be multiple users on the system, it is, therefore, necessary to manage their authentication. Authentication is primarily handled with passwords and public keys. One of the many tools available we use to set up passwords is the passwd command.

The passwd command changes passwords for user accounts. A normal user may only change the password for their own account, while the superuser may change the password for any account. passwd also changes the account or associated password validity period. This task is achieved through calls to the Linux-PAM and libuser API.

The -l option is used to lock the password of a specified account, and it is available to root only. The result is that the user cannot use the password to log in to the system but can use other means such as SSH public key authentication.

This option is used to disable an account after the password has been expired for a number of days. After a user account has had an expired password for INACTIVE days, the user may no longer sign on to the account.

I work as Unix/Linux Administrator with a passion for high availability systems and clusters. I am a student of performance and optimization of systems and DevOps. I have passion for anything IT related and most importantly automation, high availability, and security. More about me

The opinions expressed on this website are those of each author, not of the author's employer or of Red Hat. The content published on this site are community contributions and are for informational purpose only AND ARE NOT, AND ARE NOT INTENDED TO BE, RED HAT DOCUMENTATION, SUPPORT, OR ADVICE.

c80f0f1006
Reply all
Reply to author
Forward
0 new messages