Verisign – Jupiter Broadcasting https://www.jupiterbroadcasting.com Open Source Entertainment, on Demand. Thu, 22 Jun 2017 00:47:16 +0000 en-US hourly 1 https://wordpress.org/?v=5.5.3 https://original.jupiterbroadcasting.net/wp-content/uploads/2019/04/cropped-favicon-32x32.png Verisign – Jupiter Broadcasting https://www.jupiterbroadcasting.com 32 32 Holding Hospitals Hostage | TechSNAP 261 https://original.jupiterbroadcasting.net/98616/holding-hospitals-hostage-techsnap-261/ Thu, 07 Apr 2016 08:44:35 +0000 https://original.jupiterbroadcasting.net/?p=98616 Find out about another hospital that accidentally took advantage of free encryption, researchers turn up a DDoS on the root DNS servers & the password test you never want to take. Plus your batch of networking questions, our answers & a packed round up! Thanks to: Get Paid to Write for DigitalOcean Direct Download: HD […]

The post Holding Hospitals Hostage | TechSNAP 261 first appeared on Jupiter Broadcasting.

]]>

post thumbnail

Find out about another hospital that accidentally took advantage of free encryption, researchers turn up a DDoS on the root DNS servers & the password test you never want to take.

Plus your batch of networking questions, our answers & a packed round up!

Thanks to:


DigitalOcean


Ting


iXsystems

Direct Download:

HD Video | Mobile Video | MP3 Audio | OGG Audio | YouTube | HD Torrent | Mobile Torrent

RSS Feeds:

HD Video Feed | Mobile Video Feed | MP3 Audio Feed | Ogg Audio Feed | iTunes Feed | Torrent Feed

Become a supporter on Patreon:

Patreon

Show Notes:

Researchers at VeriSign investigate DDoS on root DNS servers

  • Researchers from VeriSign, the company that runs the .com and .net registries, and operations 2 of the 13 critically import root DNS servers, will be giving a talk at a conference detailing their investigation into the attack
  • Their findings suggest the attack, which took place in November of 2015, was not directed at the root name servers directly, but was an attempt to down two chinese websites
  • The attack had some interesting patterns, likely caused by design decisions and mistakes made by the programmer of the botnet that was used in the attack
  • The provide a video showing a breakdown of the attack
  • It was interesting to learn that Randall Munroe (of XKCD fame) actually came up with the best way to visualize the distribution of IP addresses, with a grid where sequential numbers are in adjacent squares
  • Only IP addresses in the first 128 /8 netbooks were used. The use of 128/8 specifically suggests an less than or equal, rather than an equal was used during the comparison of IP addresses
  • It is not clear why a larger set of addresses were not used
  • The attack seemed to use 3 or 4 different groups of bots, sending spoofed DNS requests
  • Two of the larger groups of bots sequentially cycled through the 2.0.0.0/8 through 19.0.0.0/8 subnets at different speeds
  • Attacks were not seen from the 10.0.0.0/8 and 127.0.0.0/8 networks, for obvious reasons
  • However, a delay in the attacks sourced from 11.0.0.0/8 suggests that the botnet attempted to use the entire 10 block, but the packets just never left the source networks
  • “The researchers also note that Response Rate Limiting was an effective mitigation in countering up to 60 percent of attack traffic. RRL is a feature in the DNS protocol that mitigates amplifications attacks where spoofed DNS queries are used to target victims in large-scale DDoS attacks.”
  • “In addition to RRL, the researchers said attack traffic was easily filterable and through filtering were able to drop response traffic for the attack queries, leaving normal traffic untouched. One of the limitations with this approach is that it’s a manual process”

