Ramblings of a Unix Geek

The core problem with a public cloud is “untrusted infrastructure”.

If your organisation is anything typical then you have multiple web sites and application that require authentication.

“To summarise the summary of the summary; people are a problem” - Douglas Adams, The Restaurant At The End Of The Universe In a traditional compute environment we may have a lot of controls.

Shadow IT isn’t a new thing.

From Twitter came this gem: This is a cute way of helping people understand the difference between the three concepts.

I’ve spent a few posts talking about the ecosystem required to keep a container secure; hands off automation, code provenance, and the like.

A decade or so back, VistaPrint did a “free card” offer as long as you used one of their templates.

Back in Container security I said that we need to think about containers as VMs.

Identity and Access Management (IAM) historically consists of the three A’s Authentication What acccount is being accessed?

In a previous post I showed that if you stop treating containers as if they were VMs then container security is easy.

People think container security is hard.

It started with a set of slides by a friend: My first thought was to wonder wonder how heartbleed, shellshock, cve-2015-7547 and the like fit into this story.

My old site was nicely hand crafted HTML.

I first got into Unix in 1987.

I was reminded of a backblaze article about SMART numbers.

Coworker: i’ve found that networking/factime can pay dividends CW: *face time Me: “factime” - that was the early name for “bullet time”, but they realised “fast and circular” didn’t sound as cool.

Either the DHS is attacking me, or else they’ve got compromised computers… In my logs I see 1147 attempts from 64.69.57.20 to my web server; e.g. 64.69.57.20 - - [03/Jul/2015:00:40:32 -0400] "\x16\x03\x01" 501 295 "-" "-" 64.69.57.20 - - [03/Jul/2015:00:4…

So it looks like those scans were coming from NCATS.

When I was 10 my teacher told us this joke.

So I wrote that Voyager was the worst ST ever.

“Voyager” has a reputation for being awful.

I hit a web page which, naturally, refused to work properly.

I have a linode and a Panix v-colo.

Discussions elsewhere (in more than one place; coincidence?)

I can code, but mostly I write quick scripts for various purposes.

So I decided to play a little bit with google authenticator on my systems that are visible to the internet. ie my linode, Panix v-colo and ‘bastion’ host at home.

My web design skills are a little on the old side.

In the early 90s I was learning DOS and Unix.

Just two weeks ago, I revisited my virtualization options with a view to making the system more reliable - primarily by using mirrored disks.

Two years ago I looked at some options for doing virtualisation at home.

People keep telling me how Windows 7 is so much better than XP.

Since those experiments, linode is now also providing native IPv6 so my linode was switched to the auto-provided address they provide.

Just for the lulz I fired up a CentOS VM (I knew that Citrix XenServer would come in handy!)

My v-colo at Panix can be configured to use IPv6.

Not only have I been playing with Kerberos, but I’ve also been playing with IPv6.

So I built a quick AD domain based on W2k3 R2.

Disclaimer: I know nothing about Kerberos.

Because of who we are and what we do, a number of people who post to newsgroups like to hide themselves; use anonymous names, try to stop archives from retaining messages and so on.

Many of us are geeks who like to play with technology “because it is there”.

In my spare room I have what I grandiously like to call a library.