[foodhackingbase] Wiki relaunch

Fri Jan 31 16:11:31 CET 2014

The "problem" with CAcert is that their root certificate is not included
in most mainstream browsers. Therefore most people will see a
certificate warning when accessing your website via HTTPS, which might
scare them away. 

If you're confident that your audience is educated about this (or will
simply ignore the warning) and you absolutely do not want to pay money
to a commercial CA, then CAcert is certainly an option. For example:
https://www.ccc.de/ 

Best regards, 

Alexander 

---
PGP Key: 0xC55A356B | https://dietrich.cx/pgp

On 2014-01-31 15:55, Frantisek Apfelbeck wrote: 

> Thanks Alexander for the prompt response. I wonder if there are other advantages or disadvantages between the CAcert and as you mention "https://www.ssls.com/domain-only.html" except the price. I'm not very experienced on the topic, again others who know more should decide and I/well fhb would cover it. 
> 
> If close to 10 spammers managed to get in within last two days without nearly anyone knowing about the new wiki page than we may get issues once we bring more attention to it, seems to me. I'm personally fine at least for some time to use "direct confirmation" meaning if you want to create account, write to "us" and someone will open or activate the account for you once we find out you are not a spamm bot, should be doable within 24 hours or less. What do you think? At least I would like to have this option as a back up in case the things go bad meaning hundreds of spammers per day signing in ... 
> 
> Sincerely,
> 
> Frantisek Algoldor Apfelbeck 
> 
> biotechnologist&kvasir and hacker 
> 
> http://www.frantisekapfelbeck.org 
> 
> "There is no way to peace, peace is the way." Mohandas Karamchand Gandhi 
> 
> On Friday, January 31, 2014 3:30 PM, Alexander Dietrich <alexander at dietrich.cx> wrote:
> 
> About the Spam: 
> Wow, this must have happened recently. I believe I checked 1 or 2 days ago and there was nothing. Clearly the Spam protection isn't working yet. 
> About the SSL certificate: 
> If you want to go the "just make the warning go away" route, they can acquired much cheaper: https://www.ssls.com/domain-only.html 
> I have an account there and can donate the SSL certificate. 
> Unless you prefer using a CAcert.org certificate. 
> Best regards, 
> Alexander 
> 
> ---
> PGP Key: 0xC55A356B | https://dietrich.cx/pgp
> 
> On 2014-01-31 14:51, Frantisek Apfelbeck wrote: 
> 
>> Hi to all, 
>> I've created an account on the uberspace.de wiki "algoldor" after some struggle with "secret magical ingredient of passion" and code 567 gave me quite some thinking ... :-)
>> 
>> if you (Steffen) or anyone else can give me full admin privileges wit the access to the localsettings.php included great, I hope not to have to use them for a while but well ...
>> 
>> It looks like that there is an agreement on the payment for the hosting with uberspace.de - if so I go forward and pay for that from fhb budget - or rather I would send money by PayPal to someone who can do the bank transfer which info Steffen shared, someone willing? How is it with the certificate? Are the others OK if I cover the cost of CAcert certificate (for 3 years = 39 eu) from fhb budget? If so I can do that, especially if it is PayPal friendly or again send money to someone by PayPal and ask him/her to do it for us.
>> 
>> Now to the wiki few questions. I see the page is up from 24/1. There are 12 active users, three are us, rest spammers, I see 25 pages, 4 are spamm. If this is what we got for a week than not bad but before on our current wiki we were quite fine at the beginning and it got crazy really quickly therefore I wonder if there is a way how be/make sure that this spamm protection works. Or option number two from my point of view is to finish the redirect, payments, certificates bla bla bla go life and see how it goes. If we have few people around keeping an eye on the pages who have admin rights (with the access to the localsettings.php too) than we should be able to make it, what do you think?
>> 
>> Now if I start to create pages at this new wiki at uberspace.de, they will be all there when we finish the redirect right? If I create an event now on the wiki as for example the "subpage" for the synchronous hackathon is there a way how to share them with public now under some "link" which would however be valid even after the "redirecting" from the old wiki to the new one? So we can start to promote using the new wiki already now with the links being valid even after the transfer.
>> 
>> Please let me know how do you see the topics above, in summary: 
>> 
>> - please give me all the admin rights which we need to operate the wiki and the uberspace.de hosting
>> 
>> - who is OK to receive money by PayPal from fhb and do for us bank payment for first year of hosting at uberspace.de for our wiki?
>> 
>> - are you OK if we pay for the CAcert certificate from fhb money, again can we pay by PayPal or who would be OK to receive money from us and do the payment?
>> 
>> - are you happy with the current spamm protection, are you OK to go life if having proper rights to administer the wiki atc.?
>> 
>> - if we create the events/wiki subpages at the uberspace.de now, are they going to be life after we "redirect" to these pages?
>> 
>> - what should be the syntax for "synchronous hackathon on food, beverage and bio hacking on 14,15 and 16th of February" wiki subpage - using the real namespaces etc.in this case probably something like "events" or "global events" as key words or how you call it
>> 
>> Well that should be all for now, tomorrow we will hit Bulgaria and Sofia, I hope to be online for a bit, mostly on Sunday and Monday.
>> 
>> Sincerely from HackLab Belgrade, Serbia,
>> 
>> Frantisek
>> 
>> biotechnologist&kvasir and hacker
>> 
>> http://www.frantisekapfelbeck.org 
>> 
>> "There is no way to peace, peace is the way." Mohandas Karamchand Gandhi 
>> 
>> On Thursday, January 23, 2014 10:44 AM, Alexander Dietrich <alexander at dietrich.cx> wrote:
>> 
>> Very cool, thanks! Signing up worked without a problem, let us know when 
>> you think the anti-spam mechanism is working reliably.
>> 
>> If Frantisek isn't using "foodhackingbase.org" for anything other than 
>> the Wiki, why not use the existing SSL certificate and key? Otherwise 
>> something like "wiki.foodhackingbase.org" would be nice.
>> 
>> For people without CAcert in their browser (yet), you could allow both 
>> HTTP and HTTPS access to the Wiki, but redirect to HTTPS when people try 
>> to access the login page. And maybe put a short note about CAcert on the 
>> main page.
>> 
>> Best regards,
>> Alexander
>> ---
>> PGP Key: 0xC55A356B | https://dietrich.cx/pgp [1]
>> 
>> On 2014-01-23 04:49, Steffen Beyer wrote:
>>> Hello to all,
>>> 
>>> as a newbie I volunteered to help with the wiki, mainly solving the
>>> spam problem. I learned about FHB at the 30C3 - although I did just
>>> grab some tasty snacks, I got interested further while listening to one
>>> of the Sondersendung podcasts afterwards, and I decided to engage. :)
>>> 
>>> Now a fresh MediaWiki is set up at Uberspace¹, temporarily reachable at
>>> 
>>> https://fhb.canis.uberspace.de [2]
>>> 
>>> The server is located in Frankfurt, Germany, at the rh-tec facilities².
>>> 
>>> The suggested hosting fee is 5EUR/month, while the first month is free.
>>> To top up the account, money needs to be transferred to
>>> 
>>> Beneficiary: Jonas Pasche
>>> IBAN: DE35550501200200003978
>>> BIC: MALADE51MNZ (Sparkasse Mainz)
>>> Reference: Uberspace fhb
>>> 
>>> To combat spam, I took the following measures:
>>> 
>>> * require login to edit pages
>>> * require account validation by email
>>> * require Captcha for new user sign up
>>> 
>>> I would suggest to change the foodhackingbase.org DNS now to point to
>>> the new wiki³. The current state was saved and can be restored easily.
>>> My idea is to wait with editing, let's say until Sunday, and see if the
>>> spam injection is still a problem. If it is, I can revert back to the
>>> clean state without any hassle and perform more hardening.
>>> 
>>> The content structure has changed a little bit:
>>> 
>>> Recipes are grouped in the "Recipe" namespace now. Projects and
>>> Associated groups have been converted to categories - they weren't
>>> real namespaces in the old wiki anyway, not set up properly in
>>> LocalSettings. This is documented for editors within the wiki⁴. Of
>>> course, this is not set in stone; let's see how it works out.
>>> 
>>> Image resizing, thumbnails, should work now. Frantisek mentioned a
>>> Flickr extension. Please enlighten me, what is missing in this regard?
>>> 
>>> It would be nice to have one or two volunteers for user support. I.e.
>>> the wiki sends mails to users with a certain sender address, e.g.
>>> account validation. This address is dead currently, but I could set it
>>> up to be forwarded to some nice people, handling feedback.
>>> 
>>> Last point is SSL - the old wiki runs with a CAcert certificate which
>>> produces a warning for most users. A commercial certificate would cost
>>> 39EUR for three years⁵. A compromise could be to run the wiki
>>> unencrypted, using the above URL - and therefore the Uberspace
>>> wildcard certificate - for administration. This would require
>>> disciplined administrators, OTOH. ,)
>>> 
>>> I'm sure, there are some glitches in the new wiki instance. Just play
>>> around and let me know. Good night!
>>> 
>>> Sincerely,
>>> --
>>> Steffen Beyer <steffen at beyer.io>
>>> 
>>> ¹ https://uberspace.de [3]
>>> ² http://www.rh-tec.de [4]
>>> ³ DNS records (foodhackingbase.org, www.foodhackingbase.org):
>>> A -> 95.143.172.226
>>> AAAA -> 2001:1a50:11:0:5f:8f:ace2:11c
>>> ⁴ https://fhb.canis.uberspace.de/wiki/Help:Categories_and_namespaces [5]
>>> ⁵ http://www.psw.net/ssl-zertifikate.cfm [6]
>>> _______________________________________________
>>> foodhackingbase mailing list
>>> foodhackingbase at lists.hackerspaces.org
>>> http://lists.hackerspaces.org/mailman/listinfo/foodhackingbase [7] 
>> 
>> _______________________________________________
>> foodhackingbase mailing list
>> foodhackingbase at lists.hackerspaces.org
>> http://lists.hackerspaces.org/mailman/listinfo/foodhackingbase [7]

Links:
------
[1] https://dietrich.cx/pgp
[2] https://fhb.canis.uberspace.de/
[3] https://uberspace.de/
[4] http://www.rh-tec.de/
[5] https://fhb.canis.uberspace.de/wiki/Help:Categories_and_namespaces
[6] http://www.psw.net/ssl-zertifikate.cfm
[7] http://lists.hackerspaces.org/mailman/listinfo/foodhackingbase
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hackerspaces.org/pipermail/foodhackingbase/attachments/20140131/76cccf03/attachment.html>