go-sendxmpp
- A tool to send messages to an XMPP contact or MUC.
go-sendxmpp
[-cdilnt] [-a value] [-f value] [--headline] [--help] [-h value] [-j value] [-m value] [--muc-password value] [--oob-file value] [--ox] [--ox-delete-nodes] [--ox-genprivkey-rsa] [--ox-genprivkey-x25519] [--ox-import-privkey value] [--ox-passphrase value] [-p value] [--raw] [--timeout value] [--tls-version value] [-u value] [--version] [recipients…]
A tool to send messages to an XMPP contact or MUC inspired by (but not as powerful as) sendxmpp
.
You can either pipe a programs output to go-sendxmpp
, write in your terminal (put ^D
in a new line to
finish) or send the input from a file (-m
or --message
).
The account data is expected at ~/.config/go-sendxmpp/config
(preferred), ~/.config/go-sendxmpp/sendxmpprc
(deprecated) ~/.sendxmpprc
(for compatibility with the original perl sendxmpp) if no other configuration
file location is specified with -f
or --file
.
-a
, --alias
=[value]-c
, --chatroom
=[value]-d
, --debug
-f
, --file
=[value]--headline
--help
-h
, --http-upload=
[value]-i
, --interactive
tail -f
).-j
, --jserver
=[value]-l
, --listen
-m
, --message
=[value]--muc-password
=[value]-n
, --no-tls-verify
--oob-file
=[value]--ox
--ox-delete-nodes
--ox-genprivkey-rsa
-u
and -p
)
and publish the corresponding public key.
Go-sendxmpp will save the key in $XDG_DATA_HOME/go-sendxmpp/oxprivkeys
or
$HOME/.local/share/go-sendxmpp/oxprivkeys
. To protect the key a passphrase might be set
using --ox-passphrase
while generating the key. --ox-import-privkey
.--ox-genprivkey-x25519
-u
and -p
)
and publish the corresponding public key.
Go-sendxmpp will save the key in $XDG_DATA_HOME/go-sendxmpp/oxprivkeys
or
$HOME/.local/share/go-sendxmpp/oxprivkeys
. To protect the key a passphrase might be set
using --ox-passphrase
while generating the key. --ox-import-privkey
.--ox-import-privkey
=[value]--ox-passphrase
=[value]--tls-version
=[value]-p
, --password
=[value]--raw
-c
and go-sendxmpp will join the MUC.--timeout=
[value]-t
, --tls
-u
, --username
=[value]--version
Go-sendxmpp supports Salted Challenge Response Authentication Mechanism (SCRAM).
If go-sendxmpp successfully connects using SCRAM it will create a file
~/.local/share/go-sendxmpp/[your_jid]/authmechanism
containing the name of the
used mechanism. It will read this file and use the same mechanism for future connections
and fail if it is not available. This is to protect against downgrades by a
Machine In The Middle (MITM). If you want to upgrade to another mechanism (e.g.
if SCRAM-SHA-1-PLUS gets available for your server that previously only supported
SCRAM-SHA-1) you have to manually edit the file. It is not recommended to delete
the file and let go-sendxmpp recreate it as this would make it vulnerable to downgrade
attacks for the next connection attempt.
There are no shell completions yet (contributions welcome) but for zsh it is
possible to automatically create completions from --help
which might work
good enough.
Just place the following in your ~/.zshrc
or ~/.zshrc.local
:
compdef _gnu_generic go-sendxmpp
Feel free to join https://join.jabber.network/#go-sendxmpp@chat.mdosch.de?join.
Written by Martin Dosch.
Report bugs at https://salsa.debian.org/mdosch/go-sendxmpp/issues.
Copyright (c) Martin Dosch License: BSD 2-clause License
go-sendxmpp(5), sendxmpp(1)