summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-sysadm/attachments/20130215/4aabd80e/attachment-0001.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-sysadm/attachments/20130215/4aabd80e/attachment-0001.html')
-rw-r--r--zarb-ml/mageia-sysadm/attachments/20130215/4aabd80e/attachment-0001.html49
1 files changed, 49 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/attachments/20130215/4aabd80e/attachment-0001.html b/zarb-ml/mageia-sysadm/attachments/20130215/4aabd80e/attachment-0001.html
new file mode 100644
index 000000000..60d8d60d8
--- /dev/null
+++ b/zarb-ml/mageia-sysadm/attachments/20130215/4aabd80e/attachment-0001.html
@@ -0,0 +1,49 @@
+<br><br><div class="gmail_quote">On Fri, Feb 15, 2013 at 3:33 PM, nicolas vigier <span dir="ltr">&lt;<a href="mailto:boklm@mars-attacks.org" target="_blank">boklm@mars-attacks.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+
+<div class="im">On Fri, 15 Feb 2013, Pascal Terjan wrote:<br>
+<br>
+&gt; On Fri, Feb 15, 2013 at 11:52 AM, nicolas vigier &lt;<a href="mailto:boklm@mars-attacks.org">boklm@mars-attacks.org</a>&gt;wrote:<br>
+&gt;<br>
+&gt; &gt; On Fri, 15 Feb 2013, Pascal Terjan wrote:<br>
+&gt; &gt;<br>
+&gt; &gt; &gt; On Fri, Feb 15, 2013 at 11:24 AM, nicolas vigier &lt;<a href="mailto:boklm@mars-attacks.org">boklm@mars-attacks.org</a><br>
+&gt; &gt; &gt;wrote:<br>
+&gt; &gt; &gt;<br>
+&gt; &gt; &gt; &gt; On Fri, 15 Feb 2013, Romain d&#39;Alverny wrote:<br>
+&gt; &gt; &gt; &gt;<br>
+&gt; &gt; &gt; &gt; &gt; Is there a tool/place (or plan to have it) to store and share account<br>
+&gt; &gt; &gt; &gt; &gt; data to various services (blogs, twitter, flickr, hosting services,<br>
+&gt; &gt; &gt; &gt; &gt; etc.)?<br>
+&gt; &gt; &gt; &gt; &gt;<br>
+&gt; &gt; &gt; &gt; &gt; A restricted wiki, or something that could handle groups?<br>
+&gt; &gt; &gt; &gt;<br>
+&gt; &gt; &gt; &gt; Not yet. But we could store on svn a file containing passwords,<br>
+&gt; &gt; encrypted<br>
+&gt; &gt; &gt; &gt; with gpg. Each team can create a gpg key and share it between all team<br>
+&gt; &gt; &gt; &gt; members, and encrypt the passwords file with this key.<br>
+&gt; &gt; &gt; &gt;<br>
+&gt; &gt; &gt; &gt; I&#39;m sure a better sstem has to exist, where you can revoke acces for<br>
+&gt; &gt; &gt; example :)<br>
+&gt; &gt;<br>
+&gt; &gt; Do you know one ?<br>
+&gt;<br>
+&gt;<br>
+&gt; No but we can try to find one :)<br>
+<br>
+</div>I tried to find one before, but didn&#39;t find something good. I was<br>
+thinking about making some scripts for that, but it&#39;s not high priority.<br>
+So using something simple like a shared gpg key would maybe be enough<br>
+for now.<br>
+<div class="im"><br>
+&gt; Actually if the svn repository is not readable by people not in a given<br>
+&gt; group that allows revoking access even if they still have a copy of the<br>
+&gt; master key, but still in security/cryptography world I don&#39;t like<br>
+&gt; reinventing things :)<br>
+<br>
+</div>Maybe some systems allow to revoke access, but nothing prevent that<br>
+person from keeping a copy of all passwords before his access is<br>
+revoked. So only reliable way to revoke access is to change all<br>
+passwords.<br></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+If using a shared gpg key, to revoke access for someone we need to start<br>
+using a new key and change all passwords. That&#39;s not very convenient,<br>
+but hopefully we don&#39;t need to do that often.</blockquote><div><br></div><div>Yes my problem was with the need to change the key when someone leaves the team</div></div>