Virus hits Medstar hospital network, Hospital forced to shutdown systems

  • “The health system took down some its computers to prevent the virus from spreading, but it’s not clear how many computers — or hospitals — are affected”
  • “A statement by the health system said that all facilities remain open, and that there was “no evidence of compromised information.””
  • “The not-for-profit healthcare system operates ten hospitals across the Washington and Baltimore region, with more than a hundred outpatient health facilities. According to the system’s website, it has more than 31,000 employees and serves hundreds of thousands of patients annually.”
  • “One visitor to the hospital told ZDNet that staff switched the computers off after learning about the virus. The person, who was visiting a patient in one of the healthcare system’s Washington DC hospital, said the computers were powered off for more than an hour, with all patient orders lost, the person said.”
  • “It’s not clear exactly what kind of malware was used in Monday’s cyberattack. A spokesperson for MedStar Health did not immediately respond to a request for comment.”
  • An FBI spokesperson confirmed that it was “aware of the incident and is looking into the nature and scope of the matter.”
  • Additional Coverage: Threat Post
  • After a few days, the medical network was recovering
  • “The healthcare provider said the attack forced it to shut down its three main clinical information systems, prevented staff from reviewing patient medical records, and barred patients from making medical appointments. In a statement issued Wednesday, it said that no patient data had been compromised and systems were slowly coming back online.”
  • “Clinicians are now able to review medical records and submit orders via our electronic health records. Restoration of additional clinical systems continues with priority given to those related directly to patient care”
  • “While the hospital still won’t officially confirm the attacks were ransomware related, The Washington Post along with other news outlets are reporting that employees at the hospital received pop-up messages on their computer screens seeking payment of 45 Bitcoins ($19,000) in exchange for a digital key that would decrypt data”
  • “The MedStar cyberattack is one of many hospitals in recent months targeted by hackers. Last week, Kentucky-based Methodist Hospital paid ransomware attackers to unlock its hospital system after crypto-ransomware brought the hospital’s operations to a grinding halt. Earlier this year Los Angeles-based Hollywood Presbyterian Medical Center paid 40 Bitcoin ($17,000) to attackers that locked down access to the hospital’s electronic medical records system and other computer systems using crypto-ransomware.”
  • As long as hospitals continue to pay out, this will only grow to be a worse problem
  • “Medical facilities don’t give security the same type of attention that other verticals do,” said Craig Williams, senior technical leader for Cisco Talos. “They are there to heal people and cure the sick. Their first priority is not to take care of an IT environment. As a result it’s likely the hackers have been out there for quite some time and realized that there are a lot (healthcare) sites that have a lot of base vulnerabilities.”
  • As you might expect: 1400 vulnerabilities to remain unpatched in medical supply system
  • Additional Coverage
  • In related news:
  • Canadian hospital website compromised serves up the Angler malware kit to visitors
  • The site is for a hospital in a small city that serves a mostly rural area. Happens to be where I grew up, and the hospital I was born in
  • The hospital site is run on Joomla, and is running version 2.5.6, which has many known vulnerabilities. The latest version of Joomla is 3.4.8
  • “Like many site hacks, this injection is conditional and will appear only once for a particular IP address. For instance, the site administrator who often visits the page will only see a clean version of it, while first timers will get served the exploit and malware.”
  • The obvious targets are “staff, patients and their families and visitors, as well as students”
  • The hospital became a teaching facility for McMaster University’s Faculty of Health Sciences in 2009
  • “The particular strain of ransomware dropped here is TeslaCrypt which demands $500 to recover your personal files it has encrypted. That payment doubles after a week.”

CNBC Password Tester — How not to do it

  • CNBC has a post about constructing secure passwords
  • The basic idea was that you submit your password, and it tells you how strong it is
  • There are obvious problems with this idea. Why are you giving out your password anyway?
  • Of course, the CNBC site is served in plain text (which is fine for a news site), but it means your password is sent to them in the clear
  • Worse, they had the site adding all of the submitted passwords to a google spreadsheet, also in the clear
  • Because the password was submitted as a GET variable, and was in the URL, it was also included in the referral information sent to all of the advertising networks in the CNBC site, including DoubleClick, ScoreCardResearch, something hosted at Amazon AWS, and any other widgets on the site (Facebook, Gigya)
  • If you actually did want to build a tool like this, at least use javascript to perform the calculations on the users’ device and never transmit their passwords
  • Of course, users should never type the password into another website. This is the definition if a phishing attack
  • The page has since been removed
  • Additional Coverage

