milenage usage
Harald Welte
laforge at gnumonks.org
Wed Jul 18 19:33:33 CEST 2012
Hi Max,
On Thu, Jul 19, 2012 at 12:50:24AM +0800, ☎ wrote:
> I've noticed that unlike a5.h and comp128.h (include/osmocom/gsm), milenage.h is
> located in "src/gsm/milenage/" and thus is not included into .deb packages.
the debian packages are not really maintained, we're happy if you want
to improve their status.
> What are the reasons for that and how milenage should be used properly?
neither comp128v1 nor milenage should be used directly. Thei idea is
that an application shouldn't care or know about the detailed
algorithms. It should all be handled by the library in a generic way.
They should be used via the generic osmo_auth api. both the comp128v1
and the milenage plugin are registering themselves via
osmo_auth_register().
>From the application, you can call
osmo_auth_load()
osmo_auth_supported()
osmo_auth_gen_vec()
osmo_auth_gen_vec_auts()
osmo_auth_alg_name()
osmo_auth_alg_parse()
You can check the libosmocore/utils/osmo-auc-gen.c example on how they
are used to generate authentication truplets or quintuples.
OpenBSC predates this generic API and should be updated. Once again,
contributions are welcome.
Regards,
Harald
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
More information about the baseband-devel
mailing list