Second try gets it right

It seems some people still miss the point about my previous post — the focus is on the misleading PR approach, not the contents of the talk or speaker’s ability. So in that vein, let’s compare the two articles, both post-talk and pre-talk (same author, same publication, two weeks apart.)

First Article Second Article
Title New class of attack targets embedded devices” “New attack puts routers, cell phones at risk”
Major tech focus JTAG (no NULL pointers) NULL pointers (no JTAG)
Impact “criminals could … steal sensitive information from mobile phones or redirect Internet traffic on routers” “Jack plans to show how his attack could be used to make changes to the firmware of a router so that it injects a malicious code into any executable files downloaded from the Internet” (i.e. this talk)

The second article gets it right. It has enough details to know the general type of attack being discussed, downplays the hype, and lacks the misleading focus on JTAG. If the first article had never been written, I wouldn’t be discussing any of this.

The important thing to note is that the same author wrote both, so the only difference had to be the information that was provided to him. It was easy for me to recognize the PR influence since previous companies I’ve worked at have done the same thing. Security researchers, please make the effort to provide accurate details when announcing your talk, despite pressure from your PR department to overhype it or withhold information necessary to even know the topic.

Baysec meetup on May 16

Interested in meeting other infosec professionals? Not interested in a big commitment or sales pitch? Live in the SF Bay area? Then Baysec is for you!

We’ll be meeting on Wednesday, May 16 at 7 pm at Zeitgeist in San Francisco. We’ll grab a table, have some drinks, and chat about security. No sponsor currently so your tab is on you but that’s the only cost.

To find out more, join the low-traffic mailing list <baysec-subscribe at sockpuppet.org>. No RSVP needed unless you want someone to save you a seat.  Update: here’s the official announcement.

WOOT = Usenix + Blackhat

The call for papers is now up for a new Usenix workshop, WOOT (Workshop On Offensive Technologies, but don’t think the name came before the acronym.) The workshop will be co-hosted with Usenix Security and will focus on new practical attacks.

I was recently saying that vulnerability research could use more Peer Review instead of the other kind of PR (i.e., vague news stories, user-scaring Month of X Bugs). So help the community out here by submitting quality papers, especially if you’ve never submitted one before. I think the goal of bridging the gap between slideware (e.g., Blackhat) and 15th generation theoretical overlay network designs (e.g. Usenix Security) is a great one.

Also, I’m on the program committee but don’t hold that against them.

GPG now requires pinentry package

As a FreeBSD committer, I also run FreeBSD on a lot of my machines. I recently upgraded my desktop with portupgrade and found that gnupg no longer worked. I got the error message:

gpg-agent[13068]: can’t connect server: `ERR 67109133 can’t exec `/usr/local/bin/pinentry’: No such file or directory’
gpg-agent[13068]: can’t connect to the PIN entry module: IPC connect call failed
gpg-agent[13068]: command get_passphrase failed: No pinentry
gpg: problem with the agent: No pinentry

I found these two articles and noticed that my gpg had been upgraded from the 1.x to 2.x series. The 1.x gpg had an integrated password entry prompt but 2.x requires an external package. This can be fixed by installing the security/pinentry port. I’m not sure why it wasn’t marked as a dependency for gpg2.

# yes “hi” > /dev/kmem

Hi, I’m Nate and I’ll be writing about network, OS, and embedded security, cryptography, FreeBSD, and the occasional trip into retrocomputing. Here’s more detail on what this is all about.

What’s “rdist”? Well, only the keys to your kingdom from 1991 to about 1997. Closely following sendmail in terms of bug count, it was either your nightmare to support or a sign of easy root ahead. Go ahead and read the entire archives for some interesting history.