212 stories
·
3 followers

Software Bug Behind Biggest Telephony Outage In US History

1 Comment and 3 Shares
An anonymous reader writes: A software bug in a telecom provider's phone number blacklisting system caused the largest telephony outage in US history, according to a report released by the US Federal Communications Commission (FCC) at the start of the month. The telco is Level 3, now part of CenturyLink, and the outage took place on October 4, 2016. According to the FCC's investigation, the outage began after a Level 3 employee entered phone numbers suspected of malicious activity in the company's network management software. The employee wanted to block incoming phone calls from these numbers and had entered each number in fields provided by the software's GUI. The problem arose when the Level 3 technician left a field empty, without entering a number. Unbeknownst to the employee, the buggy software didn't ignore the empty field, like most software does, but instead viewed the empty space as a "wildcard" character. As soon as the technician submitted his input, Level 3's network began blocking all incoming and outgoing telephone calls — over 111 million in total.

Read more of this story at Slashdot.

Read the whole story
Share this story
Delete
1 public comment
letssurf
12 days ago
reply
Lol
Northampton, UK

Foxconn acquires Belkin International for $866 million

1 Comment
Foxconn expands its footprint into the mobile accessories and smart home markets by acquiring Belkin International, including the Linksys, Wemo, and Phyn brands, for nearly $866 million in cash. Read more...
Read the whole story
Share this story
Delete
1 public comment
letssurf
22 days ago
reply
Eek
Northampton, UK

All my messages are being marked as spam

1 Comment and 2 Shares

Read the whole story
Share this story
Delete
1 public comment
letssurf
26 days ago
reply
Oh no, how was he suppose to know. lol
Northampton, UK

Let’s Encrypt now supports wildcard certificates

1 Comment

Here are some very exciting news from Let’s Encrypt:

We’re pleased to announce that ACMEv2 and wildcard certificate support is live! With today’s new features we’re continuing to break down barriers for HTTPS adoption across the Web by making it even easier for every website to get and manage certificates.

ACMEv24.0k is an updated version of our ACME protocol which has gone through the IETF standards process, taking into account feedback from industry experts and other organizations that might want to use the ACME protocol for certificate issuance and management some day.

Wildcard certificates5.1k allow you to secure all subdomains of a domain with a single certificate. Wildcard certificates can make certificate management easier in some cases, and we want to address those cases in order to help get the Web to 100% HTTPS. We still recommend non-wildcard certificates for most use cases.

Wildcard certificates are only available via ACMEv2. In order to use ACMEv2 for wildcard or non-wildcard certificates you’ll need a client that has been updated to support ACMEv28.5k. It is our intent to transition all clients and subscribers to ACMEv2, though we have not set an end-of-life date for our ACMEv1 API yet.

Additionally, wildcard domains must be validated using the DNS-01 challenge type. This means that you’ll need to modify DNS TXT records in order to demonstrate control over a domain for the purpose of obtaining a wildcard certificate.

Read the whole story
Share this story
Delete
1 public comment
letssurf
31 days ago
reply
Yay wildcards!!
Northampton, UK

When you think you’ve finished the project, but actually you haven’t… at all…

1 Comment and 2 Shares

Read the whole story
Share this story
Delete
1 public comment
letssurf
31 days ago
reply
Oh and...
Northampton, UK

The sprint is the sprint

2 Comments

Read the whole story
Share this story
Delete
2 public comments
letssurf
31 days ago
reply
These are funny
Northampton, UK
mkalus
34 days ago
reply
I say this from the bottom of my heart: FUCK AGILE!
iPhone: 49.287476,-123.142136
reconbot
33 days ago
What works better for you?
Next Page of Stories