Re: Unable to Access Samba Shared Folder from Windows 10 Guest in virt-manager/QEMU Setup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2025-01-18 at 08:00 -0800, ToddAndMargo via users wrote:
> M$ has a bizarre way of stating such:
> 
>     Private: a hazardous environment with lots of
>              potential bad guys on the same network.
>              You are a network island and can see no
>              network resources except your Internet router
> 
>     Public: you trust everyone on the network.
> 
> It is intuitively backwards.  Almost every customer
> I have come across gets it backwards.

I wouldn't be surprised at anything they do, but if I look it up (such
as on the link below), I get the kind of thing that I *do* expect.

https://support.microsoft.com/en-au/topic/preventing-smb-traffic-from-lateral-connections-and-entering-or-leaving-the-network-c0541db7-2244-0dce-18fd-14a3ddeb282a

"Guest/Public (untrusted) networks
Name: Block outbound Guest/Public SMB 445
Description: Blocks all outbound SMB TCP 445 traffic when on an untrusted network
Action: Block the connection..."

"Private/Domain (trusted) networks
Name: Allow outbound Domain/Private SMB 445
Description: Allows outbound SMB TCP 445 traffic to only DCs and file servers when on a trusted network
Action: Allow the connection if it is secure..."

Which versions of Windows have you discovered have that backwards?

While I could understand some description of private meaning keeping
things private, and public as making things public (which I can only
ever remember seeing as FTP fileshare descriptions).  Everything I've
seen has always used private networking for your own space that is
secure and can be trusted, whereas being in public is risky and
untrusted.

-- 
 
uname -rsvp
Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 

-- 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux