All of lore.kernel.org
 help / color / mirror / Atom feed
From: Klaus Singvogel <kssingvo@suse.de>
To: Johannes Meixner <jsmeix@suse.de>
Cc: printing-architecture@lists.linux-foundation.org,
	lsb-discuss@lists.linux-foundation.org
Subject: Re: [Printing-architecture] [lsb-discuss] LSB 4.0 and printing
Date: Thu, 27 Mar 2008 17:55:06 +0100	[thread overview]
Message-ID: <20080327165506.GA7647@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0803271634280.23932@nelson.suse.de>

Johannes Meixner wrote:
> 
> Have a network scanner (a scanner with ethernet connection)
> in an office for several people.

If the scanner has ethernet connection, any user can install drivers
on his _desktop_. No need to restrict installation on a _server_, or?

> Run the scanner driver (the SANE backend) together with
> the saned on an arbitrary server machine somewhere in
> a locked server room to have both the driver and the
> access permission stuff under full control of the admin
> of the central server.

What's the advantage of your model? It seems not very practicable and
a bit uncommon to me.

Restricting printing access is easy to explain: every single page
printed out costs resources (paper, toner, etc).

But scanning?

Why restricting a network scanner to special users and not to a
special, secure place? If there is no trust to all of the users, why
is the network scanner physical accessible to anyone, with danger of
thefts, and the scanning restricted to users? Why not locking the
scanner into a restricted room?

I neither see how you can prevent scanning by the bad guys, if the
scanner is still accessible by (physical) anyone and (by software)
through whole network?

I would suggest to setup a special desktop machine with limited
physical access in such an scenario into a special secured room. IMHO
more secure.

Another solution for your example might be to setup a a _desktop_
machine and use (in a limited way) as a server for above scenario. No
need to blow up all the other server machines with unnecessary scanner
software.

And I think it is a very limited, uncommon scenario you describe.
Let us stay at the more common real life examples, please.

> Run the scanning frontend together with the SANE "net"
> meta-driver on the individual user's workstation where
> it doesn't harm others if one user corrupts his workstation.

Workstation means a desktop machine right? So again: scanning with
SANE is done on the desktop machine.

Kindly regards,
	Klaus.
-- 
Klaus Singvogel
SUSE LINUX Products GmbH
Maxfeldstr. 5                     E-Mail: Klaus.Singvogel@SuSE.de
90409 Nuernberg                   Phone: +49 (0) 911 740530
Germany                           GnuPG-Key-ID: 1024R/5068792D  1994-06-27

SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)

  parent reply	other threads:[~2008-03-27 16:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47EA99E8.8020007@licquia.org>
2008-03-26 21:34 ` [Printing-architecture] [lsb-discuss] LSB 4.0 and printing Till Kamppeter
2008-03-27  8:48   ` Klaus Singvogel
     [not found]   ` <Pine.LNX.4.64.0803271421320.19740@nelson.suse.de>
2008-03-27 14:19     ` Klaus Singvogel
2008-03-27 14:29       ` Till Kamppeter
     [not found]       ` <Pine.LNX.4.64.0803271527300.20593@nelson.suse.de>
2008-03-27 15:31         ` Klaus Singvogel
     [not found]           ` <Pine.LNX.4.64.0803271634280.23932@nelson.suse.de>
2008-03-27 16:55             ` Klaus Singvogel [this message]
2008-03-27 17:42               ` Ira McDonald
2008-03-27 22:57                 ` Till Kamppeter
2008-03-28 14:02                   ` Klaus Singvogel
     [not found]               ` <Pine.LNX.4.64.0803281008280.14927@nelson.suse.de>
2008-03-28 16:09                 ` Klaus Singvogel
2008-03-27 22:23     ` Till Kamppeter
     [not found]   ` <20080326222308.GB7202@mit.edu>
     [not found]     ` <3F62CBEE02D6404E98C65934617EB582040A7A41@fmsmsx414.amr.corp.intel.com>
     [not found]       ` <20080326232809.GD7202@mit.edu>
2008-03-27 23:04         ` Till Kamppeter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080327165506.GA7647@suse.de \
    --to=kssingvo@suse.de \
    --cc=jsmeix@suse.de \
    --cc=lsb-discuss@lists.linux-foundation.org \
    --cc=printing-architecture@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.