According to the Defcon 22 presentation, the most straightforward way to hack / disable an alarm system is to:
Find out the frequency the alarm system transmitter uses from publicly available FCC documentation.
Get a software defined radio, set it to that frequency to jam it.
Periodically, for very short periods of time, stop jamming to overcome / trick anti-jamming functionality in the system.
For those interested in reading the original research, see Logan Lamb's Defcon 22 whitepaper and presentation.
[White paper]: http://media.defcon.org/DEF%20CON%2022/DEF%20CON%2022%20presentations/Logan%20Lamb/DEFCON-22-Logan-Lamb-HOME-INSECURITY-NO-ALARMS-FALSE-ALARMS-AND-SIGINT-WP.pdf
[Presentation]: http://media.defcon.org/DEF%20CON%2022/DEF%20CON%2022%20presentations/Logan%20Lamb/DEFCON-22-Logan-Lamb-HOME-INSECURITY-NO-ALARMS-FALSE-ALARMS-AND-SIGINT.pdf
http://ipvm.com/report/hack-adt-alarm-system
(Score: 0, Offtopic) by Anonymous Coward on Tuesday January 27 2015, @08:39PM
Don't you just hate it when some (Windoze?) user puts white spaces in filenames so that each one expands to %20?
-- gewg_
(Score: 2) by frojack on Tuesday January 27 2015, @09:19PM
Don't you just hate it when some (Windoze?) user puts white spaces in filenames so that each one expands to %20?
Yeah, it can be annoying. (But its not unique to windowz).
Its posix-ly correct.
The actual %20 bit, (which causes no problems in the context for which it was intended - the web), but rather for the need to quote file names, or backslash every embedded space when dealing with them in 'Nix. Even in windows the spaces tended to break any batch files.
No, you are mistaken. I've always had this sig.
(Score: 2) by danomac on Tuesday January 27 2015, @11:38PM
Maybe early on, but newer versions of the shells in Windows (not just powershell) have autocomplete automatically put quotes around the file/folder name if there's a space in it. When using batch files, AFAICR Windows always supported encapsulating with quotes.
(Score: 0) by Anonymous Coward on Wednesday January 28 2015, @04:40AM
How does it know where the file name starts and ends? Sounds like it could be like all of the terrible msoffice 'you clearly wanted a space there' and 'sorry dave, i can't let you highlight that word without its trailing punctuation' stupidity.
(Score: 2) by danomac on Monday February 02 2015, @10:08PM
(Score: 0) by Anonymous Coward on Wednesday January 28 2015, @02:39AM
Yes%20I%20Hate%20It%20When%20They%20Do%20That.
(Score: 1) by poutine on Wednesday January 28 2015, @04:22PM
You're an idiot, it's %20 because that's what's required in a URL to be valid as ' ' is not a valid character in a URL. It has nothing to do with windows at all.
(Score: 0) by Anonymous Coward on Wednesday January 28 2015, @08:00PM
You're an idiot
On occasion. Not this time.
that's what's required
It's not required at all.
Smart people use a hyphen.
Some folks use CamelCase.
Some use an underscore (though that screws up Googleability as well).
A proper OS/DE doesn't allow whitespace in filenames because it's a stupid notion (dreamed up by MICROS~1).
Start with the fact that each one gets expanded to 3 characters.
-- gewg_
(Score: 0) by Anonymous Coward on Tuesday January 27 2015, @11:23PM
My CB radio used to set off alarms. Although it was running 100 watts (Stock max is 4 watts) with 120% modulation.
(Score: 0) by Anonymous Coward on Wednesday January 28 2015, @08:04AM
Bad anon coward!
Over-modulation causes harmonics that can pollute a lot of spectrum.