INTL 3:770/1 3:770/3   
   REPLYADDR 68g.1499@etr6.net   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  2cdd04a6   
   REPLY:  33610a5e   
   PID: SoupGate-Win32 v1.05   
   On 2/6/24 4:16 AM, Jesper Kaas wrote:   
   > On 06.02.2024 06:10, 68g.1499 wrote:   
   >> 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.   
   >   
   > Unforunately only the RealVNC Viewer can be activated. Not the server.   
      
      
      Um ... have TightVNCServer running on four PIs at my   
      home right now - three Bullseye and one Worm.   
      
      Never activate the default VNC server ... go to Synaptic   
      or something and install Tight. It will ask if you want   
      to uninstall the other, say yes.   
      
      Anyway, it works.   
      
      DID warn about Tiger sneakily changing some config files   
      in ways that DOES block some other VNC servers ...   
      
      
   > Anyway, after following Bob Lathams guide I can see the raspi shares in   
   > windows, so by now there is no reason to hunt for a better VNC server.   
   > Put perhaps restrict the access to all files on the raspberrypi.   
      
      
      VNC is not really made to "share" files/folders ... it's   
      a remote-desktop thing. As said, use SAMBA if you want to   
      share files/folders cleanly.   
      
      
   >>    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.   
   >   
   > Well I started reading about winbind, and it looks way more complicated > to   
   install (and use) than I can manage.   
      
      
      On SOME distros, SAMBA just would not work right unless   
      winbind was there - although NO extra configuration was   
      ever needed. Try it without winbind first.   
      
      
   >>    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.   
   >   
   > Thanks for your thorough comments   
   >   
   > Best regards   
   >   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225   
   SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 112 113 200 206 307 317 400 426   
   SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038   
   SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364   
   SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100   
   SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426