April 2018 - Admin - Freifunk Nordwest

Let's Encrypt certificate expiration notice for domain "matrix.ffnw.de" (and 1 more)

by Let's Encrypt Expiry Bot

Hello, Your certificate (or certificates) for the names listed below will expire in 1 days (on 30 Apr 18 19:30 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors. matrix.ffnw.de riot.ffnw.de For any questions or support, please visit https://community.letsencrypt.org/. Unfortunately, we can't provide support by email. For details about when we send these emails, please visit https://letsencrypt.org/docs/expiration-emails/. In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message. If you want to stop receiving all email from this address, click http://mandrillapp.com/track/unsub.php?u=30850198&id=f1990fc330554f8982a8f1… (Warning: this is a one-click action that cannot be undone) Regards, The Let's Encrypt Team

5 years, 5 months

1
0
0 0

Let's Encrypt certificate expiration notice for domain "api.netmon.ffnw.de" (and 13 more)

by Let's Encrypt Expiry Bot

Hello, Your certificate (or certificates) for the names listed below will expire in 1 days (on 30 Apr 18 17:08 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors. api.netmon.ffnw.de blog.nordwest.freifunk.net dns.ffnw.de ffnw.de hoodgen.ffnw.de matrix.ffnw.de matter.ffnw.de mitglied.ffnw.de mitglieder.ffnw.de nordwest.freifunk.net spenden.ffnw.de webmail.ffnw.de wiki.ffnw.de wiki.nordwest.freifunk.net For any questions or support, please visit https://community.letsencrypt.org/. Unfortunately, we can't provide support by email. For details about when we send these emails, please visit https://letsencrypt.org/docs/expiration-emails/. In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message. If you want to stop receiving all email from this address, click http://mandrillapp.com/track/unsub.php?u=30850198&id=6b056f821f804336b09d95… (Warning: this is a one-click action that cannot be undone) Regards, The Let's Encrypt Team

5 years, 5 months

1
0
0 0

Mailinglistfehler?

by Malte Modler

Hi, ich weiß nicht was da los ist, aber da ist scheinbar was kaputt, kann mal jemand nachsehen? Fehlerbild: siehe Anhang https://lists.ffnw.de/postorius/lists/nordwest.lists.ffnw.de/

5 years, 5 months

3
2
0 0

Let's Encrypt certificate expiration notice for domain "cloud.ffnw.de" (and 3 more)

by Let's Encrypt Expiry Bot

Hello, Your certificate (or certificates) for the names listed below will expire in 10 days (on 03 May 18 18:23 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors. cloud.ffnw.de dev.ffnw.de firmware.ffnw.de office.ffnw.de For any questions or support, please visit https://community.letsencrypt.org/. Unfortunately, we can't provide support by email. For details about when we send these emails, please visit https://letsencrypt.org/docs/expiration-emails/. In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message. If you want to stop receiving all email from this address, click http://mandrillapp.com/track/unsub.php?u=30850198&id=0e5ae2d8442844c7b0b8a1… (Warning: this is a one-click action that cannot be undone) Regards, The Let's Encrypt Team

5 years, 5 months

1
0
0 0

Let's Encrypt certificate expiration notice for domain "netmon.ffnw.de"

by Let's Encrypt Expiry Bot

Hello, Your certificate (or certificates) for the names listed below will expire in 10 days (on 03 May 18 10:29 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors. netmon.ffnw.de For any questions or support, please visit https://community.letsencrypt.org/. Unfortunately, we can't provide support by email. For details about when we send these emails, please visit https://letsencrypt.org/docs/expiration-emails/. In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message. If you want to stop receiving all email from this address, click http://mandrillapp.com/track/unsub.php?u=30850198&id=3b3d55fb9f2c4b3892c2da… (Warning: this is a one-click action that cannot be undone) Regards, The Let's Encrypt Team

5 years, 5 months

1
0
0 0

Let's Encrypt certificate expiration notice for domain "matrix.ffnw.de" (and 1 more)

by Let's Encrypt Expiry Bot

Hello, Your certificate (or certificates) for the names listed below will expire in 10 days (on 30 Apr 18 19:30 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors. matrix.ffnw.de riot.ffnw.de For any questions or support, please visit https://community.letsencrypt.org/. Unfortunately, we can't provide support by email. For details about when we send these emails, please visit https://letsencrypt.org/docs/expiration-emails/. In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message. If you want to stop receiving all email from this address, click http://mandrillapp.com/track/unsub.php?u=30850198&id=822f54f8a52a41fb870e0f… (Warning: this is a one-click action that cannot be undone) Regards, The Let's Encrypt Team

5 years, 5 months

1
0
0 0

Let's Encrypt certificate expiration notice for domain "api.netmon.ffnw.de" (and 13 more)

by Let's Encrypt Expiry Bot

Hello, Your certificate (or certificates) for the names listed below will expire in 10 days (on 30 Apr 18 17:08 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors. api.netmon.ffnw.de blog.nordwest.freifunk.net dns.ffnw.de ffnw.de hoodgen.ffnw.de matrix.ffnw.de matter.ffnw.de mitglied.ffnw.de mitglieder.ffnw.de nordwest.freifunk.net spenden.ffnw.de webmail.ffnw.de wiki.ffnw.de wiki.nordwest.freifunk.net For any questions or support, please visit https://community.letsencrypt.org/. Unfortunately, we can't provide support by email. For details about when we send these emails, please visit https://letsencrypt.org/docs/expiration-emails/. In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message. If you want to stop receiving all email from this address, click http://mandrillapp.com/track/unsub.php?u=30850198&id=6a1ed8b36daf4e38bdbf14… (Warning: this is a one-click action that cannot be undone) Regards, The Let's Encrypt Team

5 years, 5 months

1
0
0 0

Facebook and the Blustery Week | EFFector 31.6

by EFFector List

_______ _______ _______ (_______)(_______)(_______) _ _____ _____ _____ _____ ____ _| |_ ___ ____ | ___) | ___) | ___)| ___ | / ___)(_ _)/ _ \ / ___) | |_____ | | | | | ____|( (___ | |_| |_| || | |_______)|_| |_| |_____) \____) \__)\___/ |_| EFFector Vol. 31, No. 6 Wednesday, April 18, 2018 editor(a)eff.org A Publication of the Electronic Frontier Foundation ISSN 1062-9424 effector: n, Computer Sci. A device for producing a desired change. : . : . : . : . : . : . : . : . : . : . : . : . : . : . : In our 733rd issue: * Read more: * We Watched The Zuckerberg Hearings So You Don't Have To In most issues of EFFector, we give an overview of all the work we're doing at EFF right now. This week, we present a deep dive on the recent Facebook data revelations and Mark Zuckerberg's testimony before Congress. As the nation searched for answers in the wake of Facebook's Cambridge Analytica scandal, Mark Zuckerberg testified last week before a joint session of the Senate Judiciary and Commerce Committees as well as the House Energy and Commerce Committee. While many users' suspicions were affirmed, many important questions went unasked, unanswered, or deflected. Can users trust tech companies to handle their personal information? Can a surveillance-based, advertising-powered platform provide real user privacy protections? If not, how should users, legislators, and the company itself respond? These have long been important questions for users and platforms to explore. This particular scandal with Facebook and Cambridge Analytica was unique only in that it combined sweeping data collection, indiscriminate sharing, lax safeguards, and manipulative advertising into the perfect privacy storm. Several years ago, Facebook's Graph API allowed a researcher to engage in voracious collection of millions of people's data without anything resembling informed consent. Then Facebook failed to step in as Cambridge Analytica subjected that user data to privacy-invasive machine learning techniques for targeted advertising purposes. Perhaps worst of all, Facebook never notified users of a known bad actor's unauthorized access to their data. A Pivotal Time for Online Privacy When a former Cambridge Analytica employee came forward to the press last month, it broke the dam on over a decade of Facebook privacy concerns. This Cambridge Analytica fiasco and subsequent fallout serve as a reminder of the serious privacy risks that users face when their personal information is captured, analyzed, indefinitely stored, and shared by a constellation of data brokers, marketers, and social media companies. Facebook has responded with a stream of statements and changes, from reorganizing privacy settings to locking down APIs to ending relationships with third-party data brokers. But none of these changes have addressed the problem at the core of not only Facebook's but much of the popular web's privacy problems: We can’t be full participants in 21st-century social and political discourse without providing advertisers and others a constant stream of our most intimate personal details. You shouldn't have to be a settings wizard in order to enjoy a popular platform in a safe, private way. Platforms should protect your privacy by default and by design, collecting information only with your affirmative, informed consent. You should have meaningful control over your information and your experience. And, if you decide that a particular platform isn't doing a good enough job protecting the data you’ve entrusted it with, you should be able to leave and take all your information with you. These are just a few of the privacy rights that any responsible social media platform should provide for its users. Word Games In Congress Unfortunately, Mark Zuckerberg's testimony in front of Congress gave us little confidence that the company is committed to providing the transparency and accountability at the foundation of those privacy rights. Instead, the hearings were full of technically accurate but deceptively incomplete word games, as well as hand-waving about AI, confusion about the roles of platforms and ISPs, and shocking inaccuracies about Section 230. Zuckerberg was unable to provide even ballpark answers about the scale at which Facebook tracks users and non-users across the web, and promised that his team would follow up at a later date a whopping 40 times. With the hearings over, the question remains: What next? Above all, the guiding question should not be: What legislation do we need to make sure there is never another Cambridge Analytica? Rather, we should be asking: What privacy protections are missing, and how can we fill that gap while respecting other essential values like speech, user empowerment, and competition? What Comes Next A knee-jerk urge to slap rules on Facebook risks enshrining it as the sole guardian of our discourse and data, with the quasi-authoritarian power to police speech and squash rivals. It's important to consider how any reactions to the Cambridge Analytica scandal, legislative or otherwise, might help or hinder potential future competitors. While Facebook has the vast resources to comply with whatever requirements Congress throws at it, smaller start-ups may not. Facebook's surveillance business model and data-hungry design have created real problems for its users' privacy rights. But some of those problems can be fixed. Going forward, we can look for answers in existing laws, pressure from users and investors, and focused legislative steps where necessary. We need to be both creative and judicious to ensure that today's solutions don’t become tomorrow’s unexpected problems. Read more: https://www.eff.org/deeplinks/2018/04/facebook-not-what-complete-user-contr… : . : . : . : . : . : . : . : . : . : . : . : . : . : . : miniLinks ~ Facebook's Week of shame: the Cambridge Analytica Fallout How the dam broke. (The Guardian) https://www.theguardian.com/technology/2018/mar/24/facebook-week-of-shame-d… ~ A Short History of Facebook's Privacy Gaffes The recent scandal may result in significant reimagining of how we share our information online, and what responsibility platforms have to protect their users' information. But, it's certainly not the first time users have questioned their trust in Facebook. (Wired) https://www.wired.com/story/facebook-a-history-of-mark-zuckerberg-apologizi… ~ The Facebook Privacy Setting That Doesn't Do Anything at All It shouldn't be entirely surprising that users struggled to understand how each privacy setting worked. At times, so did Facebook. (Wired) https://www.wired.com/story/facebook-privacy-setting-doesnt-do-anything/ ~ The Giant List of Shit Mark Zuckerberg Swears He'll Get Back to Congress on Mark Zuckerberg did face some important questions during the congressional hearings. We're still waiting for answers on many of them. (Gizmodo) https://gizmodo.com/the-giant-list-of-shit-mark-zuckerberg-swears-hell-get-… : . : . : . : . : . : . : . : . : . : . : . : . : . : . : Announcements * EFF's 2nd Annual Tech Trivia Night in San Francisco, CA Join us from 6 pm to 11 pm on April 26, for our second annual exploration of the fascinating, obscure, and trivial minutiae of digital security, online rights, and Internet culture. It's the ultimate technology quiz crafted by EFF experts and hosted by our very own Cooper Quintin. EFF's Tech Trivia Night is a great opportunity to gather with peers in the tech community AND support the crucial fight for online civil liberties. Spaces are limited, so act fast and register now! https://www.eff.org/event/effs-2nd-annual-tech-trivia-night * The Facebook Fiasco: What does it mean and what do we do? The personal information of 87-million Facebook users was collected by a consulting firm called Cambridge Analytica. How dangerous is this? What do we do about it? These are the questions many activists are now asking themselves. We want to talk about some answers in this latest Need to Know webinar from May First/People Link and the Progressive Technology Project on Thursday, April 19, at 12 pm PT / 2 pm CT / 3 pm ET. https://mayfirst.org/en/post/2018/content-need-know-facebook-threat-and-opp… * Community Meeting About Surveillance in St. Louis, MO On Wednesday, August 23, from 7 pm to 9 pm, join EFA ally Privacy Watch STL for a community meeting regarding Board Bill 66 and surveillance in St. Louis. We'll have a discussion regarding surveillance technology, how this technology affects St. Louis, and how you can take action. https://www.eff.org/event/community-meeting-surveillance * 20 Years of DMCA Shenanigans discussion hosted by README @ UCLA in Los Angeles, CA A law intended to stop people from making off-brand DVD players now means that security researchers can't warn you about dangers from the cameras in your bedroom; that mechanics can't fix your car; and that your printer won't take third-party ink. Every three years, the US Copyright Office holds hearings about proposed exceptions to this law. This is one of those years. On April 24, at 6 pm, come and hear about what we showed and told the Copyright Office, and ask us questions about your freedom and the funny thing that happened to us all on the way to the twenty-first century. https://www.eff.org/event/20-years-dmca-shenanigans * Representation in the Age of Digital Consciousness Join EFA ally EYEBEAM, at 6:30 pm ET on April 24, as they livestream a discussion about embodied artificial intelligence (androids) as representation, community generated storytellers, and the animated transmitters of culture. https://www.eff.org/event/eyebeam-assembly-representation-age-digital-consc… * Stanford Law Cybersecurity Symposium in Palo Alto, CA EFF Staff Attorney Nate Cardozo will be in attendance for Stanford Technology Law Review and Stanford Policy & Law Review's Cybersecurity Symposium on Thursday, April 26, and Friday, April 27, at Stanford Law School in the Law Lounge. https://www.eff.org/event/stanford-law-cybersecurity-symposium * LinuxFest Northwest in Bellingham, WA LinuxFest Northwest is a free community event for people of all technical skill levels. On April 28th & 29th, stop by our table in the expo hall to talk about digital rights issues, or to sign up to become a member. https://www.eff.org/event/eff-linuxfest-northwest-2018 * Job Opening: Member Outreach Assistant We're looking for an energetic Member Outreach Assistant to support EFF's fundraising operations and help build relationships with our growing community. https://www.eff.org/about/opportunities/jobs : . : . : . : . : . : . : . : . : . : . : . : . : . : . : -------- SUPPORTED BY DONORS ------------------------------------------------- Our members make it possible for EFF to bring legal and technological expertise into crucial battles about online rights. Whether defending free speech online or challenging unconstitutional surveillance, your participation makes a difference. Every donation gives technology users who value freedom online a stronger voice and more formidable advocate. If you aren't already, please consider becoming an EFF member today. Donate Today [1] [1] https://supporters.eff.org/join/effector : . : . : . : . : . : . : . : . : . : . : . : . : . : . : * Administrivia Editor: Nathan Sheard, Grassroots Advocacy Organizer editor(a)eff.org EFFector is published by: The Electronic Frontier Foundation https://www.eff.org/ Membership & donation queries: membership(a)eff.org General EFF, legal, policy, or online resources queries: info(a)eff.org Reproduction of this publication in electronic media is encouraged. MiniLinks do not necessarily represent the views of EFF. Back issues of EFFector are available via the Web at: https://www.eff.org/effector/ Unsubscribe from future mailings or change your email preferences: https://supporters.eff.org/update-your-preferences?cid1=2061725&cs=ee9b2951… Opt out of all EFF email: https://supporters.eff.org/civicrm/mailing/optout?reset=1&jid=57782&qid=832… 815 Eddy Street San Francisco, CA 94109-7701 United States

