Re: [WEB REQ] /oper -pubkey but silc-client request a passphrase - Silc Server / Silc Client

[email protected] (Mika Bostrom)
Newsgroups gmane.network.silc.user
Message-ID <[email protected]>
On Sat, Oct 02, 2004 at 05:41:21PM +0200, Christoph Flügel wrote:
> 
> Software: Silc Server / Silc Client
> Operating System: Suse Linux 8.1 pro
> Installation: source
> 
> I have copied your basic server configuration but when i use the /oper
> command within the silc-client, the client ask after a passphrase. 

  Of course it does. Read below for more.

> My adminsection looks like 
> Admin {
>         PublicKey = \"/etc/silc/adminkeys/chris.pub\";
> };

  Yes, so you have set your own public as the server admin's key. This
is correct. As everything in SILC, authentication is done with standard
cryptographic challenge-response mechanism.

  In effect, the server sends your client a challenge, encrypted with
your public key. The client enforces a security measure and requires you
to verify that you indeed know the passphrase protecting your private
key. With right passphrase, the key is loaded and used to send a
response to server.

  So the passphrase you need to use is YOUR private key's passphrase.
The server only knows that it receives a response which it can verify
for true/false.

-- 
 Mika Boström      +358-40-525-7347  \-/  "World peace will be achieved
 [email protected]    www.iki.fi/bostik   X    when the last man has killed
 Security freak, and proud of it.    /-\   the second-to-last." -anon?

_______________________________________________________________
Info:    https://lists.silcnet.org/mailman/listinfo/silc-users
Archive: https://lists.silcnet.org/pipermail/silc-users
FAQ:     http://silcnet.org/support/faq/
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBXtD8v829VwOfGI4RAqshAJ9vlxkyumetdRBJ08AcJ41sGCtW1wCfa8++
y37CCuuJ8S64901BUfbIsWI=
=3auK
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.