-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathminitalk.1
More file actions
46 lines (46 loc) · 1.09 KB
/
minitalk.1
File metadata and controls
46 lines (46 loc) · 1.09 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
.TH "MINITALK" "1" "July 2016" "Minitalk 0.2.3" ""
.SH NAME
.PP
minitalk \- small, simple chat system
.SH SYNOPSIS
.PP
minitalk FILE [NICK]
.SH DESCRIPTION
.PP
FILE File to use as "room".
Must have read/write permissions.
.PP
NICK Specify nick to use.
Default is current username.
.SH EXAMPLES
.PP
Join a room controlled via /var/chat/general.
.IP
.nf
\f[C]
$\ minitalk\ /var/chat/general
\f[]
.fi
.PP
The same, but specifying the username "admin".
.IP
.nf
\f[C]
$\ minitalk\ /var/chat/general\ admin
\f[]
.fi
.SH ISSUES
.PP
The primary issue is a security concern.
Anyone that needs to chat in the "room" has to be able to write to the control file. Anyone that needs read from the room needs read access. Anyone that has access to these "control" files can also inject anything they want into the chat. This truly is built on the honor system, and was designed around a single purpose: multi\-user chat between trusted users on a single host.
.PP
Don\[aq]t expect this to be secure.
.SH AUTHOR
.PP
Written by Andrew Benson.
.SH COPYRIGHT
.PP
Copyright © 2016 Andrew Benson.
License: MIT
.SH AUTHORS
Andrew Benson.