Feedback:


Round Up:


The post Holding Hospitals Hostage | TechSNAP 261 first appeared on Jupiter Broadcasting.

]]>
Virginia BSD Assembly | BSD Now 105 https://original.jupiterbroadcasting.net/87226/virginia-bsd-assembly-bsd-now-105/ Thu, 03 Sep 2015 05:42:04 +0000 https://original.jupiterbroadcasting.net/?p=87226 It’s already our two-year anniversary! This time on the show, we’ll be chatting with Scott Courtney, vice president of infrastructure engineering at Verisign, about this year’s vBSDCon. What’s it have to offer in that’s different in the BSD conference space? We’ll find out! Thanks to: Get Paid to Write for DigitalOcean Direct Download: Video | […]

The post Virginia BSD Assembly | BSD Now 105 first appeared on Jupiter Broadcasting.

]]>

post thumbnail

It’s already our two-year anniversary! This time on the show, we’ll be chatting with Scott Courtney, vice president of infrastructure engineering at Verisign, about this year’s vBSDCon. What’s it have to offer in that’s different in the BSD conference space? We’ll find out!

Thanks to:


DigitalOcean


iXsystems


Tarsnap

Direct Download:

Video | HD Video | MP3 Audio | OGG Audio | Torrent | YouTube

RSS Feeds:

MP3 Feed | OGG Feed | iTunes Feed | Video Feed | HD Vid Feed | HD Torrent Feed

– Show Notes: –

Headlines

OpenBSD hypervisor coming soon

  • Our buddy Mike Larkin never rests, and he posted some very tight-lipped console output on Twitter recently
  • From what little he revealed at the time, it appeared to be a new hypervisor (that is, X86 hardware virtualization) running on OpenBSD -current, tentatively titled “vmm”
  • Later on, he provided a much longer explanation on the mailing list, detailing a bit about what the overall plan for the code is
  • Originally started around the time of the Australia hackathon, the work has since picked up more steam, and has gotten a funding boost from the OpenBSD foundation
  • One thing to note: this isn’t just a port of something like Xen or Bhyve; it’s all-new code, and Mike explains why he chose to go that route
  • He also answered some basic questions about the requirements, when it’ll be available, what OSes it can run, what’s left to do, how to get involved and so on

Why FreeBSD should not adopt launchd

  • Last week we mentioned a talk Jordan Hubbard gave about integrating various parts of Mac OS X into FreeBSD
  • One of the changes, perhaps the most controversial item on the list, was the adoption of launchd to replace the init system (replacing init systems seems to cause backlash, we’ve learned)
  • In this article, the author talks about why he thinks this is a bad idea
  • He doesn’t oppose the integration into FreeBSD-derived projects, like FreeNAS and PC-BSD, only vanilla FreeBSD itself – this is also explained in more detail
  • The post includes both high-level descriptions and low-level technical details, and provides an interesting outlook on the situation and possibilities
  • Reddit had quite a bit to say about this one, some in agreement and some not

DragonFly graphics improvements

  • The DragonFlyBSD guys are at it again, merging newer support and fixes into their i915 (Intel) graphics stack
  • This latest update brings them in sync with Linux 3.17, and includes Haswell fixes, DisplayPort fixes, improvements for Broadwell and even Cherryview GPUs
  • You should also see some power management improvements, longer battery life and various other bug fixes
  • If you’re running DragonFly, especially on a laptop, you’ll want to get this stuff on your machine quick – big improvements all around

OpenBSD tames the userland

  • Last week we mentioned OpenBSD’s tame framework getting support for file whitelists, and said that the userland integration was next – well, now here we are
  • Theo posted a mega diff of nearly 100 smaller diffs, adding tame support to many areas of the userland tools
  • It’s still a work-in-progress version; there’s still more to be added (including the file path whitelist stuff)
  • Some classic utilities are even being reworked to make taming them easier – the “w” command, for example
  • The diff provides some good insight on exactly how to restrict different types of utilities, as well as how easy it is to actually do so (and en masse)
  • More discussion can be found on HN, as one might expect
  • If you’re a software developer, and especially if your software is in ports already, consider adding some more fine-grained tame support in your next release

