[TrunkCom] can we decode encryption?

[Arthur-Bryan E. Phelps]

Encryption or even an ID can be changed remotely on all our two-way radios.
For a scanner, obviously not. I really have to emphasize the fact that
getting the key or an ID is risky--you just might get a visit from the feds
or local detectives. This information is CONFIDENTIAL. Even if you had that
information, the key could be changed at anytime and you would be back to
nothing. I don't know if an ID would be required for a non-tranmitting
device.  I would think not.

-----Original Message-----
From: trunkcom-bounces+aphelps=enter.net at mailman.qth.net
[mailto:trunkcom-bounces+aphelps=enter.net at mailman.qth.net] On Behalf Of
Jeff Kenyon
Sent: Monday, November 06, 2006 11:46 AM
To: Discussion of Monitoring Trunk Radio Systems
Subject: RE: [TrunkCom] can we decode encryption?

Even for radios that haven't been keyloaded or encrypted before all that is
sold separately.  Also, for larger fleets of radios you have OTAR that
manages all kekeys and distributes and changes them ovre the air.





On Mon, 6 Nov 2006, Arthur-Bryan E. Phelps wrote:

> Yes to both.  You would need an ANI board and they are not standard. 
> The ANI board and you would need both the software and hardware to 
> program the units.
>
> -----Original Message-----
> From: trunkcom-bounces+aphelps=enter.net at mailman.qth.net
> [mailto:trunkcom-bounces+aphelps=enter.net at mailman.qth.net] On Behalf 
> Of JERRY NONE
> Sent: Monday, November 06, 2006 11:26 AM
> To: Discussion of Monitoring Trunk Radio Systems
> Subject: Re: [TrunkCom] can we decode encryption?
>
> I guess one would also need the algorithmic code for the encryption or 
> the encrytpion code itself for a particular system.  Right?  One would 
> figure that each system out there has a different code plus that they 
> can rekey the code Over The Air.  Would the radio scanners also need 
> to have a radio ID for a particular system jsut like each radio has for
each system out there?
>
> --- Brian J Cathcart <scannerdude at juno.com> wrote:
>
> > On Fri, 3 Nov 2006 06:18:13 -0800 (PST) JERRY NONE 
> > <thepolishdude at yahoo.com> writes:
> > > Jeff, could you please explain the following:
> > > "This is where it would come in handy for a
> > scanner
> > > that can be keyloaded..."
> >
> > The keyloader is a device that loads the encryption key into the 
> > radio.
> > It plugs into the same port used for programming the radio itself 
> > but only loads the encryption key.  Jeff was saying it would be nice 
> > to include keyloading capability into a scanner, but that would also 
> > require having the encryption circuitry in the scanner (either 
> > built-in or an add-on module) and that would add significant cost to 
> > the scanner.
> >
> > --
> >
> > The Scanner Dude
> > Brian J. Cathcart - KE4PMJ
> > South Florida Frequency & Trunking Guide 10th Edition Available in 
> > both Printed and CD-ROM format http://www.scannerdude.com
> >
> ______________________________________________________________
> > TrunkCom mailing list
> > Home:
> > http://mailman.qth.net/mailman/listinfo/trunkcom
> > Help: http://mailman.qth.net/mmfaq.html
> > Post: mailto:TrunkCom at mailman.qth.net
> >
>
>
>
>
>
> ______________________________________________________________________
> ______
> ________
> Do you Yahoo!?
> Everyone is raving about the all-new Yahoo! Mail.
> http://new.mail.yahoo.com
> ______________________________________________________________
> TrunkCom mailing list
> Home: http://mailman.qth.net/mailman/listinfo/trunkcom
> Help: http://mailman.qth.net/mmfaq.html
> Post: mailto:TrunkCom at mailman.qth.net
>
> ______________________________________________________________
> TrunkCom mailing list
> Home: http://mailman.qth.net/mailman/listinfo/trunkcom
> Help: http://mailman.qth.net/mmfaq.html
> Post: mailto:TrunkCom at mailman.qth.net
>
______________________________________________________________
TrunkCom mailing list
Home: http://mailman.qth.net/mailman/listinfo/trunkcom
Help: http://mailman.qth.net/mmfaq.html
Post: mailto:TrunkCom at mailman.qth.net