with-authinfo-kludge.1: Don't bother digging into the password database.
[with-authinfo-kludge] / with-authinfo-kludge.1
CommitLineData
b3370918
MW
1.\" -*-nroff-*-
2.\"
3.\" Manual page for `with-authinfo-kludge'.
4.\"
5.\" (c) 2016 Mark Wooding
6.\"
7.
8.\"----- Licensing notice ---------------------------------------------------
9.\"
10.\" This program is free software; you can redistribute it and/or modify
11.\" it under the terms of the GNU General Public License as published by
12.\" the Free Software Foundation; either version 2 of the License, or
13.\" (at your option) any later version.
14.\"
15.\" This program is distributed in the hope that it will be useful,
16.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
17.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
18.\" GNU General Public License for more details.
19.\"
20.\" You should have received a copy of the GNU General Public License
21.\" along with this program; if not, write to the Free Software Foundation,
22.\" Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
23.
24.ie t \{\
25. ds o \(bu
26.\}
27.el \{\
28. ds o o
29.\}
30.
31.de hP
32.IP
33\h'-\w'\fB\\$1\ \fP'u'\fB\\$1\ \fP\c
34..
35.
36.de VS
37.sp 1
38.RS
39.nf
40.ft B
41..
42.de VE
43.ft R
44.fi
45.RE
46.sp 1
47..
48.
49.TH with-authinfo-kludge 1 "23 April 2016"
50.
51.\"--------------------------------------------------------------------------
52.SH NAME
53with-authinfo-kludge \- run a newsreader with AUTHINFO GENERIC support
54.
55.SH SYNOPSIS
56with-authinfo-kludge
57.RB [ \-v ]
58.RB [ \-d
59.IR dir ]
60.RB [ \-f
61.IR conf ]
62.RB [ \-t
63.IR tag ]
64.br
65\h'5m'\c
66[
67.BI + server
68.RI [ param \fR= value
69\&...] \&...]
70.RB [ + ]
71.br
72\h'5m'\c
73.I command
74.RI [ args
75\&...]
76.
77.\"--------------------------------------------------------------------------
78.SH DESCRIPTION
79.
80The
81.B with-authinfo-kludge
82program is an
83.I adverbial modifier
84which runs another command
85(typically a newsreader)
86in an environment in which at can,
87transparently to it,
88make connections to certain NNTP servers
89which usually require
90.B AUTHINFO GENERIC
91authentication before they'll permit clients to read or post.
92This is useful because support for
93.B AUTHINFO GENERIC
94has never been especially widely supported by newsreaders
95and now seems to be being withdrawn from those newsreaders
96which used to support it.
97.PP
98In the simple case, you say something like
99.VS
100with-authinfo-kludge slrn
101.VE
102and then
103.B slrn
104will start up,
105connect to your default NNTP server
106(as named in the
107.B NNTPSERVER
108environment variable),
109authenticate to it as needed,
110and let you read and post news.
111In more complicated cases,
112.B with-authinfo-kludge
113can handle multiple NNTP servers,
114set up SSH forwarding for them,
115offer different authentication credentials to them,
116and hide the fact that they might be running on nonstandard ports.
117.PP
118The
119.B with-authinfo-kludge
120program doesn't do all of this itself:
121it depends on some other tools existing on the system in which it runs.
122(It doesn't need anything special running on the server system.)
123The external dependencies are as follows.
124.hP \*o
125The
126.B authinfo-kludge
127program, by Richard Kettlewell,
128is a simple proxy which relays commands and responses
129between the client (on stdin/stdout) and server (over TCP),
130and responds transparently to authentication requests from the server.
131.hP \*o
132The
133.B noip
134hack, by Mark Wooding,
135is an
136.B LD_PRELOAD
137library which selectively uses Unix-domain sockets
138in place of IPv4 or IPv6 sockets.
139.
140.SS "Command line"
141The
142.B with-authinfo-kludge
143program accepts a small number of options
144before its main command-line arguments.
145.TP
146.B \-h
147Write help about the command-line syntax to standard output,
148and exit with status zero.
149.TP
150.BI "\-d " dir
151Use
152.I dir
153as the `runtime directory',
154which is used to store sockets and other working files
155while
156.B with-authinfo-kludge
157is running.
158By default, it will choose an appropriate place
159in a moderately complicated manner described below;
160this option lets you override its choice
161in order to achieve special effects.
162.TP
163.BI "\-f " conf
164Read configuration from
165.IR conf .
166The default is somewhat complicated;
167see below.
168.TP
169.BI "\-t " tag
170Use
171.I tag
172to distinguish this usage of
173.B with-authinfo-kludge
174from others.
175The tag is used to select default configuration files
176and runtime directories.
177By default, the basename of the
178.I command
179is used.
180.TP
181.B "\-v"
182Print messages explaining what
183.B with-authinfo-kludge
184is doing to standard error.
185By default,
186.B with-authinfo-kludge
187does its thing silently unless there are problems.
188.PP
189The
190.I command
191argument names the command which should be run
192with the various proxy arrangements which it is the task of
193.B with-authinfo-kludge
194to arrange; it will be passed the
195.IR args ,
196if any.
197The command name and arguments are not subject to
198interpretation by the shell;
199if, for some reason, you wanted to make use of shell features,
200you should specify a command of the form
201.B /bin/sh
202.B \-c
203.IR shell-fragment .
204.PP
205Between the options (if any) and the
206.I command
207name,
208there may be a number of server configurations.
209If any are present, they take the place of any configuration file:
210an error is reported if a
211.B \-f
212option was passed.
213A server configuration starts with
214an argument consisting of a server name prefixed by a
215.RB ` + '
216character:
217.IP
218.BI + server
219.PP
220This may be followed by assignments
221.IP
222.IB param = value
223.PP
224which set configuration parameters
225for the previously-named server.
226Such a server configuration on the command line
227is treated exactly the same as a configuration-file section
228.IP
229.BI [ server ]
230.br
231.IB param = value
232.br
233\&...
234.PP
235See below for details about the configuration file.
236.PP
237To hedge against the unlikely event that the desired
238.IR command 's
239name actually begins with
240.RB ` + ',
241an argument consisting of a
242.RB ` + '
243sign on its own marks the end of the server configurations:
244the following argument will be interpreted as the command name
245regardless of its syntactic form.
246If there is a
247.RB ` + '
248marker, but no server configurations,
249then the configuration file is read,
250or the default configuration is used,
251as usual.
252.
253.SS "Configuration file"
254The
255.B with-authinfo-kludge
256program reads configuration from a standard-ish
257.RB ` .ini '-format
258file.
259The file consists of parameter settings of the form
260.IP
261.I param
262.B =
263.I value
264.PP
265divided into sections by headers of the form
266.IP
267.BI [ name ]
268.PP
269Whitespace around the
270.IR name ,
271.I param
272and
273.I value
274strings is discarded.
275A section
276.I name
277may itself contain square brackets,
278and they need not be properly nested.
279There is no syntax for continuing values over more than one line.
280.PP
281The file may also contain blank lines,
282and comment lines whose first non-whitespace character is either
283.RB ` # '
284or
285.RB ` ; '.
286All such lines are ignored.
287.PP
288Parameter settings apply to the section named in the most recent
289setion header.
290Settings appearing before the first section header apply to
291the special section named
292.BR @GLOBAL ,
293just as if a line
294.IP
295.B [@GLOBAL]
296.PP
297appeared at the very top of the file.
298It is permitted (though not usually expected)
299for several section headers to have the same name;
300in this case,
301all of the settings following any of the occurrences are gathered together,
302just as if they'd all appeared under a single header,
303in the same order.
304If the same parameter is assigned more than once,
305then only the
306.I last
307assignment has any effect.
308.PP
309With the exception of the
310.B @GLOBAL
311section,
312each section header should name an NNTP server.
313.PP
314The following server parameters are recognized.
315.TP
316.BI local= host\fR[ : port \fR]
317Sets the NNTP server address which the newsreader command
318expects to connect to.
319This does
320.I not
321have to be an address local to the machine on which
322.B with-authinfo-kludge
323runs.
324It defaults to the
325.I server
326name from the section heading
327(which must therefore be in the appropriate format),
328and may be equal to the
329.I remote
330address (below) without causing difficulty.
331.TP
332.BI nntpauth= "parameter arguments\fR..."
333Set the AUTHINFO GENERIC authentication parameter and arguments
334to use for this server.
335The default is to use the settings from the
336.B NNTPAUTH
337environment variable.
338.TP
339.BI remote= host\fR[ : port \fR]
340Sets the real address of the NNTP server which
341.BR with-authinfo-kludge 's
342proxy (or the SSH tunnel) should connect to.
343It defaults to the
344.I server
345name from the section heading
346(which must therefore be in the appropriate format).
347.TP
348.BI sshbind= host\fR[ : port\fR]
349Change the address and port number
350of the local end of the SSH tunnel
351set up by the
352.B via
353parameter.
354The default is to use
355127.1.0.1:119.
356It is
357.I not
358a problem for multiple servers to use the same address:
359.B with-authinfo-kludge
360uses the
361.BR noip (1)
362library to keep them
363separate.
364.TP
365.BI via= gateway
366Use SSH connection forwarding to reach the server.
367The
368.I gateway
369is passed to
370.BR ssh (1)
371as its hostname parameter,
372so may be a hostname or IP address,
373possibly prefixed by
374.IB user @
375to choose a different login name;
376or it may name a
377.BR ssh_config (1)
378stanza providing detailed configuration.
379Note that the local end of the tunnel will
380.I not
381be exposed to other users of the local machine,
382since this instance of SSH is run under the control of
383.BR noip (1).
384.PP
385The various parameters which take network addresses
386accept a common syntax:
387.IP
388.IR host \c
389.RB [ : \c
390.IR port ]
391.PP
392The
393.I host
394may be a hostname;
395an IPv4 address in dotted-quad notation; or
396an IPv6 address in hex-and-colons notation,
397which must contain at least
398.I two
399colons to be valid.
400Raw IP addresses may be surrounded by square brackets;
401this is necessary to disambiguate a trailing
402.BI : port
403following an IPv6 address because the IPv6 address syntax is stupid.
404.PP
405The
406.B @GLOBAL
407section may set the following parameters.
408.TP
409.BI rundir= dir
410Set the runtime directory to be
411.IR dir .
412This directory (but not its parent directories)
413will be created automatically if necessary.
414The default runtime directory is chosen in a complicated way;
415see below.
416.PP
417The configuration file is found as follows.
418.hP 1.
419If server configurations are provided on the command line,
420then they are used instead of any configuration file.
421.hP 2.
422If a
423.B \-f
424option is given, then it is read as a configuration file.
425A fatal error is reported if the file does not exist,
426or cannot be read for some other reason.
427.hP 3.
428The user's home directory is determined, as follows.
429If the environment variable
430.B HOME
431is set, then its value is used.
b3370918
MW
432Let
433.I home
434be the home directory so determined, if any.
435.hP 4.
436A `configuration home' directory is determined, as follows.
437If the environment variable
438.B XDG_CONFIG_HOME
439is set, then its value is used.
440Otherwise, the configuration home is
441.IB home /.config \fR;
442a fatal error is reported at this point
443if no home directory was determined.
444Let
445.I config-home
446denote the configuration home directory so determined.
447.hP 5.
448A `tag' is chosen, as follows.
449If the
450.B \-t
451option is given, then its value is used;
452otherwise the tag is the basename of the
453.I command
454(i.e., the part following the last
455.RB ` / ',
456if any).
457Let
458.I tag
459denote the tag so chosen.
460.hP 6.
461If
462.IB config-home /with-authinfo-kludge/ tag .conf
463exists, then it is read as a configuration file.
464(If it can't be read, then a fatal error is reported.)
465.hP 7.
466If
467.IB config-home /with-authinfo-kludge/@default.conf
468exists, then it is read as a configuration file.
469(If it can't be read, then a fatal error is reported.)
470.hP 8.
471No configuration file could be found,
472so a default configuration is constructed, as follows.
473Let
474.I nntp-server
475be the value of the
476.B NNTPSERVER
477environment variable;
478if it is not set, then a fatal error is reported.
479The default configuration is as follows.
480.RS
481.IP
482.BI [ nntp-server ]
483.RE
484.
485.SS "The runtime directory"
486(This section is technical, and can safely be skipped by most users.
487It may be useful to know this stuff if
488.B with-authinfo-kludge
489is behaving confusingly and you're trying to understand why.)
490.PP
491The runtime directory is chosen as follows.
492.hP 1.
493If the
494.B \-d
495option is present, then its value is used.
496.hP 2.
497If the environment variable
498.B XDG_RUNTIME_DIR
499is set, then let
500.I run
501denote its value;
502then
503.IB run /with-authinfo-kludge
504is used as the runtime directory.
d9c763dc 505.hP 3
b3370918
MW
506If the environment variable
507.B TMPDIR
508is set, then let
509.I tmp
510be its value;
511otherwise, let
512.I tmp
513be
514.BR /tmp .
d9c763dc
MW
515Let
516.I uid
517be the current effective uid, in decimal,
518without leading zeroes
519(if the superuser is foolish enough to run this program then
520.I uid
521is
522.BR 0 ).
b3370918 523If
d9c763dc 524.IB tmp/ with-authinfo-kludge- uid
b3370918
MW
525exists,
526is a directory (and not a symbolic link),
527is owned by the current effective uid,
528and has no permissions for group or others;
529or if it does not exist but can be created with the above properties;
530then it is used as the runtime directory.
d9c763dc 531.hP 4.
b3370918
MW
532The user's home directory is determined, as follows.
533If the environment variable
534.B HOME
535is set, then its value is used.
b3370918
MW
536Let
537.I home
538be the home directory so determined, if any.
d9c763dc 539.hP 5.
b3370918
MW
540A `cache home' directory is determined, as follows.
541If the environment variable
542.B XDG_CACHE_HOME
543is set, then its value is used.
544Otherwise, the configuration home is
545.IB home /.cache \fR;
546a fatal error is reported at this point
547if no home directory was determined.
548Let
549.I cache-home
550denote the cache home directory so determined.
551If the cache home directory does not exist,
552then it is created with mode 0777 (as modified by the umask).
d9c763dc 553.hP 6.
b3370918
MW
554Let
555.I hostname
556be the local machine's hostname,
557as reported by
558.BR gethostname (2).
559If
560.IB cache-home /with-authinfo-kludge. hostname
561does not exist,
562then it is created as a directory,
563with mode 0700 (and modified by the umask).
564This directory is then used as the runtime directory.
565(If it exists, but is not in fact a directory,
566then later operations will fail.)
567.PP
568The runtime directory contains a number of other directories,
569named
570.IR tag . pid \fR.
571Each such directory corresponds to a running
572(or failed)
573instance of
574.BR with-authinfo-kludge ;
575the
576.I pid
577is its process-id (possibly useful for diagnostic purposes),
578and the
579.I tag
580is the tag summarizing its purpose
581(as determined in step 5 of the procedure
582for finding a configuration file).
583.PP
584The contents of the instance directory are as follows.
585.TP
586.B client.pid
587The process-id of the client command run by
588.BR with-authinfo-kludge .
589.TP
590.B lock
591An empty file.
592A
593running
594.B with-authinfo-kludge
595process holds a lock on this file.
596It is used simply to tell other processes that
597the directory is still in use and shouldn't be cleaned up.
598.TP
599.B noip/
600A directory containing Unix-domain sockets,
601maintained by the
602.B noip
603library.
604.TP
605.B ssh.pid
606The process-id of the SSH process started to satisfy a
607.B via
608server parameter.
609.
610.\"--------------------------------------------------------------------------
611.SH BUGS
612.
613The program is probably too complicated for many uses,
614but the author finds the various bells and whistles useful.
615.PP
616There isn't a good way to get two or more NNTP clients
617to share the same proxy machinery.
618This is somewhat wasteful.
619Fixing this would necessitate some other way of
620orchestrating the setup and teardown of runtime directories.
621.PP
622Maybe there ought to be a way to set
623a separate runtime directory for each server.
624But, really, I had to draw a line somewhere.
625.
626.\"--------------------------------------------------------------------------
627.SH SEE ALSO
628.
629.BR authinfo-kludge (1),
630.BR noip (1).
631.PP
632S. Barber,
633.IR "RFC2980, Common NNTP Extensions",
634.if !t \{\
635.br
636\h'5m'\c
637.\}
638.BR "https://www.ietf.org/rfc/rfc2980.txt" .
639.
640.SH AUTHOR
641Mark Wooding,
642<mdw@distorted.org.uk>
643.
644.\"----- That's all, folks --------------------------------------------------