[Scan-DC] D.C. Fire/EMS: Planning for ENCRYPTION !!!

[Lee Williams]

Actually the first city of size to go full encryption that I know of was Jacksonville, FL well over 10 years ago. Florida as a state leads the nation with the most encrypted law enforcement communications to include the entire Florida Highway Patrol. 



 
> Date: Mon, 18 Nov 2013 05:15:38 -0500
> From: dewey3 at gmail.com
> To: binstockj at comcast.net
> CC: scan-dc at mailman.qth.net; alan at henney.com
> Subject: Re: [Scan-DC] D.C. Fire/EMS: Planning for ENCRYPTION !!!
> 
> Yes, Chief Lanier set that precedent here, but the first city I know of to
> go full encryption is Orlando, Florida... about 5 - 7 years before DC.
> There may be others who switched before, but Orlando is the first that I
> know of.  And I fully agree, Radio Reference has made a ton of money of off
> us while destroying the exact same hobby with the feeds!  Remember the
> battle between Lindsey and the Fed years ago about publishing the AAFB
> frequencies?
> On Nov 18, 2013 1:17 AM, "Jonathan Binstock" <binstockj at comcast.net> wrote:
> 
> > Alan:
> >
> > It appears that Chief Lanier set the precedent.  I sure hope there will be
> > some channels that will simulcast.  We are all aware of the homeland
> > security issues, but why can't they just keep the systems as is and encrypt
> > only the sensitive information?  If the concern is with criminals evading
> > the police via iPhone apps. or scanners, history shows that criminals
> > evaded
> > police WAY before scanners and iPhones.  Their cohorts can just as easily
> > text them the location of officers.  Lone criminals can always scope out
> > potential crime scenes themselves and figure ways to stay ahead of the law.
> >
> >
> > So why deprive the scanner community of a hobby and those who would use it
> > for beneficial purposes i.e. hearing a fire/ems call while in your car and
> > avoiding that area so that the apparatus can arrive safely or hearing the
> > description of a criminal suspect and protecting yourself and/or reporting
> > someone matching that description to law enforcement, thereby aiding in the
> > apprehension.
> >
> > New York, the city hit hardest (no pun intended by any means) on that
> > fateful day in 2011, still operates on their VHF channels for fire and UHF
> > for police.  No trunking, encryption, etc. and whatever city and suburban
> > systems are trunked, they are not encrypted and the only monitoring
> > problems
> > deal with reception issues i.e. steel buildings, RF, etc.
> >
> >
> > End of soapbox.
> >
> > Jonathan Binstock
> > NK3D
> >
> >
> >
> > -----Original Message-----
> > From: scan-dc-bounces at mailman.qth.net
> > [mailto:scan-dc-bounces at mailman.qth.net] On Behalf Of Alan Henney
> > Sent: Sunday, November 17, 2013 11:24 PM
> > To: Scan DC
> > Subject: [Scan-DC] D.C. Fire/EMS: Planning for ENCRYPTION !!!
> >
> >
> > We have heard from a couple different sources who are telling us that when
> > D.C. Fire/EMS switches to its new Motorola APX radios in early 2014, the
> > radio system will be encrypted!
> >
> > This will be another tremendous loss for the scanner community and another
> > horrible precedent.
> >
> > No doubt the embattled fire chief has taken some hard knocks the past year
> > and perhaps a few of those incidents could be attributed to what was
> > monitored on the radio.
> >
> > Specifically cited by one source was the Navy Yard shooting.  Audio
> > recordings from that incident were downloaded by the local media from
> > RadioReference, much to the anguish of fire/EMS officials.
> >
> > While I don't think it made the department look bad at all, it demonstrated
> > how they have lost control of who monitors and shares what is broadcast
> > from
> > FEMS radio channels --- but not for long?
> >
> > I'm frustrated by the continuing erosion of our hobby and the inability of
> > the public -- and especially the once mighty D.C. press corps -- to make
> > change.
> >
> > If anybody has the ability to change things in the D.C. government, now is
> > the time!
> >
> > Alan
> > ______________________________________________________________
> > Scan-DC mailing list
> > Home: http://mailman.qth.net/mailman/listinfo/scan-dc
> > Help: http://mailman.qth.net/mmfaq.htm
> > Post: mailto:Scan-DC at mailman.qth.net
> >
> > This list hosted by: http://www.qsl.net
> > Please help support this email list: http://www.qsl.net/donate.html
> >
> > ______________________________________________________________
> > Scan-DC mailing list
> > Home: http://mailman.qth.net/mailman/listinfo/scan-dc
> > Help: http://mailman.qth.net/mmfaq.htm
> > Post: mailto:Scan-DC at mailman.qth.net
> >
> > This list hosted by: http://www.qsl.net
> > Please help support this email list: http://www.qsl.net/donate.html
> >
> ______________________________________________________________
> Scan-DC mailing list
> Home: http://mailman.qth.net/mailman/listinfo/scan-dc
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Scan-DC at mailman.qth.net
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html