Interview – Scott Courtney – vbsdcon@verisign.com / @verisign

vBSDCon 2015


News Roundup

OPNsense, beyond the fork

  • We first heard about OPNsense back in January, and they’ve since released nearly 40 versions, spanning over 5,000 commits
  • This is their first big status update, covering some of the things that’ve happened since the project was born
  • There’s been a lot of community growth and participation, mass bug fixing, new features added, experimental builds with ASLR and much more – the report touches on a little of everything

LibreSSL nukes SSLv3

  • With their latest release, LibreSSL began to turn off SSLv3 support, starting with the “openssl” command
  • At the time, SSLv3 wasn’t disabled entirely because of some things in the OpenBSD ports tree requiring it (apache being one odd example)
  • They’ve now flipped the switch, and the process of complete removal has started
  • From the Undeadly summary, “This is an important step for the security of the LibreSSL library and, by extension, the ports tree. It does, however, require lots of testing of the resulting packages, as some of the fallout may be at runtime (so not detected during the build). That is part of why this is committed at this point during the release cycle: it gives the community more time to test packages and report issues so that these can be fixed. When these fixes are then pushed upstream, the entire software ecosystem will benefit. In short: you know what to do!”
  • With this change and a few more to follow shortly, LibreSSL won’t actually support SSL anymore – time to rename it “LibreTLS”

FreeBSD MPTCP updated

  • For anyone unaware, Multipath TCP is “an ongoing effort of the Internet Engineering Task Force’s (IETF) Multipath TCP working group, that aims at allowing a Transmission Control Protocol (TCP) connection to use multiple paths to maximize resource usage and increase redundancy.”
  • There’s been work out of an Australian university to add support for it to the FreeBSD kernel, and the patchset was recently updated
  • Including in this latest version is an overview of the protocol, how to get it compiled in, current features and limitations and some info about the routing requirements
  • Some big performance gains can be had with MPTCP, but only if both the client and server systems support it – getting it into the FreeBSD kernel would be a good start

UEFI and GPT in OpenBSD

  • There hasn’t been much fanfare about it yet, but some initial UEFI and GPT-related commits have been creeping into OpenBSD recently
  • Some support for UEFI booting has landed in the kernel, and more bits are being slowly enabled after review
  • This comes along with a number of other commits related to GPT, much of which is being refactored and slowly reintroduced
  • Currently, you have to do some disklabel wizardry to bypass the MBR limit and access more than 2TB of space on a single drive, but it should “just work” with GPT (once everything’s in)
  • The UEFI bootloader support has been committed, so stay tuned for more updates as further progress is made

Feedback/Questions


  • Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv
  • BSD Now anniversary shirts are no longer available, and should be shipping out very soon (if they haven’t already) – big thanks to everyone who bought one (183 sold!)
  • This week is the last episode written/organized by TJ

The post Virginia BSD Assembly | BSD Now 105 first appeared on Jupiter Broadcasting.

]]>
BGP & BSD | BSD Now 1 https://original.jupiterbroadcasting.net/42662/bgp-bsd-bsd-now-1/ Fri, 06 Sep 2013 13:34:00 +0000 https://original.jupiterbroadcasting.net/?p=42662 We kick off the first episode with the latest BSD news, show you how to avoid intrusion detection systems and talk to Peter Hessler about BGP spam blacklists!

The post BGP & BSD | BSD Now 1 first appeared on Jupiter Broadcasting.

]]>

post thumbnail

RSS Feeds:

MP3 Feed | OGG Feed | iTunes Feed | Video Feed | HD Vid Feed | HD Torrent Feed

– Show Notes: –

Headlines

Radeon KMS commited

  • Committed by Jean-Sebastien Pedron
  • Brings kernel mode setting to -CURRENT, will be in 10.0-RELEASE (ETA 12/2013)
  • 10-STABLE is expected to be branched in October, to begin the process of stabilizing development
  • Initial testing shows it works well
  • May be merged to 9.X, but due to changes to the VM subsystem this will require a lot of work, and is currently not a priority for the Radeon KMS developer
  • Still suffers from the syscons / KMS switcher issues, same as Intel video
  • More info: https://wiki.freebsd.org/AMD_GPU

