Servidor de arquivo [RESOLVIDO]

1. Servidor de arquivo [RESOLVIDO]

Eduardo
revenge79

(usa Ubuntu)

Enviado em 21/12/2011 - 14:27h

Boa Tarde

Alguem poderia me ajudar em uma seguinte situação,

eu estava querendo conhecer o linux, instalei em uma máquina virtual o ubuntu, caçando daqui, dali no google, em foruns e tal, deixei funcional, bom dai quis abusar, quis instalar um servidor de arquivos, fuçando daqui e dali, consegui instalar o samba, agora que vem o pepino

Criei 2 pastas com nomes "todos" e "particular", e 2 grupos, "publico" e "pessoal" criei, 2 usuários, "X" e "Y"

Queria que o "X" só tivesse acesso ao diretório "Todos" e o "Y" a ambos os diretórios, dai nomamente em foruns consegui, definindo os grupo "publico" no usuário "X" e o usuário "Y" com ambos os grupos, e com o comando chown coloquei o grupo "publico" como proprietario do diretório "todos" e o grupo "pessoal" proprietário do diretório "particular" apliquei o comando chmod 770 que pelo que li é permissao total para o dono da pastas e o grupo da pasta

Achei que estava tudo ok, porém ambos os usuarios conseguem criar diretorios e arquivos e exclui-los independente de quem criou, porem os arquivos não consigo alterar/editar, apenas quem criou o arquivo....

depois caçando mais um pouco achei q solucionei meus prolemas pois existia as permissoes especiais. Bom, como nao entendi bem como elas funcionam, entao configurei umas por uma, e achei que iria funcionar, porem, continuava a mesma coisa, configurei deste jeito chmod *770
onde estrela é que cada hora substitui pela permissao especial ou seja 4, 2 e 1
SUID 4
SGUID 2
STICKY 1

Masn ao importa o que eu faço, se o usuário X ou Y criam um arquivo de texto por exemplo, o outro não consegue acrescentar informações e vice versa, to quase desistindo ja rs


Abraços a todos e desculpem pelo texto longo



  


2. Re: Servidor de arquivo [RESOLVIDO]

Ricardo Libanio
riesdra

(usa Debian)

Enviado em 21/12/2011 - 16:59h

posta o arquivo smb.conf




3. Re: Servidor de arquivo [RESOLVIDO]

Eduardo
revenge79

(usa Ubuntu)

Enviado em 21/12/2011 - 18:19h

riesdra escreveu:

posta o arquivo smb.conf



Estou postando, mas como falei nao sei mexer no linux, so de curioso, de videos, google e foruns, tudo que fiz foi via terminal, nao cheguei nem mexer nesse arquivo, ele está original do sistema


# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home director as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# The following parameter makes sure that only "username" can connect
#
# This might need tweaking when using external authentication schemes
; valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom






4. Re: Servidor de arquivo [RESOLVIDO]

Reginaldo de Matias
saitam

(usa Slackware)

Enviado em 21/12/2011 - 19:57h

Dê uma conferida no tutorial de configuração samba no em: http://mundodacomputacaointegral.blogspot.com/2011/10/configurar-servidor-samba-no-linux.html


5. Re: Servidor de arquivo [RESOLVIDO]

Ricardo Libanio
riesdra

(usa Debian)

Enviado em 22/12/2011 - 10:33h

Eduardo,

este arquivo que você postou não tem os compartilhamentos citados, é o padrão, de acordo com este arquivo nem existe os compartilhamentos.

segue mais uns links para leitura;

http://www.hardware.com.br/tutoriais/samba-swat/
http://www.hardware.com.br/tutoriais/samba-configuracao-avancada/
http://www.hardware.com.br/tutoriais/samba-pdc/


a questão de liberar gravação no samba para um grupo, vai ser a opção write list = @grupo, configure isto dentro da sessão do compartilhamento de sua pasta.



6. Re: Servidor de arquivo [RESOLVIDO]

Eduardo
revenge79

(usa Ubuntu)

Enviado em 22/12/2011 - 10:52h

