The Panasonic R/W/T/Y series is a set of ultralight notebooks, also available in a US model. I like the Y4-Y7 for their large screen, light weight, and long battery life.
There are a couple things needed to get suspend/resume working on these models in FreeBSD. To get the backlight on and video working again, we need to trigger the 0xc000 video BIOS reset. Set the following in /etc/sysctl.conf:
The built-in mouse is stuck once we resume. We need to reinitialize it by setting the following in /boot/loader.conf. This should really be done automatically since the reinitialization should work on most systems. But more testing will have to be done before that is enabled by default.
With these changes, I can suspend/resume to RAM successfully. For more info, check the handbook.
We had a pretty good time at Zeitgeist but boy was it chilly. We’re going to try meeting inside this time at 21st Amendment, downtown SF. Date is June 20, 7 pm, details at http://www.sockpuppet.org/baysec/. See you there!
Comments Off on Next Baysec: June 20 at 21st Amendment
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.)
||“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)
||“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.