5 years, 5 months

1
0
0 0

test@lists.ffnw.de post from stefan@osnabrueck.freifunk.net requires approval

by test-owner＠lists.ffnw.de

As list administrator, your authorization is requested for the following mailing list posting: List: test(a)lists.ffnw.de From: stefan(a)osnabrueck.freifunk.net Subject: test The message is being held because: The message is not from a list member At your convenience, visit your dashboard to approve or deny the request.

5 years, 5 months

1
0
0 0

Let's Encrypt certificate expiration notice for domain "cloud.ffnw.de" (and 3 more)

by Let's Encrypt Expiry Bot

Hello, Your certificate (or certificates) for the names listed below will expire in 20 days (on 03 May 18 18:23 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors. cloud.ffnw.de dev.ffnw.de firmware.ffnw.de office.ffnw.de For any questions or support, please visit https://community.letsencrypt.org/. Unfortunately, we can't provide support by email. For details about when we send these emails, please visit https://letsencrypt.org/docs/expiration-emails/. In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message. If you want to stop receiving all email from this address, click http://mandrillapp.com/track/unsub.php?u=30850198&id=7b5d7c271cce46eba05511… (Warning: this is a one-click action that cannot be undone) Regards, The Let's Encrypt Team

5 years, 5 months

1
0
0 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

Admin April 2018