É verdade eu não configurei nada via smb.conf
todos os comandos que fui lendo em foruns e tal, foram feitos via terminal eo compartilhamento ta Ok, funcionando.
E o compartilhamento em si, fui na pasta e cliquei com o direito e tinha o "compartilhar pasta"
Mas vou dar mais uma lidar sobre esse tal arquivo e ve se aparece algo novo, tambem pesquisando li sobre uma tal de umask, que acho que tambem cai no meu prolemas

Mas vlw gente


7. Re: Servidor de arquivo [RESOLVIDO]

Ricardo Libanio
riesdra

(usa Debian)

Enviado em 22/12/2011 - 12:08h

Eduardo,

acrescente isto ao seu arquivo
#########################################################################################
[todos]
comment= público
browseable = yes
path = /local-onde-esta-no-sistema
read only = no
create mask = 0770
directory mask = 0770
writable = yes

[particular]
comment= privado
browseable = yes
path = /local-onde-esta-no-sistema
read only = no
create mask = 0770
directory mask = 0770
writable = yes
valid users = +pessoal
#########################################################################################

troque a linha path, pelo caminho esta sua pasta
verifique se os nomes das pastas e dos grupos de acordo com o exemplo.

salve o arquivo, reinicie o samba e faça o teste.



8. Re: Servidor de arquivo [RESOLVIDO]

Eduardo
revenge79

(usa Ubuntu)

Enviado em 22/12/2011 - 13:52h

Eu fiz como pediu mas nao deu certo ´
o mais louco é que os usuários que criei conseguem criar diretoria e arquivos, e apagarem um do outro, independente de quem criou, mas nao conseguem edita-los.........muito doido isso
vou pesquisar mais sobre esse arquivo de configuração do smb.conf, que sou iniciante, nao sei se os comandos que havia digitado no terminal anteriormente, entram em conflito com o arquivo smb.conf que estou colocando agora,,,,,,usuário novo é assim desconfia de tudo e nao tenho noçao de linux, mas vou continuar tentando aqui


9. Re: Servidor de arquivo [RESOLVIDO]

Ricardo Libanio
riesdra

(usa Debian)

Enviado em 22/12/2011 - 14:11h

Eduardo,

instale o swat, e configure por ele, pode ser mais fácil para você.




10. Re: Servidor de arquivo [RESOLVIDO]

Eduardo
revenge79

(usa Ubuntu)

Enviado em 23/12/2011 - 08:34h

Acho que vou instalar esse aplicativo sim
Esse negocio ta estranho demais
eu vi que todos os arquivos os arquivo e diretorios dentro do grupo sao do proprietario, e nao do grupo, como queria, apesar do comando chmod -R os arquivos que serao criados sao do proprietario nativo. Agora nao entendo onde ta a segurança nisso? pos se eu crio uma pasta ou um arquivo o cara nao pode editar ou alterar, mas pode deletar, que é o que ta acontecendo aqui......
Isso ta ficando complicado demais rs



11. Re: Servidor de arquivo [RESOLVIDO]

Eduardo
revenge79

(usa Ubuntu)

Enviado em 24/12/2011 - 12:45h

Pessoal
Mexendo daqui e mexendo dali resolvi o problema do compartilhamento, o problema que estava o correndo era o seguinte
o diretorio de compartilhamento criado estava OK, porém os arquivos criados além por um determinado usuário alem dele mesmo ser o proprietario, o grupo tambem estava saindo em nome do usuário tipo
usuario X criou um arquivo e a propriedade era o seguinte proprietario X grupo X
Entao pesquisei sore grupos primarios e encontrei o comando usermod -g usuário grupo.
E coloquei ele no grupo q queria, entao todo arquivo criado agora é editavel pelo grupo.
So que vem a seguinte questao se eu coloco o usuário em um outro grupo, todoas os arquivos criados vao continuar com o grupo primario, dando o mesmo erro para outros usuários que nao pertecencem ao grupo primario.....
Tem algum comando no smb.conf que caso eu criei um arquivo em um diretorio ja preconfigurado com o grupo, por exemplo, "linux" tudo criado la saia com as permissoes herdadas do diretorio, e nao do usuário criador?







Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts