Received: from mail-qv1-f48.google.com ([209.85.219.48]:36708) by stodi.digitalkingdom.org with esmtps (TLSv1.3:TLS_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iwkf7-0001f4-QO; Wed, 29 Jan 2020 02:33:35 -0800 Received: by mail-qv1-f48.google.com with SMTP id db9so4152217qvb.3; Wed, 29 Jan 2020 02:33:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=LFKdHHMj7D3wvAPLZ5PH95CXXerNOgGzai8GBwl/fr0=; b=jcjGV+JUV57j8ES+h7ND9J+QAh+Jh1PmTzGl9yxHqe8lkjmF8LqUTy9H5jnhkxO0ov lli+9L4jZLr+um0Z2gv995fUV44RIMkk1JWtCTw5KrmZZFw2S8i6CvNVXSdikWSMgeWA Tnw8MSbIbjIklkqgBlY5thuLoXzFBKuRhA4fzKXIYaCWmYi/1gdsRl/NvkHQJXe7b1s+ 73aK0pRmi/ThtXhg0u4rfGcyMLsbC/GDkgsj2W1gh5H7Q9MtBx2CqJGv6mjO3HP0AilU aCRwooPvVi+C7vYQ0uWUATmIflQ3k2iamhvDIVmZMaVUYMkrslqd5+6kZ4Q8mwDNnARK myEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=LFKdHHMj7D3wvAPLZ5PH95CXXerNOgGzai8GBwl/fr0=; b=Xn0W+U7p2YT1l6v01ipX3FfiNJTORPDMPeECK+4tqmqaIbVva2KajJlZGjPbM8XQHm OKwRHTPPqAcb8J3XouEx8PEXxAKL7bscn1iLAg2qV57f2DFEbOFQ0pcZBuy2Ko2dWRn5 eLhuuIm9u+vC39Wx1gAtwbKPkQEGnPMcJT4usrLUUV+AGauHyoXHJBhi3TWRsPqOWDDh 6IeXhkrm0eALeS/4RCD2ZX310g+QmGHasQxo1hvoSa13hb7fyhSYyF9DdpG61H6Scfg7 H60ZtS5DbGCHT/xvMyNkb7suIIk2fyLRjYFRQ6xg0iB3qJ5ZCGNpz8DExFmWe6sp36Q6 tjfQ== X-Gm-Message-State: APjAAAWBhOed8mCZQ3xrNNV+nK0fyeCUeQt6vwOtwe8FBI2X8i1+88be qkxD1MJCqKIUjzbirvbdGvf7NF4Hzjw= X-Google-Smtp-Source: APXvYqwv1yRN1jR2dSBC6zWPhSKmFCKNySM74kyO4kprBubLhOxd7DiNZyZdl+uS/1s/zyqFKPLXKQ== X-Received: by 2002:a05:6214:13a3:: with SMTP id h3mr27323209qvz.212.1580294006626; Wed, 29 Jan 2020 02:33:26 -0800 (PST) Received: from ?IPv6:2604:2000:14c6:8922:4055:6b52:d53d:656? ([2604:2000:14c6:8922:4055:6b52:d53d:656]) by smtp.gmail.com with ESMTPSA id f11sm724360qkh.96.2020.01.29.02.33.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 29 Jan 2020 02:33:25 -0800 (PST) Content-Type: multipart/alternative; boundary=Apple-Mail-0F9F7ECE-1BC9-49B8-99DD-1E38B9BAFBF5 Content-Transfer-Encoding: 7bit From: Riley Martinez-Lynch Mime-Version: 1.0 (1.0) Subject: Re: Storing secrets for Lojban resources. Date: Wed, 29 Jan 2020 05:33:25 -0500 Message-Id: References: Cc: secretary@lojban.org, president@lojban.org, Robert LeChevalier In-Reply-To: To: Gleki Arxokuna X-Mailer: iPhone Mail (17C54) X-Spam-Score: -2.1 (--) X-Spam_score: -2.1 X-Spam_score_int: -20 X-Spam_bar: -- --Apple-Mail-0F9F7ECE-1BC9-49B8-99DD-1E38B9BAFBF5 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ha! I can confirm Robin's assumptions about secrets keeping. I want to be cl= ear, though: I remain grateful to Robin for all of the organizational work t= hat he has done and continues to do. I just think that given increasing onli= ne security threats, we need to adopt some new secret-keeping and sharing pr= actices. I can't agree with friend Gleki about the use of email for secrets, and woul= d kindly request that we not use email to share or store secrets. I applaud Robin for proposing a solution: I use 1password personally, but ha= ve also used LastPass, and I think we should consider using one of these ser= vices or something similar to create a vault for LLG secrets. There will be a= small monthly charge. Sent from my iPhone > On Jan 29, 2020, at 4:26 AM, Gleki Arxokuna w= rote: >=20 > =EF=BB=BF > I suggest use precisely this email thread for storing secrets. Email might= not be the safest option but it's the most stable message exchange system. >=20 >> On Wed, Jan 29, 2020, 10:07 Robin Lee Powell wrote: >> Hi! I need a place to stick usernames and passwords for Lojbanic >> stuff. >>=20 >> In the past, I've just used a shared Google doc, but I get the >> impression that Riley isn't OK with that, and that's fine. >>=20 >> I personally use LastPass, but I'll use whatever; I just need us to >> agree on *something*, please. >>=20 >> Please add anyone else that you think has or should have an >> interested in the sysadmin side of lojbanistan. --Apple-Mail-0F9F7ECE-1BC9-49B8-99DD-1E38B9BAFBF5 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Ha! I can confirm Robin's assumptions a= bout secrets keeping. I want to be clear, though: I remain grateful to Robin= for all of the organizational work that he has done and continues to do. I j= ust think that given increasing online security threats, we need to adopt so= me new secret-keeping and sharing practices.

I can'= t agree with friend Gleki about the use of email for secrets, and would kind= ly request that we not use email to share or store secrets.

I applaud Robin for proposing a solution: I use 1password personall= y, but have also used LastPass, and I think we should consider using one of t= hese services or something similar to create a vault for LLG secrets. There w= ill be a small monthly charge.

Sent from my iPhone

On Jan 29, 2020, at 4:26 A= M, Gleki Arxokuna <gleki.is.my.name@gmail.com> wrote:

=EF=BB=BF
I suggest use precisely this email thread for storing secrets. Email mig= ht not be the safest option but it's the most stable message exchange system= .

= On Wed, Jan 29, 2020, 10:07 Robin Lee Powell <rlpowell@digitalkingdom.org> wrote:
Hi!  I need a place to stick usernames and pa= sswords for Lojbanic
stuff.

In the past, I've just used a shared Google doc, but I get the
impression that Riley isn't OK with that, and that's fine.

I personally use LastPass, but I'll use whatever; I just need us to
agree on *something*, please.

Please add anyone else that you think has or should have an
interested in the sysadmin side of lojbanistan.
= --Apple-Mail-0F9F7ECE-1BC9-49B8-99DD-1E38B9BAFBF5--