INTL 3:770/1 3:770/3   
   REPLYADDR 68g.1499@etr6.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID: <8USdnewkyKXKIlz4nZ2dnZfqn_udnZ2d@earthlink.com> 785acb6d   
   REPLY:  06d5b47f   
   PID: SoupGate-Win32 v1.05   
   On 2/5/24 7:11 AM, Jesper Kaas wrote:   
   > Raspberrypi 5 running updated bookworm.   
   >   
   > Moving files between Windows and Pi'es was easy with VNC, but VNC   
   > server is gone in Bookworm. Moving files between Windows and Pi *can*   
   > be done with SCP, but everytime I have to check how to write the   
   > command corretly. Bad memory.   
      
      "Worm" is not really an 'upgrade' IMHO. More like some crap   
      contaminated by the Canonical philosophy. Deb should FIRE   
      those dinks. They made Worm the moral equiv of Vista.   
      
      However, there are several VNC servers you can install,   
      one is there kinda by default if you just use the rPI   
      config utility. I prefer tightvncserver. Note that   
      Tiger will subtly alter some deeply-obscure config   
      files under /etc which tends to keep OTHER VNC servers   
      from working right. After long searching I found what   
      needed to be changed back to default. SOME VNC servers   
      allow for cut-n-paste, some don't, some claim to but   
      don't always.   
      
      Also, for traditional file sharing, there's SAMBA server.   
      DO suggest manually adding 'winbind' and 'cifs-utils' to   
      the install. Plenty of docs on samba.conf and how to set   
      up shares/users - SOME of which are semi-comprehensible.   
      Copy examples, tweak to suit later. That's quickest.   
      
      The Samba config file is where you make shares 'visible'   
      or not. It sometimes works without winbind, sometimes   
      not, so DO co-install winbind.   
      
      Anyway, Samba is THE best way to share files to/from   
      a Pi or any other Linux system. NFS may be traditional   
      but it's WEIRD, funky to set up, potentially less   
      secure, NO faster really anymore and generally less   
      flexible than Samba. Note that the BSDs have an   
      older-spec Samba which may not easily employ the   
      more modern security features. Not a big deal on   
      an intranet, but a  possible PROBLEM for sharing   
      over the internet.   
      
      And for cheap file "sharing" there's always 'scp'.   
      DO change your SSH port to something non-standard   
      however. My firewalls doc infinite attempts on   
      the standard port, but nada elsewhere. The perps   
      are not movie-style hackers, just stupid bots   
      that don't waste time. There ARE some easy params   
      to tweak in the sshd config file to limit how   
      many attempts/sessions an outside agent might   
      attempt. Fail2Ban is also useful.   
      
      Did all this crap, often, for a mid-sized concern.   
      Nobody ever broke the system - not even a company   
      hired to find security weaknesses, even after offered   
      'special access' through the firewalls.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 15/0 19/38 90/1 105/81 106/201 128/260 129/305 135/225 153/7715   
   SEEN-BY: 218/700 226/30 227/114 229/110 112 113 200 206 307 317 400   
   SEEN-BY: 229/426 428 470 550 616 664 700 266/512 282/1038 291/111   
   SEEN-BY: 292/854 320/219 322/757 342/200 396/45 460/58 633/280 281   
   SEEN-BY: 633/412 418 420 509 2744 712/848 770/1 3 100 330 340 772/210   
   SEEN-BY: 772/220 230 5020/400 5075/35   
   PATH: 770/3 1 633/280 229/426