RVNC

I think I may just use the software RealVNC. I have used this in the past with windows. I'm trying to get a toe-hold with some of the things I know and expand from there.

I'm amazed with how these little boxes run. I have been computing for a while, even used an old MFM HDD, my first computer didn't even have a HDD... for first HDD was a 40 Meg, and it was almost kick ass.

Anyway, regressed.... learning lots. I'd like to test this out someday to see how many users I can get on before we notice any performance changes.

Thanx for your help!!!

IB JOE AKA Joe Schweier SysOp of Joe's Computer & BBS Telnet: joesbbs.com

Reply to
IB JOE
Loading thread data ...

Dana Fri, 22 Sep 2017 16:45:19 +1200, IB JOE napis'o:

Tunnel it through ssh for extra protection if you plan to put your machine on the Internet.

Reply to
Nikolaj Lazic

Hello Nikolaj,

Be aware to change the "default is your fault" password for user Pi immediately before connecting your Pi's to InterNet ! Because default SSH is set ON and anybody can login with the default password witch has ROOT capabilities! Change it to something cryptic, with at least one capital and one number and/or special character in it. Good luck with it. Greetings from Henri, a Raspbian Linux and RISC OS Pi 3B user.

Reply to
Henri Derksen

even better reconfigure ssh to require secure key authentication

it does not take much more effort than changing the password (which is still strongly recommended)

--
The main thing is the play itself.  I swear that greed for money has  
nothing 
 Click to see the full signature
Reply to
alister

my preference is tightvnc. It is possible to set up a VNC X11 desktop using the tightvnc server. This would work well for a headless system, but you should disable the "boot into GUI" default system if you do that, to avoid wasting RAM on two GUIs.

if you do this, you could try setting up the following file in the '.vnc' directory, once you have tightvnc installed

~/.vnc/xstartup

--
#!/bin/sh 

xrdb $HOME/.Xresources 
 Click to see the full signature
Reply to
Big Bad Bob

ideally, only enable ssh for specific users, then require them to 'su - pi' to access sudo. with a cryptic password on BOTH of them. And ONLY cryptic "non-dictionary-guessable" user names that can ssh in.

and never... EVAR... allow root to ssh in directly. ALWAYS require an 'su' or use of 'sudo' (with a password) for root-level access. The convenience setup would allow you to 'sudo su' to get a "root console" whenever you need it, so there ya go.

Reply to
Big Bad Bob

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.