Regret can't get to the group. Should I be able to get Optical Character Recognition with Linux (Ubuntu)?
> From: [email protected] > Subject: dorset Digest, Vol 404, Issue 2 > To: [email protected] > Date: Tue, 4 Oct 2011 12:00:02 +0000 > > Send dorset mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.lug.org.uk/mailman/listinfo/dorset > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of dorset digest..." > > > Today's Topics: > > 1. Re: Locking down physical console access (David Wilkinson) > 2. Re: Locking down physical console access (Ralph Corderoy) > 3. Re: Locking down physical console access (Dan Dart) > 4. Re: Locking down physical console access (John Carlyle-Clarke) > 5. Re: Locking down physical console access (Ralph Corderoy) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 04 Oct 2011 09:50:46 +0100 > From: David Wilkinson <[email protected]> > Subject: Re: [Dorset] Locking down physical console access > To: Dorset Linux User Group <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 04/10/11 09:31, Chris Dennis wrote: > > > > The modern Ubuntu way of doing that may be to change the contents of > > /etc/init/tty[1-6].conf. > > > > I've changed tty1.conf on my MythTV front-end so that a user > > automatically logs in, but you could also prevent logins completely. > > > > On the other hand, I'm not an expert on this stuff, so you should > > confirm these ideas elsewhere. > > > > cheers > > > > Chris > > Hi > > I did try to disable the tty's but I was then unable to connect to the > server the server, it didn't respond to pings either so I am not sure if > fully booted up or not, so I had to boot up from a live CD and change > the files to allow tty's again. > > Just as thought is there away to prevent users from logging in locally > while allowing remote access via ssh as that might be easier. > > Thanks > > David > > > > > > ------------------------------ > > Message: 2 > Date: Tue, 04 Oct 2011 10:16:24 +0100 > From: Ralph Corderoy <[email protected]> > Subject: Re: [Dorset] Locking down physical console access > To: Dorset Linux User Group <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > Hi David, > > > > The modern Ubuntu way of doing that may be to change the contents of > > > /etc/init/tty[1-6].conf. > > > > I did try to disable the tty's but I was then unable to connect to the > > server the server, it didn't respond to pings either so I am not sure > > if fully booted up or not, so I had to boot up from a live CD and > > change the files to allow tty's again. > > How about disabling just tty3 through /etc/init/tty3.conf and seeing if > that works. If so, add the others and see when it stops working. > > Cheers, Ralph. > > > > ------------------------------ > > Message: 3 > Date: Tue, 4 Oct 2011 10:23:37 +0100 > From: Dan Dart <[email protected]> > Subject: Re: [Dorset] Locking down physical console access > To: Dorset Linux User Group <[email protected]> > Message-ID: > <CAACZMPacwM9+jvOGuRv3HwPYCng1jjDYLx3vRhqqnkjk5o=t...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > I believe some programs will stop working with a "no more ttys" error > - can you just not start the gettys but leave the ttys? Not sure I > have the correct terminology there - even don't start the login > processes? > > > > ------------------------------ > > Message: 4 > Date: Tue, 04 Oct 2011 10:36:22 +0100 > From: John Carlyle-Clarke <[email protected]> > Subject: Re: [Dorset] Locking down physical console access > To: Dorset Linux User Group <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 04/10/11 10:23, Dan Dart wrote: > > I believe some programs will stop working with a "no more ttys" error > > - can you just not start the gettys but leave the ttys? Not sure I > > have the correct terminology there - even don't start the login > > processes? > > > > Can you still make one of them a console? That might help. It would > also you you know what was going on. > > > > > ------------------------------ > > Message: 5 > Date: Tue, 04 Oct 2011 10:55:47 +0100 > From: Ralph Corderoy <[email protected]> > Subject: Re: [Dorset] Locking down physical console access > To: Dorset Linux User Group <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8 > > Hi David, > > John Carlyle-Clarke wrote: > > On 04/10/11 10:23, Dan Dart wrote: > > > I believe some programs will stop working with a "no more ttys" > > > error - can you just not start the gettys but leave the ttys? Not > > > sure I have the correct terminology there - even don't start the > > > login processes? > > > > Can you still make one of them a console? That might help. It would > > also you you know what was going on. > > Well, you could leave the getty(8)s running but use their -n option to > stop printing a login prompt and their -l option to alter the login > program they run (as root) to something that does nothing, e.g. displays > a message and sleeps endlessly. > > If it's OK for root to log in on a tty but no one else then nologin(5) > may be what you need. > > Cheers, Ralph. > > > > ------------------------------ > > _______________________________________________ > dorset mailing list > [email protected] > https://mailman.lug.org.uk/mailman/listinfo/dorset > > End of dorset Digest, Vol 404, Issue 2 > ************************************** -- Next meeting: Bournemouth, Tuesday 2011-10-04 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
