December 2014 archive
Dec 22
FIR #787 – 12/22/14 – For Immediate Release
Dec 21
TDYR 201 – Winter Solstice and the Coming of Light
Dec 21
10 Years of FIR Podcast Coming Up on January 5, 2015 – Suggestions?
Unbelievably, the For Immediate Release (FIR) Podcast to which I contribute is coming up on a TEN YEAR anniversary! As co-host Neville Hobson recently wrote in the FIR Community on Google+:
On January 5, 2015, Shel and I will be recording episode 789 of The Hobson & Holtz Report.That episode will mark a very special milestone for us and for our community of listeners and friends as it will be the episode that starts our eleventh year of podcasting.
So on January 5 next year, we will have completed 10 years of The H&H Report almost to the day - episode 1 was published on January 3, 2005.
A rather amazing run for a podcast! I remember quite well way back in early 2005 as the whole world of "podcasting" was this new and fascinating space. It was something like February or March 2005 when I stumbled across FIR and started listening... and then, of course, shy person that I am, almost immediately started sending in audio comments.
Over time those audio comments evolved into reports and sometime in the fall of 2005 I was officially named a "correspondent" into the show.
And ever since those days in 2005... pretty much every week I've sent in my 5-7 minute report. I've missed a few weeks, but over all those years it's only been a few weeks. Even as I write this post, I'm also writing the notes for what I'm going to talk about in my report into tomorrow's show (that I'll record in the morning).
I'll save some more reminiscing for that actual show #789 on January 5, 2015 ... but in the meantime I'll relay the rest of Neville's request:
We have in mind a few things we plan to say in episode 789 to mark the milestone. One thing we definitely want to do is highlight the journey from that single podcast in 2005 to the FIR Podcast Network you see today, and our plans in 2015.Is there anything that you would like to say or contribute or suggest for that episode to celebrate 10 years? All ideas most welcome!
If you do have ideas... I would encourage you to leave them as comments inside the FIR community on Google+. You can also contact Shel and Neville through one of the various contact methods in the sidebar of the FIR website.
It's pretty amazing to think of FIR being around - and consistently published for 10 years - I'm looking forward to joining in the celebration on January 5, 2015!
If you found this post interesting or useful, please consider either:
- following me on Twitter;
- adding me to a circle on Google+;
- following me on Ello;
- following me on App.net;
- subscribing to my email newsletter; or
- subscribing to the RSS feed.
Dec 20
Congrats to the Wire Team for TNW Apps of The Year Selection
TNW's Napier Lopez talks about how beautiful Wire is and how much it is a platform that he wants to use... and suddenly he is the one asking people to join him.
Many of comments mirror my own opinion of how much I enjoy using the app. It's just a pleasure to use for communication.
Napier Lopez does, though, hit Wire's real challenge:
Still, I mentioned earlier that I started using other messaging platforms because my friends made me, and therein lies the crux with Wire, or any new messaging platofrm, really: you need to get users on the platform.
This is indeed the "user directory problem" that I wrote about at great length. And I, too, hope that the Wire team - and we all as Wire users - can find ways to help bring people to the platform.
Meanwhile, congrats to the Wire team for this recognition - and I look forward to seeing what may be coming up next in the app!
P.S. I notice a version 1.2 for iOS just appeared in the AppStore and it includes the ability to invite people to join, so that's a start....
If you found this post interesting or useful, please consider either:
- following me on Twitter;
- adding me to a circle on Google+;
- following me on Ello;
- following me on App.net;
- subscribing to my email newsletter; or
- subscribing to the RSS feed
Dec 19
SS7 Security On Techmeme? A Reminder About Interconnected Systems…
SS7 security issues reported on Techmeme? I did a double-take yesterday and, as Jay Cuthrell noted on Twitter, wondered if this was a “ThrowbackThursday” taken to the extreme. But no, there was indeed a report in the Washington Post about German security researchers discovering that aspects of SS7 signaling that could be used to listen to phone conversations and/or read text messages on mobile networks. As the article notes:
The flaws discovered by the German researchers are actually functions built into SS7 for other purposes – such as keeping calls connected as users speed down highways, switching from cell tower to cell tower – that hackers can repurpose for surveillance because of the lax security on the network.
The researchers noted that one of the attackers could get around existing encryption mechanisms used on mobile networks:
For calls or texts transmitted using strong encryption, such as is commonly used for advanced 3G connections, hackers could request through SS7 that each caller’s carrier release a temporary encryption key to unlock the communication after it has been recorded.
SS7, or Signalling System 7, is of course the dominant set of telephony signaling protocols used in the legacy Public Switched Telephone Network (PSTN) made up of today’s wired and wireless (mobile) telephone networks. As such, we don’t write about SS7 hardly at all here on the VOIPSA blog as it is not related to VoIP.
However, there were three important thoughts to me coming out of this article:
1. VoIP can be more secure than the PSTN. The report mentions the encryption of the underlying 3G transport infrastructure being subverted. However, with VoIP apps that are “Over-The-Top” (OTT) riding on the mobile data network, the encryption can happen from within the app on one mobile device all the way to the app on the other mobile device – or at least back to a central set of servers. Now, there can be other security vulnerabilities with such a system, but the transport layer could at least be secured.
2. Telecommunication systems are only as secure as their weakest link – and are interconnected. The bigger concern is of course that most of our telecom systems are all interconnected… and you can have the most secure VoIP system in the world, but if you wind up connecting to the PSTN – and specifically in this case to mobile PSTN networks – then you are open to exactly these kind of attacks. Obviously if you are communicating only within an OTT “walled garden” where you only talk to others using the same OTT app you can be secure, but the moment you go out to the PSTN you are open to all the issues there.
3. Fixed lines are no safer if you talk to mobile users. The article ends with a German senator saying “When I really need a confidential conversation, I use a fixed-line phone“. I don’t know about that. For one thing, if the person you are calling is a mobile phone user, you are again open to these kind of attacks. Secondly the Snowden revelations of the past year have certainly shown us that large agencies have the ability to listen in to communications on the networks of the PSTN. If I absolutely want a confidential conversation, I’m personally going to use one of the VoIP applications that has end-to-end encryption. I’m NOT going to trust a fixed line any more than I would trust a mobile phone.
And I guess the final thought is of course that the legacy PSTN is full of security issues – they just aren’t necessarily as open to all to see because of the more closed nature of the traditional telephone networks.
A good reminder, though, that telephony security has always been a problem – and we need to ensure that both our VoIP and traditional networks have adequate security.
Meanwhile, it was rather fun to see SS7 mentioned on Techmeme… not something you’d expect to see!
Dec 19
Friday Humor – Hipku Encodes An IPv6 Address As Haiku
For your Friday enjoyment, here is the IPv6 utility you never knew you needed – Hipku will encode an IP address as haiku. For instance, here is the IPv6 address of our Deploy360 website:
Chilled apes and fat smew
aid chilled ace ace ace ace ants.
Ace ants aid ace clans.
Now, I’m not personally sure that helps me a great amount… but it’s certainly something amusing to try on a Friday. You may get something more memorable for your address. 
You can visit the site at:
http://gabrielmartin.net/projects/hipku/
and get the actual source code on Github at:
https://github.com/gabemart/hipku
It does work for IPv6 and IPv4 addresses and if you click on the link for your current IP address (under “Example”) you’ll get a nice page with an image behind it.
As author Gabriel Martin explains, he did this entirely for fun … and he does go into great detail about how he did it all.
Anyway… have fun with it!
P.S. And when you are ready to get serious about implementing IPv6, please head over to our Start Here page to find resources designed to help you get started today!
P.P.S. And if you are asking yourself, “why would I remember an IPv6 address? That’s what DNS is for!” We agree… and we also think DNS should be made secure! If you aren’t familiar with DNSSEC, why not learn about it today?
Dec 19
Norway’s .NO Passes 22,000 DNSSEC-signed Domains
It’s fun watching on Twitter as Norway’s .NO grows in the number of DNSSEC-signed second-level domains. Norid’s Unni Solås tweeted out today that they had passed 22,794 signed .NO domains – and also provided an explanation for this ongoing growth:
#DNSSEC, day 11: 22794 signed .no domains. The steady increase is due to Very Big Registrar signing in nightly batches.
— Unni Solås (@unniquity) December 19, 2014
Congrats to the Norid team – it’s great to see the growth… you may recall that only a week ago we wrote about .NO crossing the 5,000 signed domain mark! Quite a good increase in the space of only a week! Given that Norid’s main page states there are 650,211 .NO domains in total, this brings them to about 3.5% of all .NO domains being signed with DNSSEC. Not a bad start for a newly signed domain.
Norid has also published its “DNSSEC Policy and Practice Statement (DPS)” that outlines their policies and procedures. We’ve added that to our list of DPS documents that can be found at:
http://www.internetsociety.org/deploy360/resources/dnssec-practice-statements/
If you are with a top-level domain, or even with an enterprise seeking to sign your own domain(s), these DPS documents can be useful to understand the degree of security that some TLDs are undertaking.
Congrats again to the Norid team and we’ll look forward to seeing their continued growth!
P.S. If you want to sign your domain with DNSSEC or enable DNSSEC validation on your network, please visit our Start Here page to find resources aimed at your type of organization or role.
Dec 18
TDYR 200 – WordPress 4.1 Brings Improved Distraction-Free Writing
Dec 18
New WordPress 4.1 Provides Much Improved Distraction-Free Writing Experience
The beautiful part about this is that when you click in the window and start typing, all the sidebars and menus fade way so that you can just focus on writing...
BUT...
... the moment you move your mouse outside the writing window all the sidebars and menus come back!
This is a huge improvement over the previous experience with WordPress 4.0 where once you clicked the button you were in a white screen with no way out unless you scrolled up and clicked the link in the menu bar that appeared:
I found the WordPress 4.0 way so annoying that I never used it. Inevitably after I entered the mode I needed to change categories or tags or something like that - and so it was simply easier to NOT use the distraction-free mode.
The WordPress development team produced a video that shows how well this new writing mode works.
I like it because it lets me write but also makes it super easy for me to get back to the menus and sidebars.
All you need to do to enable the "distraction-free writing" mode is to click on the box on the right top of the editing window:
It acts as a toggle to turn the "DFW" mode on or off.
Very nicely done!
There were of course many other aspects of the WordPress 4.1 release. The release post and the field notes as well as the codex entry go into much more detail. The Twenty Fifteen theme is pretty cool... and some of the other features are also interesting. But for me... I just like this new writing environment!
What do you think? What do you like best about WordPress 4.1?
An audio commentary is available as TDYR 200:
If you found this post interesting or useful, please consider either:
- following me on Twitter;
- adding me to a circle on Google+;
- following me on Ello;
- following me on App.net;
- subscribing to my email newsletter; or
- subscribing to the RSS feed.
Dec 18
ICANN Seeking Volunteers For DNSSEC Root KSK Rollover Plan Design Team
Do you want to help ICANN plan the best was to roll the root key used for DNSSEC? Are you interested in being considered as a volunteer member of ICANN’s Root KSK Rollover Plan Design Team? Recently ICANN staff sent a message to the public dnssec-coord mailing list and other various mailing lists asking for volunteers. The “Solicitation of Statement of Internet for Membership in the Root Zone Key Signing Key Rollover Plan Design Team” (say that 10 times fast!) begins:
ICANN, as the IANA functions operator, in cooperation with Verisign as the Root Zone Maintainer and the National Telecommunications Information Administration (NTIA) as the Root Zone Administrator, together known as the Root Zone Management (RZM) partners, seek to develop a plan for rolling the root zone keysigning key (KSK). The KSK is used to sign the root zone zone-signing key (ZSK), which in turn is used to DNSSEC-sign the Internet’s root zone. The Root Zone Partners are soliciting five to seven volunteers from the community to participate in a Design Team to develop the Root Zone KSK Rollover Plan (“The Plan”). These volunteers along with the RZM partners will form the Design Team to develop The Plan.
The document goes on to list the requirements and the process. Essentially, if you meet the requirements you need to send a message with the requested information to ksk-rollover-soi@icann.org by the end of the day on Friday, January 16, 2015. The Root Zone Management partners will then choose from among the applicants to form the Design Team.
We’ve written here before about how incredibly important it is to get the Root KSK Rollover right, and so we commend ICANN for going through this process to create an appropriate Design Team. We would encourage people with operational knowledge of DNSSEC and DNS in general to definitely read over the document and consider applying!
P.S. And if you don’t know about DNSSEC, or want more information, please visit our Start Here page to find out how to begin!
