NAME<\/a> saned \u2212 SANE network daemon<\/p>\n saned [ \u2212a<\/b> [ username ]<\/i> ] [ \u2212u<\/b> username<\/i> ] [ \u2212b<\/b> address<\/i> ] [ \u2212p<\/b> port<\/i> ] [ \u2212l ] [ \u2212D ] [ \u2212o ] [ \u2212d<\/b> n<\/i> ] [ \u2212e ] [ \u2212h ]<\/b><\/p>\n saned<\/b> is the SANE (Scanner Access Now Easy) daemon that allows remote clients to access image acquisition devices available on the local host.<\/p>\n saned<\/b> recognises the following options: is equivalent to the combination of \u2212l \u2212D \u2212u<\/b> username<\/i> options. However, username<\/i> is optional and running user will only be set when specified.<\/p>\n \u2212u<\/b> username<\/i>, \u2212\u2212user<\/b>=username<\/i><\/p>\n requests that saned<\/b> drop root privileges and run as the user (and group) associated with username<\/i> after binding.<\/p>\n \u2212b<\/b> address<\/i>, \u2212\u2212bind<\/b>=address<\/i><\/p>\n tells saned<\/b> to bind to the address<\/i> given.<\/p>\n \u2212p<\/b> port<\/i>, \u2212\u2212port=<\/b>port<\/i><\/p>\n tells saned<\/b> to listen on the port<\/i> given. A value of 0 tells saned<\/b> to pick an unused port. The default is the sane-port (6566).<\/b><\/p>\n \u2212l<\/b>, \u2212\u2212listen<\/b><\/p>\n requests that saned<\/b> run in standalone daemon mode. In this mode, saned<\/b> will listen for incoming client connections; inetd<\/b>(8) is not required for saned<\/b> operations in this mode.<\/p>\n \u2212D<\/b>, \u2212\u2212daemonize<\/b><\/p>\n will request saned<\/b> to detach from the console and run in the background.<\/p>\n \u2212o<\/b>, \u2212\u2212once<\/b><\/p>\n requests that saned<\/b> exits after the first client disconnects. This is useful for debugging.<\/p>\n \u2212d<\/b> n<\/i>, \u2212\u2212debug<\/b>=n<\/i><\/p>\n sets the level of saned<\/b> debug output to n<\/i>. When compiled with debugging enabled, this flag may be followed by a number to request more or less debug info. The larger the number, the more verbose the debug output. E.g., \u2212d128<\/b> will request output of all debug info. A level of 0 produces no output at all. The default value is 2.<\/p>\n \u2212e<\/b>, \u2212\u2212stderr<\/b><\/p>\n will divert saned<\/b> debug output to stderr instead of the syslog default.<\/p>\n \u2212h<\/b>, \u2212\u2212help<\/b><\/p>\n displays a short help message.<\/p>\n If saned<\/b> is run from other programs such as inetd<\/b>(8), xinetd<\/b>(8) and systemd<\/b>(1), check that program\u2019s documentation on how to pass command-line options.<\/p>\n First and foremost: saned<\/b> is not intended to be exposed to the internet or other non-trusted networks. Make sure that access is limited by tcpwrappers and\/or a firewall setup. Don\u2019t depend only on saned<\/b>\u2019s own authentication. Don\u2019t run saned<\/b> as root if it\u2019s not necessary. And do not<\/b> install saned<\/b> as setuid root.<\/p>\n The saned.conf<\/i> configuration file contains both options for the daemon and the access list. Specify the port range to use for the data connection. Pick a port range between 1024 and 65535; don\u2019t pick a too large port range, as it may have performance issues. Use this option if your saned<\/b> server is sitting behind a firewall. If that firewall is a Linux machine, we strongly recommend using the Netfilter nf_conntrack_sane<\/i> module instead.<\/p>\n data_connect_timeout<\/b> = timeout<\/i><\/p>\n Specify the time in milliseconds that saned<\/b> will wait for a data connection. Without this option, if the data connection is not done before the scanner reaches the end of scan, the scanner will continue to scan past the end and may damage it depending on the backend. Specify zero to have the old behavior. The default is 4000ms.<\/p>\n The access list is a list of host names, IP addresses or IP subnets (CIDR notation) that are permitted to use local SANE devices. IPv6 addresses must be enclosed in brackets, and should always be specified in their compressed form. Connections from localhost are always permitted. Empty lines and lines starting with a hash mark (#) are ignored. A line containing the single character \u2018\u2018+\u2019\u2019 is interpreted to match any hostname. This allows any remote machine to use your scanner and may present a security risk, so this shouldn\u2019t be used unless you know what you\u2019re doing.<\/p>\n A sample configuration file is shown below:<\/p>\n # Daemon options The case of the host names does not matter, so AHost.COM is considered identical to ahost.com.<\/p>\n For saned<\/b> to work properly in its default mode of operation, it is also necessary to add the appropriate configuration for xinetd<\/b>(8), inetd<\/b>(8) or systemd<\/b>(1) (see below). Note that your inetd<\/b>(8) must support IPv6 if you want to connect to saned<\/b> over IPv6; xinetd<\/b>(8), openbsd-inetd<\/b>(8) and systemd<\/b>(1) are known to support IPv6, check the documentation for your inetd<\/b>(8) daemon.<\/p>\n In the sections below the configuration for inetd<\/b>(8), xinetd<\/b>(8) and systemd<\/b>(1) are described in more detail.<\/p>\n For the configurations below it is necessary to add a line of the following form to \/etc\/services<\/i>:<\/p>\n sane\u2212port 6566\/tcp # SANE network scanner daemon<\/p>\n The official IANA short name for port 6566 is “sane\u2212port”. The older name “sane” is now deprecated.<\/p>\n It is required to add a single line to the inetd<\/b>(8) configuration file (\/etc\/inetd.conf)<\/i><\/p>\n The configuration line normally looks like this:<\/p>\n sane\u2212port stream tcp nowait saned.saned \/usr\/sbin\/saned saned<\/p>\n However, if your system uses tcpd<\/b>(8) for additional security screening, you may want to disable saned<\/b> access control by putting \u2018\u2018+\u2019\u2019 in saned.conf<\/i> and use a line of the following form in \/etc\/inetd.conf<\/i> instead:<\/p>\n sane\u2212port stream tcp nowait saned.saned \/usr\/sbin\/tcpd \/usr\/sbin\/saned<\/p>\n Note that both examples assume that there is a saned<\/b> group and a saned<\/b> user. If you follow this example, please make sure that the access permissions on the special device are set such that saned<\/b> can access the scanner (the program generally needs read and write access to scanner devices).<\/p>\n If xinetd<\/b>(8) is installed on your system instead of inetd<\/b>(8) the following example for \/etc\/xinetd.conf<\/i> may be helpful:<\/p>\n # default: off saned<\/b> can be compiled with explicit systemd<\/b>(1) support. This will allow logging debugging information to be forwarded to the systemd<\/b>(1) journal. The systemd<\/b>(1) support requires compilation with the systemd-devel package installed on the system. This is the preferred option.<\/p>\n saned<\/b> can be used with systemd<\/b>(1) without the systemd<\/b>(1) integration compiled in, but then logging of debug information is not supported.<\/p>\n The systemd<\/b>(1) configuration is different for the 2 options, so both are described below.<\/p>\n For systemd<\/b>(1) configuration we need to add 2 configuration files in \/etc\/systemd\/system<\/i>.<\/p>\n The first file we need to add here is called saned.socket.<\/i> It shall have the following contents:<\/p>\n [Unit] [Socket] [Install] The second file to be added is saned@.service<\/i> with the following contents:<\/p>\n [Unit] [Service] [Install] You need to set an environment variable for SANE_CONFIG_DIR<\/b> pointing to the directory where saned<\/b> can find its configuration files. You will have to remove the # on the last line and set the variables for the desired debugging information if required. Multiple variables can be set by separating the assignments by spaces as shown in the example above.<\/p>\n Unlike xinetd<\/b>(8) and inetd<\/b>(8), systemd<\/b>(1) allows debugging output from backends set using SANE_DEBUG_XXX<\/b> to be captured. See the man-page for your backend to see what options are supported. With the service unit as described above, the debugging output is forwarded to the system log.<\/p>\n This configuration will also work when saned<\/b> is compiled WITH systemd<\/b>(1) integration support, but it does not allow debugging information to be logged.<\/p>\n For systemd<\/b>(1) configuration for saned<\/b>, we need to add 2 configuration files in \/etc\/systemd\/system<\/i>.<\/p>\n The first file we need to add here is called saned.socket.<\/i> It is identical to the version for systemd<\/b>(1) with the support compiled in. It shall have the following contents:<\/p>\n [Unit] [Socket] [Install] The second file to be added is saned@.service<\/i>. This one differs from the version with systemd<\/b>(1) integration compiled in:<\/p>\n [Unit] [Service] Environment=SANE_CONFIG_DIR=\/etc\/sane.d<\/p>\n [Install] \/etc\/hosts.equiv<\/i><\/p>\n The hosts listed in this file are permitted to access all local SANE devices. Caveat: this file imposes serious security risks and its use is not recommended.<\/p>\n \/etc\/sane.d\/saned.conf<\/i><\/p>\n Contains a list of hosts permitted to access local SANE devices (see also description of SANE_CONFIG_DIR<\/b> below).<\/p>\n \/etc\/sane.d\/saned.users<\/i><\/p>\n If this file contains lines of the form<\/p>\n user:password:backend<\/p>\n access to the listed backends is restricted. A backend may be listed multiple times for different user\/password combinations. The server uses MD5 hashing if supported by the client.<\/p>\n SANE_CONFIG_DIR<\/b><\/p>\n This environment variable specifies the list of directories that may contain the configuration file. On *NIX systems, the directories are separated by a colon (\u2018:\u2019), under OS\/2, they are separated by a semi-colon (\u2018;\u2019). If this variable is not set, the configuration file is searched in two default directories: first, the current working directory (“.”) and then in \/etc\/sane.d<\/i>. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explicitly specified directories. For example, setting SANE_CONFIG_DIR<\/b> to “\/tmp\/config:” would result in directories tmp\/config<\/i>, .<\/i>, and \/etc\/sane.d<\/i> being searched (in this order).<\/p>\n sane<\/b>(7), scanimage<\/b>(1), xscanimage<\/b>(1), xcam<\/b>(1), sane\u2212dll<\/b>(5), sane\u2212net<\/b>(5), sane\u2212”backendname”<\/b>(5), inetd<\/b>(8), xinetd<\/b>(8), systemd<\/b>(1) David Mosberger<\/p>\n saned \u2212 SANE network daemon <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,4,546],"class_list":["post-3418","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-man8","tag-saned"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3418","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3418"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3418\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3418"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3418"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3418"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
CONFIGURATION<\/a>
SERVER DAEMON CONFIGURATION<\/a>
INETD CONFIGURATION<\/a>
XINETD CONFIGURATION<\/a>
SYSTEMD CONFIGURATION<\/a>
Systemd configuration for saned with systemd support compiled in<\/a>
Systemd configuration when saned is compiled without systemd support<\/a>
FILES<\/a>
ENVIRONMENT<\/a>
SEE ALSO<\/a>
AUTHOR<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
OPTIONS <\/a> <\/h2>\n
\u2212a<\/b> [username]<\/i>, \u2212\u2212alone<\/b>[=username]<\/i><\/p>\nCONFIGURATION <\/a> <\/h2>\n
data_portrange<\/b> = min_port<\/i> – max_port<\/i><\/p>\n
data_portrange = 10000 – 10100
# Access list
scan\u2212client.somedomain.firm
# this is a comment
192.168.0.1
192.168.2.12\/29
[::1]
[2001:db8:185e::42:12]\/64<\/p>\nSERVER DAEMON CONFIGURATION <\/a> <\/h2>\n
INETD CONFIGURATION <\/a> <\/h2>\n
XINETD CONFIGURATION <\/a> <\/h2>\n
# description: The sane server accepts requests
# for network access to a local scanner via the
# network.
service sane\u2212port
{
port = 6566
socket_type = stream
wait = no
user = saned
group = saned
server = \/usr\/sbin\/saned
}<\/p>\nSYSTEMD CONFIGURATION <\/a> <\/h2>\n
Systemd configuration for saned with systemd support compiled in <\/a> <\/h2>\n
Description=saned incoming socket<\/p>\n
ListenStream=6566
Accept=yes
MaxConnections=1<\/p>\n
WantedBy=sockets.target<\/p>\n
Description=Scanner Service
Requires=saned.socket<\/p>\n
ExecStart=\/usr\/sbin\/saned
User=saned
Group=saned
StandardInput=null
StandardOutput=syslog
StandardError=syslog
Environment=SANE_CONFIG_DIR=\/etc\/sane.d
# If you need to debug your configuration uncomment the next line and
# change it as appropriate to set the desired debug options
# Environment=SANE_DEBUG_DLL=255 SANE_DEBUG_BJNP=5<\/p>\n
Also=saned.socket<\/p>\nSystemd configuration when saned is compiled without systemd support <\/a> <\/h2>\n
Description=saned incoming socket<\/p>\n
ListenStream=6566
Accept=yes
MaxConnections=1<\/p>\n
WantedBy=sockets.target<\/p>\n
Description=Scanner Service
Requires=saned.socket<\/p>\n
ExecStart=\/usr\/sbin\/saned
User=saned
Group=saned
StandardInput=socket<\/p>\n
Also=saned.socket<\/p>\nFILES <\/a> <\/h2>\n
ENVIRONMENT <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n
http:\/\/www.penguin-breeder.org\/?page=sane\u2212net<\/i><\/p>\nAUTHOR <\/a> <\/h2>\n
\n","protected":false},"excerpt":{"rendered":"