Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
SILC (protocol)
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Components == {{IPstack}} The SILC protocol can be divided in three main parts: '''SILC Key Exchange''' (SKE) protocol, '''SILC Authentication protocol''' and '''SILC Packet protocol'''. SILC protocol additionally defines SILC Commands that are used to manage the SILC session. SILC provides channels (groups), nicknames, private messages, and other common features. However, SILC nicknames, in contrast to many other protocols (''e.g.'' [[IRC]]), are not unique; a user is able to use any nickname, even if one is already in use. The real identification in the protocol is performed by unique Client ID.<ref>{{Cite web |url=http://www.silcnet.org/general/about/features.php |title=SILC features |access-date=2008-02-20 |archive-url=https://web.archive.org/web/20080205035200/http://silcnet.org/general/about/features.php |archive-date=2008-02-05 |url-status=dead }}</ref> The SILC protocol uses this to overcome nickname collision, a problem present in many other protocols. All messages sent in a SILC network are binary, allowing them to contain any type of data, including text, video, audio, and other [[multimedia]] data. The SKE protocol is used to establish [[session key]] and other security parameters for protecting the SILC Packet protocol. The SKE itself is based on the [[Diffie–Hellman key exchange]] algorithm (a form of [[asymmetric cryptography]]) and the exchange is protected with [[digital signatures]]. The SILC Authentication protocol is performed after successful SKE protocol execution to authenticate a client and/or a server. The authentication may be based on [[passphrase]] or on [[digital signatures]], and if successful gives access to the relevant SILC network. The SILC Packet protocol is intended to be a secure binary packet protocol, assuring that the content of each [[packet (information technology)|packet]] (consisting of a packet header and packet payload) is secured and authenticated. The packets are secured using algorithms based on [[symmetric cryptography]] and authenticated by using [[Message Authentication Code]] algorithm, [[HMAC]]. SILC channels (groups) are protected by using symmetric channel keys. It is optionally possible to digitally sign all channel messages. It is also possible to protect messages with a privately generated channel key that has been previously agreed upon by channel members. Private messages between users in a SILC network are protected with session keys. It is, however, possible to execute SKE protocol between two users and use the generated key to protect private messages. Private messages may be optionally digitally signed. When messages are secured with key material generated with the SKE protocol or previously agreed upon key material (for example, [[passphrase]]s) SILC provides security even when the SILC server may be compromised.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)