diff options
Diffstat (limited to 'zarb-ml/mageia-sysadm/2011-February/002784.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2011-February/002784.html | 213 |
1 files changed, 213 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2011-February/002784.html b/zarb-ml/mageia-sysadm/2011-February/002784.html new file mode 100644 index 000000000..58401c9f2 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-February/002784.html @@ -0,0 +1,213 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] Saving and sharing passwords in mageia teams + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Saving%20and%20sharing%20passwords%20in%20mageia%20teams&In-Reply-To=%3C20110219012654.GR21938%40mars-attacks.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002783.html"> + <LINK REL="Next" HREF="002785.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] Saving and sharing passwords in mageia teams</H1> + <B>nicolas vigier</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Saving%20and%20sharing%20passwords%20in%20mageia%20teams&In-Reply-To=%3C20110219012654.GR21938%40mars-attacks.org%3E" + TITLE="[Mageia-sysadm] Saving and sharing passwords in mageia teams">boklm at mars-attacks.org + </A><BR> + <I>Sat Feb 19 02:26:54 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002783.html">[Mageia-sysadm] Automated Reply Re: "Re: Saving and sharing passwords in mageia teams" +</A></li> + <LI>Next message: <A HREF="002785.html">[Mageia-sysadm] Automated Reply Re: "Re: Saving and sharing passwords in mageia teams" +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2784">[ date ]</a> + <a href="thread.html#2784">[ thread ]</a> + <a href="subject.html#2784">[ subject ]</a> + <a href="author.html#2784">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, 19 Feb 2011, Buchan Milne wrote: + +><i> On Friday, 18 February 2011 23:45:02 nicolas vigier wrote: +</I>><i> > Hello, +</I>><i> > +</I>><i> > We often need to register some accounts on various websites for the +</I>><i> > Mageia project (domain name registration, twitter, identica, etc ...). +</I>><i> > And we need to be able to share the account informations (login and +</I>><i> > password) with other people inside teams. So we need something like a +</I>><i> > password database, with permissions to restrict access to only some +</I>><i> > people or groups of people. We can store this database on Mageia servers, +</I>><i> > but I think it should be encrypted, so that root access on the server +</I>><i> > does not give access to the passwords. +</I>><i> +</I>><i> This is not an uncommon requirement, in my work environment we need to be able +</I>><i> to share the local root passwords (e.g. in case a system administrator needs +</I>><i> to be able to restore something that prevents user logins from working). +</I>><i> +</I>><i> However, in work environments, access to privileged passwords may need to be +</I>><i> auditable. +</I> +This tool could probably be used also outside Mageia. + +><i> +</I>><i> > I have looked at existing tools, but didn't find one that would allow +</I>><i> > us to do this easily. So I'm thinking about writting some scripts to do +</I>><i> > it. It would work like this : +</I>><i> > +</I>><i> > - all users first need to upload their gnupg public key in ldap +</I>><i> +</I>><i> I was already considering the requirement for GPG public keys in LDAP for +</I>><i> 'privileged user password recovery'. E.g., use the same process as +</I>><i> unprivileged users, but encrypt the key sent to the user with their gpg public +</I>><i> key (providing a second level of authentication - if we consider access to the +</I>><i> mailbox one level). +</I> +Good idea ! + +><i> I believe there may also an LDAP-based keyserver, which could provide even +</I>><i> more re-use. +</I> +A keyserver using LDAP would be nice. If not too difficult to setup. + +><i> +</I>><i> > - we have a command to create a password on the server, with a list +</I>><i> > of groups/users who can access this password : +</I>><i> > $ mgapassword create passwdname %group1 %group2 user1 user2 ... +</I>><i> +</I>><i> Should we leverage existing (e.g. LDAP) groups? +</I> +Yes, I think we should use ldap groups. + +><i> > - a command to save the value of a password : +</I>><i> > $ mgapassword set passwdname < value +</I>><i> > or +</I>><i> > $ mgapassword edit passwdname +</I>><i> > - an other command to retrieve a password : +</I>><i> > $ mgapassword get passwdname +</I>><i> > - a command to list the passwords you can access : +</I>><i> > $ mgapassword list +</I>><i> > +</I>><i> > All commands connect to the server using ssh and the ldap account. When +</I>><i> > saving a password, the client ask to the server the list of gpg keys of +</I>><i> > all users who should have access to the password, then encrypt the +</I>><i> > password with all keys and send it encrypted to the server. +</I>><i> +</I>><i> Where are the passwords stored? +</I> +Stored on the server in encrypted files. Maybe in a database. + +><i> > The command to retrieve a password connect to the server, then the server +</I>><i> > sends the password encrypted for the key of the user, which is decrypted +</I>><i> > locally using the private gpg key of the user. +</I>><i> > +</I>><i> > When new users are added into a group, they cannot access passwords +</I>><i> > immediatly (as it is not encrypted for their keys), so someone needs to +</I>><i> > retrieve and save the passwords, to encrypt them for the new users. +</I>><i> +</I>><i> This general approach was what I was considering for our work environment. +</I>><i> +</I>><i> > So, what do you think about this ? Or maybe someone knows existing tools +</I>><i> > that can do this ? +</I>><i> +</I>><i> I have not seen any I liked. +</I>><i> +</I>><i> Our work environment has a basic inventory database (the primary use was to +</I>><i> generate kickstart files), the web front end is in ... Catalyst (and possibly +</I>><i> try and implement a more complete CMDB). My plan was to integrate the CatDap +</I>><i> features into this (using CatalystX::Features maybe). Adding a shared password +</I>><i> module that could be tied into CatDap and our work webapp would also be +</I>><i> interesting to me. +</I>><i> +</I>><i> But, for now, a command-line tool would be adequate. +</I>><i> +</I>><i> I will look at the LDAP side (schema, ACLs, suoport for adding GPG public key +</I>><i> from CatDap) over the weekend. +</I> +Thanks. + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002783.html">[Mageia-sysadm] Automated Reply Re: "Re: Saving and sharing passwords in mageia teams" +</A></li> + <LI>Next message: <A HREF="002785.html">[Mageia-sysadm] Automated Reply Re: "Re: Saving and sharing passwords in mageia teams" +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2784">[ date ]</a> + <a href="thread.html#2784">[ thread ]</a> + <a href="subject.html#2784">[ subject ]</a> + <a href="author.html#2784">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |