Changeset 3740:2a2a382c10ff in roaraudio for libroar
- Timestamp:
- 04/27/10 15:35:56 (14 years ago)
- Branch:
- default
- Phase:
- public
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
libroar/auth.c
r3517 r3740 30 30 * or libpulse*: 31 31 * The libs libroaresd, libroararts and libroarpulse link this lib 32 * and are therefore GPL. Because of this it may be ill igal to use32 * and are therefore GPL. Because of this it may be illegal to use 33 33 * them with any software that uses libesd, libartsc or libpulse*. 34 34 */ … … 45 45 * 5) if stage of server response is non-zero increment stage to server stage+1 46 46 * and repeat from step 2) 47 * 6) check if we got an OK or an ERROR, return c urrect value47 * 6) check if we got an OK or an ERROR, return correct value 48 48 */ 49 49 … … 64 64 * and no additional stage is needed. 65 65 * if the message type is OK the server accepted our auth. 66 * if the message type is ERROR the server re cjected us. we may try other auth methodes.66 * if the message type is ERROR the server rejected us. we may try other auth methods. 67 67 * if the server accepted our data and the stage is non-zero we need to continue with the next 68 68 * stage of the auth. … … 80 80 * --- COOKIE: 81 81 * We send cookies for all stages the server ask us to provide a cookie. 82 * if a cookie is wrong the server rejects us or a ks us for another.82 * if a cookie is wrong the server rejects us or asks us for another. 83 83 * The cookie is send as binary data in the data block. 84 84 * 85 85 * --- TRUST: 86 * We ask the server to auth us based on o wer UID/GID/PID.87 * The server may reject this beca sue we are not allowed or because it is not86 * We ask the server to auth us based on our UID/GID/PID. 87 * The server may reject this because we are not allowed or because it is not 88 88 * supported by the transport. 89 89 * If we get rejected we may try to continue with IDENT then RHOST before we use NONE. … … 91 91 * 92 92 * --- PASSWORD: 93 * This is techni kly the same as COOKIE just that the cookie is limited to93 * This is technically the same as COOKIE just that the cookie is limited to 94 94 * printable ASCII chars and that the user should be asked to provide the password. 95 95 * This may be done via a GUI popup window. … … 100 100 * The first part is a one byte long subtype. 101 101 * The value must be 0x01 for username+password. 102 * futur versions may define other types.103 * the sec und part is the actual data block.102 * future versions may define other types. 103 * the second part is the actual data block. 104 104 * for username+password it is splited into two fields, both terminated with \0. 105 105 * the first is the username the last one the password as clear text.
Note: See TracChangeset
for help on using the changeset viewer.