{"schema_version":1,"metadata":{"branch":"current","release":"7.9","architecture":"amd64","generated_at":"2026-09-09T04:04:41.004595+00:00","source_url":"https://cdn.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/sqlports-7.55.tgz","source_sha256":"fcdbba1b9df747882aa9bab4af20ebec8dac10655069c90f1cd4145c06e1235e","package_count":12031,"source_kind":"sqlports"},"package":{"name":"silc-client-1.1.11p7","path":"net/silc-client","url":"/packages/current/net/silc-client/","comment":"Secure Internet Live Conferencing (SILC) client","homepage":"http://silcnet.org/client.html","maintainer":"Brad Smith <brad@comstyle.com>","description":"silc-client is a client for the SILC (Secure Internet Live Conferencing) \nprotocol.\n\nSILC (Secure Internet Live Conferencing) is a protocol which provides\nsecure conferencing services in the Internet over insecure channel.\n\nSILC superficially resembles IRC, although they are very different\ninternally. SILC is much more than just about `encrypting the traffic'.\nThat is easy enough to do with IRC and SSL hybrids, but even then the\nentire network cannot be secured, only part of it.\n\nSILC provides security services, such as sending private messages entirely\nsecure; noone can see the message except you and the real receiver of the\nmessage. SILC also provides same functionality for channels; noone except\nthose clients joined to the channel may see the messages destined to the\nchannel. Communication between client and server is also secured with\nsession keys and all commands, authentication data (such as passwords etc.)\nand other traffic is entirely secured. The entire network, and all parts of\nit, is secured.\n\nSILC has secure key exchange protocol that is used to create the session keys\nfor each connection. SILC also provides strong authentication based on either\npasswords or public key authentication. All authentication data is always\nencrypted in the SILC network. Each connection has their own session keys,\nall channels have channel specific keys, and all private messages can be\nsecured with private message specific keys.\n","package_architecture":"amd64","stem":"silc-client","readme":null,"dependencies":[{"path":"devel/glib2","type":"library","package_spec":"","url":"/packages/current/devel/glib2/"},{"path":"devel/metaauto","type":"build","package_spec":"","url":"/packages/current/devel/metaauto/"},{"path":"devel/autoconf/2.69","type":"build","package_spec":"","url":"/packages/current/devel/autoconf/2.69/"},{"path":"archivers/bzip2","type":"build","package_spec":"","url":"/packages/current/archivers/bzip2/"}],"reverse_dependencies":{"count":0,"url":null},"categories":["net"],"flavors":[],"only_for_architectures":[],"not_for_architectures":[]}}