source: code/trunk/doc/soju.1.scd@ 330

Last change on this file since 330 was 329, checked in by delthas, 5 years ago

Add support for the user create admin service command

This adds support for user create, a new service command only accessible
to admin users. This lets users create other users on the fly and makes
soju start the user routine immediately; unlike sojuctl which currently
requires closing soju, creating the user, and starting soju again.

File size: 5.5 KB
Line 
1soju(1)
2
3# NAME
4
5soju - IRC bouncer
6
7# SYNOPSIS
8
9*soju* [options...]
10
11# DESCRIPTION
12
13soju is a user-friendly IRC bouncer. It connects to upstream IRC servers on
14behalf of the user to provide extra features.
15
16- Multiple separate users sharing the same bouncer, each with their own
17 upstream servers
18- Clients connecting to multiple upstream servers via a single connection to
19 the bouncer
20- Sending the backlog (messages received while the user was disconnected from
21 the bouncer), with per-client buffers
22
23When joining a channel, the channel will be saved and automatically joined on
24the next connection. When registering or authenticating with NickServ, the
25credentials will be saved and automatically used on the next connection if the
26server supports SASL. When parting a channel with the reason "detach", the
27channel will be detached instead of being left.
28
29When all clients are disconnected from the bouncer, the user is automatically
30marked as away.
31
32soju supports two connection modes:
33
34- Single upstream mode: one downstream connection maps to one upstream
35 connection. To enable this mode, connect to the bouncer with the username
36 "<username>/<network>". If the bouncer isn't connected to the upstream
37 server, it will get automatically added. Then channels can be joined and
38 parted as if you were directly connected to the upstream server.
39- Multiple upstream mode: one downstream connection maps to multiple upstream
40 connections. Channels and nicks are suffixed with the network name. To join
41 a channel, you need to use the suffix too: _/join #channel/network_. Same
42 applies to messages sent to users.
43
44For per-client history to work, clients need to indicate their name. This can
45be done by adding a "@<client>" suffix to the username.
46
47# OPTIONS
48
49*-h, -help*
50 Show help message and quit.
51
52*-config* <path>
53 Path to the config file. If unset, a default config file is used.
54
55*-debug*
56 Enable debug logging (this will leak sensitive information such as
57 passwords).
58
59*-listen* <uri>
60 Listening URI (default: ":6697").
61
62# CONFIG FILE
63
64The config file has one directive per line.
65
66*listen* <uri>
67 Listening URI (default: ":6697").
68
69 The following URIs are supported:
70
71 - _[ircs://][host][:port]_ listens with TLS over TCP (default port if
72 omitted: 6697)
73 - _irc+insecure://[host][:port]_ listens with plain-text over TCP (default
74 port if omitted: 6667)
75 - _wss://[host][:port]_ listens for WebSocket connections over TLS (default
76 port: 443)
77 - _ws+insecure://[host][:port]_ listens for plain-text WebSocket
78 connections (default port: 80)
79
80 If the scheme is omitted, "ircs" is assumed. If multiple *listen*
81 directives are specified, soju will listen on each of them.
82
83*hostname* <name>
84 Server hostname (default: system hostname).
85
86*tls* <cert> <key>
87 Enable TLS support. The certificate and the key files must be PEM-encoded.
88
89*sql* <driver> <source>
90 Set the SQL driver settings. The only supported driver is "sqlite3". The
91 source is the path to the SQLite database file. By default, the path to the
92 database file is "soju.db".
93
94*log* <path>
95 Path to the bouncer logs root directory, or empty to disable logging. By
96 default, logging is disabled.
97
98*http-origin* <patterns...>
99 List of allowed HTTP origins for WebSocket listeners. The parameters are
100 interpreted as shell patterns, see *glob*(7).
101
102# IRC SERVICE
103
104soju exposes an IRC service called *BouncerServ* to manage the bouncer.
105Commands can be sent via regular private messages
106(_/msg BouncerServ <command> [args...]_). Commands may be written in full or
107abbreviated form, for instance *network* can be abbreviated as *net* or just
108*n*.
109
110*help* [command]
111 Show a list of commands. If _command_ is specified, show a help message for
112 the command.
113
114*network create* *-addr* <addr> [options...]
115 Connect to a new network at _addr_. _-addr_ is mandatory.
116
117 _addr_ supports several connection types:
118
119 - _[ircs://]host[:port]_ connects with TLS over TCP
120 - _irc+insecure://host[:port]_ connects with plain-text TCP
121
122 Other options are:
123
124 *-name* <name>
125 Short network name. This will be used instead of _addr_ to refer to the
126 network.
127
128 *-username* <username>
129 Connect with the specified username. By default, the nickname is used.
130
131 *-pass* <pass>
132 Connect with the specified server password.
133
134 *-realname* <realname>
135 Connect with the specified real name. By default, the nickname is used.
136
137 *-nick* <nickname>
138 Connect with the specified nickname. By default, the account's username
139 is used.
140
141*network delete* <name>
142 Disconnect and delete a network.
143
144*network status*
145 Show a list of saved networks and their current status.
146
147*certfp generate* *[options...]* <network name>
148 Generate self-signed certificate and use it for authentication.
149
150 Generates RSA-3072 private key by default.
151
152 Options are:
153
154 *-key-type* <type>
155 Private key algoritm to use. Valid values are: rsa, ecdsa, ed25519.
156 ecdsa uses NIST P-521 curve.
157
158 *-bits* <bits>
159 Size of RSA key to generate. Ignored for other key types.
160
161*certfp fingerprint* <network name>
162 Show SHA-1 and SHA-256 fingerprints for the certificate
163 currently used with the network.
164
165*certfp reset* <network name>
166 Disable SASL EXTERNAL authentication and remove stored certificate.
167
168*user create* -username <username> -password <password> [-admin]
169 Create a new soju user. Only admin users can create new accounts.
170
171*change-password* <new password>
172 Change current user password.
173
174# AUTHORS
175
176Maintained by Simon Ser <contact@emersion.fr>, who is assisted by other
177open-source contributors. For more information about soju development, see
178https://sr.ht/~emersion/soju.
Note: See TracBrowser for help on using the repository browser.