340 |
/* Initialize the PPP subsystem. */ |
/* Initialize the PPP subsystem. */ |
341 |
void pppInit(void); |
void pppInit(void); |
342 |
|
|
343 |
|
/* Warning: Using PPPAUTHTYPE_ANY might have security consequences. |
344 |
|
* RFC 1994 says: |
345 |
|
* |
346 |
|
* In practice, within or associated with each PPP server, there is a |
347 |
|
* database which associates "user" names with authentication |
348 |
|
* information ("secrets"). It is not anticipated that a particular |
349 |
|
* named user would be authenticated by multiple methods. This would |
350 |
|
* make the user vulnerable to attacks which negotiate the least secure |
351 |
|
* method from among a set (such as PAP rather than CHAP). If the same |
352 |
|
* secret was used, PAP would reveal the secret to be used later with |
353 |
|
* CHAP. |
354 |
|
* |
355 |
|
* Instead, for each user name there should be an indication of exactly |
356 |
|
* one method used to authenticate that user name. If a user needs to |
357 |
|
* make use of different authentication methods under different |
358 |
|
* circumstances, then distinct user names SHOULD be employed, each of |
359 |
|
* which identifies exactly one authentication method. |
360 |
|
* |
361 |
|
*/ |
362 |
enum pppAuthType { |
enum pppAuthType { |
363 |
PPPAUTHTYPE_NONE, |
PPPAUTHTYPE_NONE, |
364 |
|
PPPAUTHTYPE_ANY, |
365 |
PPPAUTHTYPE_PAP, |
PPPAUTHTYPE_PAP, |
366 |
PPPAUTHTYPE_CHAP |
PPPAUTHTYPE_CHAP |
367 |
}; |
}; |