The Mailman passwords have nothing to do with AWS credentials. Sure, you could go in and change them out from under everyone if you had AWS sudo access, but that’s so far beyond an emergency issue that I would only do so if I were going to also simultaneously put forth a proposal to ban the person in question from the space.
Mailman credentials can be requested by anyone who wishes to moderate and administer individual lists upon request. I would be more than fine with bringing on more moderators for each list. As the person who primarily moderates each of the lists, reducing my workload in moderating the lists is more than welcome. Also, to address the “subsequent complacency” of the others who had the necessary credentials to end said moderation, let me state the following: I am one of the people with the necessary password to administer ALL of the lists for SYN/HAK. I chose not to disable moderation for a few reasons: First, Torrie had explained that there was an intended end-date of said moderation, and it was, within my opinion, a reasonable timeframe. Additionally, I feel that I have made it pretty clear that I am one of the people that moderates and handles the mailing lists. I have made myself so extraordinarily available and reachable via email, telephone, SMS, carrier pigeon, smoke signals, 20m SSB etc. Not once during the moderation period did I receive a single message directed toward myself, the sysadmin list, the noc list, my personal email, or even via the board list, which I am subscribed to due to being Champion, asking if anyone had the ability to disable said moderation, nor did I get a request from a board member, sysadmin, champion or member to disable said moderation. I took the lack of request to disable the moderation as the community perhaps being upset, but agreeing to allow the moderation to continue until its intended end date. If anyone had any question whatsoever, I certainly was not contacted about it, neither as Champion, nor as Maintainer of Mailman. Regards, Chris Egeland On Mar 12, 2014, at 1:45 AM, a l <[email protected]> wrote: > I'm fairly certain this proposal is in response of the recent unilateral > censorship of discuss@ and perhaps subsequent complacency by those who > currently have the requested privileges. > > Regards, > Andrew L > > On Mar 12, 2014 1:26 AM, "Chris Egeland" <[email protected]> wrote: > Justin, > > In order to help make my decision on how I will vote on this proposal, I > would like to ask a few questions. Also, these questions are posed to Craig > and Alex. > > 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 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? > Optional: 5.) We heavily utilize git and Github as our centralized source for > Ansible plays, playbooks, configuration files, etc. Please demonstrate git > and Github competency by submitting a pull request to add your SSH public key > to the appropriate repository. I will accept said pull request upon the > passage of this proposal. > > Regards, > Chris > > On Mar 12, 2014, at 12:12 AM, Justin Herman <[email protected]> wrote: > > > SynHak.org is a community resource available to all, members seeking access > > can be trusted as long as they are members in good standing. Just as keys > > to the space are granted to members in good standing, keys to our "virtual > > space" should be granted as well. > > > > I propose power user access with sudo/admin access to AWS and all SynHak > > infrastructure, be granted to the following members... > > > > Craig Bergdorf > > Justin Herman > > Alex Kot > > > > These members in good standing and wish to support and improve the > > infrastructure of SynHak.org and ancillary services. In addition each has > > experience in the information security field. > > > > Access to static and new usernames and passwords will be shared, within 5 > > days of the proposal's passage, to the members listed above. > > > > > > > > Justin > > > > _______________________________________________ > > Discuss mailing list > > [email protected] > > https://synhak.org/mailman/listinfo/discuss > > _______________________________________________ > Discuss mailing list > [email protected] > https://synhak.org/mailman/listinfo/discuss > _______________________________________________ > Discuss mailing list > [email protected] > https://synhak.org/mailman/listinfo/discuss
_______________________________________________ Discuss mailing list [email protected] https://synhak.org/mailman/listinfo/discuss
