Linux Networking: Exploring Samba - page 5
The Samba Essentials
Samba can operate without any security or it can utilize any of a variety of security mechanisms integrated with Linux and Windows. This section presents the major options, but does not delve into all the details, as this is beyond the scope of this article. In general, a home or small business network may operate without any security. Security can be added later if necessary.
There are different ways to secure access to Samba resources. The first is with no security, so anyone can access resources. The second is to use account names. The third is to use names and passwords. In addition, the names and passwords can be maintained by Samba, Samba can use Linux names and passwords, or names and passwords from a Windows NT domain controller. It can also act as a Windows NT domain controller.
Resources can be managed at the user, share, server, or domain level. For small networks, the share level is often sufficient. In this case the shares have their own access passwords. User level management tends to be the easiest to manage.
There are many other features within Samba not covered in this article. For example, the NETLOGON support allows scripts to be executed on clients when they log onto the server to access resources. This is a necessary feature for larger networks, but it is often unused on smaller ones.
Solid state disks (SSDs) made a splash in consumer technology, and now the technology has its eyes on the enterprise storage market. Download this eBook to see what SSDs can do for your infrastructure and review the pros and cons of this potentially game-changing storage technology.
- 1Linux Top 3: GNOME 3.12 and New Betas for Ubuntu 14.04 and OpenMandriva Lx 2014.0
- 2Linux Top 3: Linus Lashes out, Linux 3.14 Gets PIE and Ubuntu One is Done.
- 3Linux Top 3: Ubuntu 14.04, Debian Gives Squeeze More Life and Red Hat Goes Atomic
- 4Linux Top 3: CoreOS, Oracle Enterprise Linux 7 and Ubuntu 14.10
- 5Linux Top 3: Debian Dumps SPARC, Ubuntu Takes Over Linux 3.13 and the Core Infrastructure Initiative