SSCC 158 - What do you mean, "Don't knit your own remote authentication"? [PODCAST]

Filed Under: Android, Data loss, Featured, Firefox, Google, Google Chrome, Internet Explorer, Law & order, Malware, Microsoft, Podcast, Privacy, Vulnerability, Web Browsers

Sophos Security Chet Chat - Episode 158 - July 30, 2014

News, opinion, advice and research!

Here's our latest security podcast, featuring Sophos experts and Naked Security writers Chester Wisniewski and Paul Ducklin.

(Audio player above not working? Download the MP3, or listen on Soundcloud.)

Stories covered in this episode of the Chet Chat

Get this and other Sophos podcasts

Download this episode as an MP3... Sophos podcasts on Soundcloud... RSS feed of Sophos podcasts...

, , , , , , , , , , , , , , , , , , , , , , ,

You might like

3 Responses to SSCC 158 - What do you mean, "Don't knit your own remote authentication"? [PODCAST]

  1. Mike · 393 days ago

    any chance you guys could post a text version for those of us that cannot listen to the podcast, or would prefer to read them as it's faster?

    • Paul Ducklin · 393 days ago

      We get asked this every now and then. We (well, I :-) then usually knuckle down and do transcripts for a week or three before giving up again. Perhaps I can explain why I don't usually do them, and see if you buy it.

      Firstly, it actually takes a LOT longer than you might think to do a proper transcript, unless you're a stenographer (and I am not).

      Secondly, we put a lot of effort into producing these *as podcasts*, where the interaction is part of what we're trying to create.

      Thirdly, spoken and written English can be considered two different languages. Reading out written English works quite well, but writing out spoken English, IMO, does not. The unscripted spoken word, when transcribed, tends to make poor prose. Even spoken English that sounds educational and informed often ends up as indifferent, sometimes borderline illiterate, written English.

      Fourthly, when we've obliged with transcripts before, they've ended up with about 10-20 people actually ever looking at the page. (And 5-10 of those are me, proofreading, correcting and proofing again :-)

      In short, we do the podcasts specifically for people who like to listen to things, as well or instead of reading, figuring we already have lots of written material for those who like to read rather than to listen. For that reason, we include links to written articles about the topics in the podcast.

      I apologise if it sounds as though I am desperately trying to get out of doing the transcripts. The reason for that is that I am desperately trying to get out of doing them :-)

      What if you were to click through to the links in the podcast article, and read those instead? Would that work for you?

      • Wow... I was just going to say if you are interested in the facts, please read the articles we link to. The podcasts are intended for people who prefer to listen, perhaps during their commute, to stay on top of the latest security topics. We do include more of our opinions on the podcast than in stories, but they are meant to be complimentary, not exclusive.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

About the author

Paul Ducklin is a passionate security proselytiser. (That's like an evangelist, but more so!) He lives and breathes computer security, and would be happy for you to do so, too. Paul won the inaugural AusCERT Director's Award for Individual Excellence in Computer Security in 2009. Follow him on Twitter: @duckblog