Re: In what ways can authentication (to server) fail?
Stefan Vetsch <[email protected]> Fri, 25 Feb 2011 11:32:52 +0100
| Newsgroups | gmane.network.silc.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Neale Am 24.02.2011 20:08, schrieb Neale Pickett: > 12:06:24 silc_packet_send_raw:1544: Sending packet CONNECTION AUTH (1) flags 0, src 2 dst 1, data len 4 How does your get_auth_method-Callback look like? There you have to specify which authentication-method you want to use. If you have copied your handler from the example (mybot.c), it is most likely set to SILC_AUTH_NONE (the CONNECTION AUTH data len is four bytes, which is exactly the size of an empty authentication payload). It's not complicated, you get the proposed authentication method as an argument to the callback (auth_method) you have to just pass it to the completion-function, that's it (the client library uses then the private key which you have supplied for signing). If you ever want to support password-based authentication then you have to gather the password by querying the user or reading it from a config file. Hope that helps. Best regards Stefan _______________________________________________________________________ Info: https://lists.silcnet.org/mailman/listinfo/silc-announce Archive: https://lists.silcnet.org/pipermail/silc-announce FAQ: http://silcnet.org/support/faq/