![]()
Home security ?
Home automation robots just got a little more dangerous (?)
Policy wonk. Torontonian. Photographer. Not necessarily in that order.
![]()
Home security ?
Home automation robots just got a little more dangerous (?)
![]()
Charts: Sexy Ladies of the TSA
Don’t be alarmed..
This invasion of privacy is for your safety..
Trust us..
![]()
IBM’s efforts to add ‘intelligence’ to cities – and thus make them more manageable – is an ongoing effort. While what they’ve developed in Rio is interesting, I suspect that several facets of the ‘defence mechanism’ obfuscate residents’ economic realities.
Specifically, the video notes that residents of favelas may receive text messages that warn of oncoming disasters. This is good, but misses the point that a warning system without a capacity to absorb/protect residents who are fleeing poorly-build environments is effectively useless.
While the IBM ‘smart city’ project may make the city more intelligent, and improve daily operations, such intelligence doesn’t necessarily mean that the city can temporarily house residents of favelas in ‘safe’ areas of the city if a major disaster occurs. Unfortunately, the sale of technology in this video obfuscates this key truth of disaster preparation.
This is the kind of wacky security device that would lead to lawsuits if it worked and hilarity regardless of functionality.
![]()
I’ve tried to think of something comprehensive to say about the Facebook censorship rules for a few days now. I still don’t have something that really captures how absurd and offensive many of the items listed are. So, rather than give a holistic analysis of the document, here are a few thoughts:
Sex and Nudity
Hate Content
Graphic Content
Credible Threats
Those are some of my thoughts about this particular document. There are others that are still crystallizing and once/if I develop a full thought about the document I’ll be sure to post it.
Some of the reasons to be concerned about using unknown third-parties’ proxy services.
We should never forget that a large number of data/privacy breeches start from within a bureaucracy/organization. When an audit was performed on the drivers license database in Minnesota, auditors found that a staggering number of officers had ‘checked up’ on a woman’s profile. From the article on this:
The numbers were astounding: One hundred and four officers in 18 different agencies from around the state had accessed her driver’s license record 425 times in what could be one of the largest private data breaches by law enforcement in history.
The Department of Public Safety sent letters to all 18 agencies demanding an Internal Affairs investigation of the 104 officers. If the cops are found to be in violation of federal privacy law, they could be fired.
It isn’t enough to assume that the police are all knights in shining armour, incapable of doing wrong. No: they’re people, with all the expected foibles and failings. Give them information and powers and they will abuse them. The only questions are when and with what consequence.
A good paper on (you guessed it!) phishing on mobile devices. Paper is here (.pdf) and abstract is below.
We assess the risk of phishing on mobile platforms. Mobile operating systems and browsers lack secure application identity indicators, so the user cannot always identify whether a link has taken her to the expected application. We conduct a systematic analysis of ways in which mobile applications and web sites link to each other. To evaluate the risk, we study 85 web sites and 100 mobile applications and discover that web sites and applications regularly ask users to type their passwords into contexts that are vulnerable to spoofing. Our implementation of sample phishing attacks on the Android and iOS platforms demonstrates that attackers can spoof legitimate applications with high accuracy, suggesting that the risk of phishing attacks on mobile platforms is greater than has previously been appreciated.
A piece that was authored last September, enumerating some of the security issues with Google Chrome Extensions. The authors:
reviewed 100 Chrome extensions and found that 27 of the 100 extensions leak all of their privileges to a web or WiFi attacker. Bugs in extensions put users at risk by leaking private information (like passwords and history) to web and WiFi attackers. Web sites may be evil or contain malicious content from users or advertisers. Attackers on public WiFi networks (like in coffee shops and airports) can change all HTTP content. We’ll show you how you can prevent attacks on your extension using Content Security Policy.
In a followup, the authors have published a full report (here) that outlines their methodology and identifies the extensions that, as of February 2012, remain unpatched.
Check out the article, and some of the other great pieces that they’ve published on security.