> From: Jeffrey Altman <[EMAIL PROTECTED]>
>
> jaltman> > ben> The ones I was referring to actually are static.
> jaltman> >
> jaltman> > Then they should not be a problem, and definitely not a source of
> jaltman> > clashing, should they?
> jaltman> >
> jaltman>
> jaltman> They are a problem because 'static' has no meaning to the linker.
> jaltman> They are functions in a library and if two libraries have overlapping
> jaltman> names spaces there will be problems.
>
> Yeah, but look again at what Ben writes. That's what I'm questioning,
> because if they were really static (as in defined with the key word
> "static"), we wouldn't have a problem, so that statement can't be
> true
Why do you say that?
Do you think "static" implies "inline"?
Here is the source code:
static void
DES_random_key(krb5_context context,
krb5_keyblock *key)
{
des_cblock *k = key->keyvalue.data;
do {
krb5_generate_random_block(k, sizeof(des_cblock));
des_set_odd_parity(k);
} while(des_is_weak_key(k));
}
static void
DES_schedule(krb5_context context,
struct key_data *key)
{
des_set_key(key->key->keyvalue.data, key->schedule->data);
}
static krb5_error_code
DES_string_to_key(krb5_context context,
krb5_enctype enctype,
krb5_data password,
krb5_salt salt,
krb5_keyblock *key)
{
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