VeriSign Embraces FreeBSD

  • “BSD is quite literally at the very core foundation of what makes the Internet work”
  • Using BSD and Linux together provides reliability and diversity
  • Verisign gives back to the community, runs vBSDCon
  • “You get comfortable with something because it works well for your particular purposes and can find a good community that you can interact with. That all rang true for us with FreeBSD.”

fetch/libfetch get a makeover

  • Adds support for SSL certificate verification
  • Requires root ca bundle (security/root_ca_nss)
  • Still missing TLS SNI support (Server Name Indication, allows name based virtual hosts over SSL)

FreeBSD Foundation Semi-Annual Newsletter

  • The FreeBSD Foundation took the 20th anniversary of FreeBSD as an opportunity to look at where the project is, and where it might want to go
  • The foundation sets out some basic goals that the project should strive towards:
    • Unify User Experience
      • “ensure that knowledge gained mastering one task translates to the next”
      • “if we do pay attention to consistency, not only will FreeBSD be easier to use, it will be easier to learn”
    • Design for Human and Programmatic Use
      • 200 machines used to be considered a large deployment, with high density servers, blades, virtualization and the cloud, that is not so anymore
      • “the tools we provide for status reporting, configuration, and control of FreeBSD just do not scale or fail to provide the desired user experience”
      • “The FreeBSD of tomorrow needs to give programmability and human interaction equal weighting as requirements”
    • Embrace New Ways to Document FreeBSD
      • More ‘Getting Started’ sections in documentation
      • Link to external How-Tos and other documentation
      • “upgrade the cross-referencing and search tools built into FreeBSD, so FreeBSD, not an Internet search engine, is the best place to learn about FreeBSD”
  • Spring Fundraising Campaign, April 17 – May 31, raised a total of $219,806 from 12 organizations and 365 individual donors. In the same period last year we raised a total of $23,422 from 2 organizations and 53 individuals
  • Funds donated to the FreeBSD Foundation have been used on these projects recently:
  • Capsicum security-component framework
  • Transparent superpages support of the FreeBSD/ARM architecture
  • Expanded and faster IPv6
  • Native in-kernel iSCSI stack
  • Five New TCP Congestion Control Algorithms
  • Direct mapped I/O to avoid extra memory copies
  • Unified Extensible Firmware Interface (UEFI) boot environment
  • Porting FreeBSD to the Genesi Efika MX SmartBook laptop (ARM-based)
  • NAND Flash filesystem and storage stack
  • Funds were also used to sponsor a number of BSD focused conferences: BSDCan, EuroBSDCon, AsiaBSDCon, BSDDay, NYCBSDCon, vBSDCon, plus Vendor summits and Developer summits
  • It is important that the foundation receive donations from individuals, to maintain their tax exempt status in the USA. Even a donation of $5 helps make it clear that the FreeBSD Foundation is backed by a large community, not only a few vendors
  • Donate Today

The place to B…SD

Ohio Linuxfest, Sept. 13-15, 2013

  • Very BSD friendly
  • Kirk McKusick giving the keynote
  • BSD Certification on the 15th, all other stuff on the 14th
  • Multiple BSD talks

LinuxCon, Sept. 16-18, 2013

  • Dru Lavigne and Kris Moore will be manning a FreeBSD booth
  • Number of talks of interest to BSD users, including ZFS coop

EuroBSDCon, Sept. 26-29, 2013

  • Tutorials on the 26 & 27th (plus private FreeBSD DevSummit)
  • 43 talks spread over 3 tracks on the 28 & 29th
  • Keynote by Theo de Raadt
  • Hosted in the picturesque St. Julians Area, Malta (Hilton Conference Centre)

Interview – Peter Hessler – phessler@openbsd.org / @phessler

