Re: Available Encryption algorithms
> see http://en.wikipedia.org/wiki/A5/2 > as well as http://en.wikipedia.org/wiki/A5/1 > and http://en.wikipedia.org/wiki/A5/3 > > seems one doesn't want A5/2 anyways and its deprecated, thus eventually > the network doesn't allow using it anymore? That's true, > just guessing.. would need to work through a pile of calypso docs for > more details, and still not know whats implemented in that specific > revision of the ti-libs anyhow.. but after reading that i think a5/1 and > 5/3 will need to be enough till we need 3g anyhow. (when gsm gets phased > out, somewhere in the future or THC is successful ;) Reading the wikipedia pages you suggested, I noticed A5/3 is a 3G. It is quite odd and 2G phone/chip would support an 3G encryption algorithm Anyway, thanks for you input. I do not suspect you to work through a pile of calypso docs, I guess you've got better ways to spend you're time :-) grz, Onno signature.asc Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Available Encryption algorithms
just as a sidenote: see http://en.wikipedia.org/wiki/A5/2 as well as http://en.wikipedia.org/wiki/A5/1 and http://en.wikipedia.org/wiki/A5/3 seems one doesn't want A5/2 anyways and its deprecated, thus eventually the network doesn't allow using it anymore? just guessing.. would need to work through a pile of calypso docs for more details, and still not know whats implemented in that specific revision of the ti-libs anyhow.. but after reading that i think a5/1 and 5/3 will need to be enough till we need 3g anyhow. (when gsm gets phased out, somewhere in the future or THC is successful ;) -- Joachim Steiger Openmoko Central Services ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Available Encryption algorithms
> > I am a little confused about the available Encryption algorithms for the > > Neo1973. When I enter the ATcommand "AT%EM=2,7" in libgsmd-tool (in > > atcmd mode) it get the response: > > > > STR=`AT%EM=2,7' > > RSTR=`%EM: 1,1,0,3,0,1,1,0,0,1,1,0 > > 6,0,0,0,0,1,1,1,4,0,0,0,0,1,0,0,0,0' > > > > According to > > http://wiki.openmoko.org/wiki/GTA01_gsm_modem#Power_Parameters_.282.2C7.29 > > this should mean that A5/1 and A5/3 Encryption algorithms should be > > available. But all the information I found on the TI Calypso chipset state > > the ciphering processor implements both A5/1 and A5/2 algorithms. > > > > Can somebody confirm whether A5/2 of A5/3 is supported by the neo1973? > > The A5/* cyphers are used to encrypt voice data between the phone and the > base station. What cyphers you can use depends on what your phone and > network support. (In some countries consumer crypto is forbidden so all > GSM voice calls are in the clear). > > I don't actually know, but I would assume that both Neo 1973 and > Freerunner support whatever the GSM module supports. Remember that when > you make a voice call the analogue audio is routed from the mic directly > to the GSM module where it is digitized and sent over the network. The > Freerunner does not get involved. > > If there is a difference between what the spec sheet for the GSM modem > supports and what the AT command says is supported, then my guess would be > that the GSM modem is also considering what is permitted by the network & > SIM card. Alternatively there may be a bug in the OpenMoko software that > runs and interprets that AT command. > I assume the available Encryption algorithms are those that are supported by both the GSM Modem and the network. If the (un-mangled as jOERG pointed out) AT command says it is supported, the modes should be supported by the network and the GSM modem. Unfortunately, this brings me back to the original confusion. The documentation I found on the Calypso chip says A5/1 and A5/2 but interpreting the response of the AT command using the information in the wiki leads me to believe A5/1 and A5/3 is supported. Either the wiki or de documentation on the used Calypso chip is wrong. Since interpretation of the output on the wiki is based on "educated guesses and should not be relied on" I tent to believe the Calypso chip documentation. But maybe there is somebody with access to the closed (NDA) documentation, who can reliably confirm one or the other? grz, Onno ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Available Encryption algorithms
> Am Di 27. Mai 2008 schrieb David Pottage: > > If there is a difference between what the spec sheet for the GSM modem > > supports and what the AT command says is supported, then my guess would be > > that the GSM modem is also considering what is permitted by the network & > > SIM card. Alternatively there may be a bug in the OpenMoko software that > > runs and interprets that AT command. > > > > -- > > David Pottage > > Exactly (point #1). The raw AT-cmds aren't mangled by any OM-sw > (libgsmd-tool, > atcmd) AFAIK. > /jOERG But it could still be that the information on the wiki for interpreting the raw AT-cmds contains an error right? grz, Onno ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Available Encryption algorithms
Am Di 27. Mai 2008 schrieb David Pottage: > If there is a difference between what the spec sheet for the GSM modem > supports and what the AT command says is supported, then my guess would be > that the GSM modem is also considering what is permitted by the network & > SIM card. Alternatively there may be a bug in the OpenMoko software that > runs and interprets that AT command. > > -- > David Pottage Exactly (point #1). The raw AT-cmds aren't mangled by any OM-sw (libgsmd-tool, atcmd) AFAIK. /jOERG signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community