NOTE: Chris and Torrie were able to decrypt it with their private key's.

In order to avoid extra noise and virtual conflict I have opted to answer
any questions during our meeting. I will be available to answer any
questions during that time. This is equivalent in conditions met to acquire
a Physical Space key.


On Mon, Mar 17, 2014 at 6:10 PM, Torrie Fischer <[email protected]>wrote:

> On Monday, March 17, 2014 17:05:56 Justin Herman wrote:
> > SOME KIND OF BLOB
>
> Ok. Right.
>
> You sent a SSH key signed with a PGP key that I have not verified. The
> signed
> key was encrypted with my public key, meaning that only I could decrypt it.
>
> Justin, are you aware that we are also asking you questions and not just
> asking for an SSH key? I'll copy them again:
>
> VVVV QUESTIONS VVVV
>
> 1.) What is your primary purpose for requesting access to AWS?
> 2.) What problems with the current website and online infrastructure do you
> currently see that require AWS root and sudo access to solve?
> 3.) What improvements can you offer to the overall infrastructure?
> 4.) Are you familiar with Ansible, the configuration-management software
> used
> to configure, deploy and maintain servers? If not, do you intend to learn
> about it?
>
> ^^^^ QUESTIONS ^^^^
>
> In case they kept getting lost in the noise of this thread, I've also
> trimmed
> out the rest of the inline quotes.
>
> There seems to be a pattern of not answering any questions when directly
> asked. Would you prefer that I ask them in private instead of on discuss@?
> I'm
> often at the space, so I can handle either e-mail or in person. I would
> still
> need to relay the answers to a public forum such as noc@ to preserve
> transparency about our site security and keep everyone else up to date with
> who has unlimited and absolute power over synhak.org.
>
> If you're not able to make this work, then I can't really give you access.
_______________________________________________
Discuss mailing list
[email protected]
https://synhak.org/mailman/listinfo/discuss

Reply via email to