Using BGP to distribute spam blacklists and whitelists

  • Q: Tell us about yourself and your previous contributions to OpenBSD
  • Q: What is BGP spamd
  • Q: What made you start the project?
  • Q: Why use BGP? What are the pros/cons versus the standard DNS distribution model?
  • Q: (How) can others make use of the project?
  • Q: How can other contribute to the project?
  • Q: What else are you working on?

Tutorial

Using stunnel to hide your traffic from Deep Packet Inspection

  • Live demo between two hosts
  • Tunnel any insecure traffic over SSL/TLS
  • Allows you to bypass Intrusion Detection Systems

News Roundup

NetBSD 6.1.1 released

  • First security/bug fix update of the NetBSD 6.1 release branch
  • Fixes 4 security vulnerabilities
  • Adds 4 new sysctls to avoid IPv6 DoS attacks
  • Misc. other updates

Sudo Mastery

  • MWL is a well-known author of many BSD books
  • Also does SSH, networking, DNSSEC, etc.
  • Next book is about sudo, which comes from OpenBSD (did you know that?)
  • Available for preorder now at a discounted price

Documentation Infrastructure Enhancements

  • Gábor Kövesdán has completed a funded project to improve the infrastructure behind the documentation project
  • Will upgrade documentation from DocBook 4.2 to DocBook 4.5 and at the same time migrate to proper XML tools.
  • DSSSL is an old and dead standard, which will not evolve any more.
  • DocBook 5.0 tree added

FreeBSD FIBs get new features

  • FIBs (as discussed earlier in the interview) are Forward Information Bases (technical term for a routing table)
  • The FreeBSD kernel can be compiled to allow you to maintain multiple FIBs, creating separate routing tables for different processes or jails
  • In r254943 ps(1) is extended to support a new column ‘fib’, to display which routing table a process is using

FreeNAS 9.1.0 and 9.1.1 released

  • Many improvements in nearly all areas, big upgrade
  • Based on FreeBSD 9-STABLE, lots of new ZFS features
  • Cherry picked some features from 10-CURRENT
  • New volume manager and easy to use plugin management system
  • 9.1.1 released shortly thereafter to fix a few UI and plugin bugs

BSD licensed “patch” becomes default

  • bsdpatch has become mature, does what GNU patch can do, but has a much better license
  • Approved by portmgr@ for use in ports
  • Added WITH_GNU_PATCH build option for people who still need it

  • All the tutorials are posted in their entirety at bsdnow.tv
  • Send questions, comments, show ideas/topics, etc to feedback@bsdnow.tv
  • Watch live Wednesdays at 2:00PM Eastern (18:00 UTC)

The post BGP & BSD | BSD Now 1 first appeared on Jupiter Broadcasting.

]]>
NASA Hacked 5,400 Times? | TechSNAP 47 https://original.jupiterbroadcasting.net/17571/nasa-hacked-5400-times-techsnap-47/ Thu, 01 Mar 2012 20:20:13 +0000 https://original.jupiterbroadcasting.net/?p=17571 NASA loses the keys to the International Space Station, Microsoft can’t figure out what day it is, and laugh over the lack of security at Stratfor.

The post NASA Hacked 5,400 Times? | TechSNAP 47 first appeared on Jupiter Broadcasting.

]]>

post thumbnail

NASA loses the keys to the International Space Station, Microsoft can’t figure out what day it is, and I laugh myself to tears over the lack of security at Stratfor

All that and more, on this week’s TechSNAP!

Thanks to:

GoDaddy.com Use our codes TechSNAP10 to save 10% at checkout, or TechSNAP20 to save 20% on hosting!

Super special savings for TechSNAP viewers only. Get a .co domain for only $7.99 (regular $29.99, previously $17.99). Use the GoDaddy Promo Code cofeb8 before the end of March to secure your own .co domain name for the same price as a .com.

Private Registration use code: march8

Pick your code and save:
cofeb8: .co domain for $7.99
techsnap7: $7.99 .com
techsnap10: 10% off
techsnap20: 20% off 1, 2, 3 year hosting plans
techsnap40: $10 off $40
techsnap25: 25% off new Virtual DataCenter plans

   

 

