On Mon, Apr 28, 2014 at 3:11 PM, Matthew Senate <mattsenate(a)gmail.com> wrote:
> Can we submit a support ticket with godaddy to remove the lock?
You can try, I doubt it though. The internet seems to be full of
people who have tried and failed. Sorry for my mistake.
On Tue, Apr 29, 2014 at 12:50 AM, Matthew Senate <mattsenate(a)gmail.com> wrote:
> create your own account on the dev.sudoroom.org site using:
>
> user: sudoer
> pass: superuserdoroom
I appreciate all your hard work on this, but I would advocate for a
more security-conscious approach to this. My two concerns are:
1) We should not share a wordpress admin account passwords on a public
mailing list. Admin accounts are able to modify files on the server
and execute arbitrary code. This creates a very easy way for anybody
on the internet to pwn our entire web server and attack our users.
2) We should not serve the dev site on http or encourage users to
create accounts in cleartext. I can move it seamlessly to
https://sudoroom.org/dev/ with your consent.
I think we owe our users better than this, especially since we've
taught some of them to use Tor at our cryptoparties. They have trusted
us with email addresses and passwords in (among other things) the
blog, wiki, and mailman. This puts them and us at risk. It also
nullifies a lot of past time and effort that's gone into keeping our
server secure.
On Mon, Apr 28, 2014 at 2:46 PM, Matthew Senate <mattsenate(a)gmail.com> wrote:
> Given that it was a pain in the butt and took a bunch of time, at the very
> least it may be worth it (in the long term) to use Mozilla Persona to hack ...
>
> Added a wiki page with more details here: https://sudoroom.org/wiki/Persona
Persona's future is uncertain. Mozilla is no longer developing it, and
while they still host the servers, the most they can say is that
decommissioning "will absolutely not happen in 2014." :P
http://identity.mozilla.com/post/78873831485/transitioning-persona-to-commu…
On Mon, Apr 28, 2014 at 2:33 PM, Matthew Senate <mattsenate(a)gmail.com> wrote:
> So for some reason this didn't go all the way through. I'm not sure why.
> Does anyone want to state the next step, or should we start from scratch?
It didn't go through the first time because Jacob's email was the
admin contact in whois, Godaddy sent him a confirmation link, and he
never clicked it.
So I changed the admin contact to be info(a)sudoroom.org and tried again.
Which was a mistake because it apparently triggered a 60-day transfer
lock, so Godaddy won't let us try again until mid-June.
I've been thinking about how we could to encourage app development without
having to increase the administrative costs, especially for user
authentication.
Does anyone have any thoughts or experience with authentication systems
(CAS or otherwise) that they can share?
Specifically, it seems like Mozilla Persona is a really good solution for
us to implement and work towards:
https://en.wikipedia.org/wiki/Mozilla_Persona
A lot of systems already have libraries or support:
https://developer.mozilla.org/en-US/Persona/Libraries_and_plugins
It would be easy to implement using Mozilla.org as the provider, but due to
decentralization of the system, we should be able to point to our own
implemented server instead in the future.
Or perhaps there is a better alternative?
// Matt
On Thu, Mar 27, 2014 at 12:50 PM, Yar <yardenack(a)gmail.com> wrote:
>> They require either a Bitcoin address or a Paypal account.
On Thu, Mar 27, 2014 at 12:52 PM, David Rorex <drorex(a)gmail.com> wrote:
> There's no official sudo paypal account?
Not that I know of. It would be great to make one, but we don't have a
debit card to associate with it yet.
If anybody is willing to help pay for transferring sudoroom.org to a
new registrar, please contact me and I will give you the login
details.
They require either a Bitcoin address or a Paypal account.
I've already set everything up. I can just link you to the invoice and
you can click "pay."
Thanks!
>> Now you see the wiki here: https://sudoroom.org/
On Tue, Mar 4, 2014 at 1:11 AM, Scott Olsen <scott(a)scottolsen.org> wrote:
> Clicking on an event in the calendar causes the calendar iframe (instead
> of the whole page) to load the event link. This happened on Firefox
> 27.0.1 Fedora 20 64-bit. I can send screen shot if you need to see.
Nice catch, thanks! It should work now.