Direct Download Links:

HD Video | Large Video | Mobile Video | MP3 Audio | OGG Audio | YouTube

Subscribe via RSS and iTunes:

Show Notes:

NASA laptop stolen, contained control algorithms for the International Space Station

  • In 2010 and 2011 NASA reported 5,408 computer security incidents ranging from the installation of malware on a computer, through the theft of devices and cyber attacks suspected to be from foreign intelligence agencies.
  • 47 incidents were identified as Advance Persistent Threat attacks, and of these, 13 were successful in compromising the agency’s computer systems
  • In an example of such an incident, attackers from Chinese-based IP addresses gained full access to a number of key JPL systems giving them the ability to:
  • Modify, copy or delete sensitive files
  • Add, modify or delete user accounts for mission critical systems
  • Upload hacking tools (keyloggers, rootkits) to steal user credentials and thereby compromise other NASA systems
  • Modify or corrupt the system logs to conceal their actions
  • Some of the breaches have resulted in the unauthorized release of Personally Identifiable Information, the disclosure of sensitive export-controlled data and 3rd party intellectual property
  • Inspector General Testimony before Congress re: IT Security
  • Discovery News Coverage

Windows Azure suffers worldwide outage

  • The Microsoft Azure Cloud service was down for most of the day on February 29th
  • The Service Management system was down for over 9 hours
  • Azure Data Sync was down form 2012–02–29 08:00 through 2012–03–01 03:00 UTC
  • Microsoft says that the outage appears to have been caused by a leap year bug
  • “28 February, 2012 at 5:45 PM PST Windows Azure operations became aware of an issue impacting the compute service in a number of regions,”
  • “While final root cause analysis is in progress, this issue appears to be due to a time calculation that was incorrect for the leap year.”
  • Microsoft Azure Service Dashboard
  • The outage also effected the UK Government’s ‘G-Cloud’ CloudStore
  • TechWeek Europe Coverage
  • Slashdot Coverage – Outage Root Cause
  • PCWorld – Previous Microsoft problems with Leap Years

Wikileaks releases the data stolen in the StratFor compromise


Feedback:

Q: Robert Bishop Writes: Can I Secure my network with multiple NAT routers to isolate a system?

War Story:

This is a war story with a difference, as it didn’t involve some crazy user doing some bat shit crazy thing with their computer. It was simply a call to one of the tech support agents where the user wanted to know the following:

“What is the exact chemical composition of the battery in the Thinkpad 760 XD?”
“What are the recommended disposal procedures for said battery?”
“Can you tell me what would happen to the battery if it ruptured in a vacuum environment?”
“If the battery were to overheat, how volatile would the liquid effluent be?”

I doubt the user could have even gotten the questions out and taken a breath before the agent put them on hold and ran for help. The agent walked over to the second level support area rather than call as per procedure. After a good five minutes of talking, nobody could really answer the questions and worse, we couldn’t figure out what part of the company might actually have those answers.

As with all good tech support strategies we decided a two pronged approach – the agent would get back on with the user and stall for time while the rest of us would frantically hunt down any possible source of information that could help. We told the agent to ask why the user needed such detailed information and if it was a weak answer to push for a callback to buy even more time.

Some twenty minutes later the agent came back over to us with some interesting details on what was going on. It was all a misunderstanding. The user was supposed to call some private support number at IBM and not the public number. Our enterprising young agent did pull a fast one and offer to transfer the user to the number directly. The user provided the number and the agent promptly connected the call, then hit mute and stayed on the line. An American accent answered, the user responded and provided an account code upon request.

The tech on the private number acknowledged that the user was calling from NASA – Blackhawk Technologies Subsidiary. Apparently the shuttle program had 4 of those laptops on each mission – 1 primary and 3 redundant backups just in case. Suddenly the tricky questions all made sense. And eavesdropping can kill curiosity can never be a bad thing, right?

Round Up:

The post NASA Hacked 5,400 Times? | TechSNAP 47 first appeared on Jupiter Broadcasting.

]]>