summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2012-06-25s3:smb2_sesssetup: implement dynamic re-authentication and expire sessionsStefan Metzmacher2-6/+129
metze
2012-06-25docs-xml: document "server max protocol" SMB3 and SMB3_00Stefan Metzmacher1-1/+10
metze
2012-06-25docs-xml: fix reference from "server min protocol" to "server max protocol"Stefan Metzmacher1-1/+1
metze
2012-06-25selftest/Samba3: 'server max protocol = SMB3'Stefan Metzmacher1-1/+1
metze
2012-06-25lib/param: add "SMB3" as alias for PROTOCOL_SMB3_00Stefan Metzmacher1-0/+1
metze
2012-06-25s3:smbd: remove now unused invalidate_all_vuids()Stefan Metzmacher2-10/+0
Pair-Programmed-With: Michael Adam <obnox@samba.org> metze
2012-06-25s3:smbd: remove now unused conn_close_all()Michael Adam2-16/+0
Pair-Programmed-With: Stefan Metzmacher <metze@samba.org>
2012-06-25s3:smbd: use smbXsrv_session_logoff_all() and smb1srv_tcon_disconnect_all() ↵Michael Adam1-4/+32
in exit_server_common() This removes the use of conn_close_all() and invalidate_all_vuids() Pair-Programmed-With: Stefan Metzmacher <metze@samba.org>
2012-06-25s3:smbd: make use of smbXsrv_session for smb1Stefan Metzmacher6-274/+194
Pair-Programmed-With: Michael Adam <obnox@samba.org> metze
2012-06-25s3:smbd: make use of smbXsrv_tcon for smb1Stefan Metzmacher10-170/+183
Pair-Programmed-With: Michael Adam <obnox@samba.org> metze
2012-06-25s3:smbd: make use of smbXsrv_tcon and smbXsrv_session for smb2Stefan Metzmacher20-275/+180
The removes the protocol specific smbd_smb2_session and smbd_smb2_tcon. Pair-Programmed-With: Michael Adam <obnox@samba.org> metze
2012-06-25s3:smb2_sesssetup: add support for SMB 2.24/3.00 signingStefan Metzmacher1-0/+29
metze
2012-06-25s3:smb2_sesssetup: make use of the smbXsrv_session infrastructureStefan Metzmacher4-63/+138
We still have smbd_smb2_session as primary structure, but that will went away once we got rid of smbd_smb2_tcon. metze
2012-06-25s3:smbXsrv_session: init and disconnect smbXsrv_tcon for SMB2/3Stefan Metzmacher1-0/+20
metze
2012-06-25s3:smbd: add smbXsrv_tcon infrastructureStefan Metzmacher5-1/+1180
Pair-Programmed-With: Michael Adam <obnox@samba.org> metze
2012-06-25s3:smbXsrv.idl: add smbXsrv_tcon* structuresStefan Metzmacher1-0/+63
struct smbXsrv_tcon will represent a SMB 1 or SMB 2 tree connect. It will replace 'struct smbd_smb2_tcon' and 'connection_struct' will be changed to handle just the protocol independent glue for the SMB_VFS layer. metze
2012-06-25sq smbXsrv_session_global_store no connectionStefan Metzmacher1-6/+3
2012-06-25s3:smbd: add smbXsrv_session infrastructureStefan Metzmacher5-0/+1164
Pair-Programmed-With: Michael Adam <obnox@samba.org> metze
2012-06-25s3:smbXsrv.idl: add smbXsrv_session* structuresStefan Metzmacher1-0/+92
struct smbXsrv_session will represent a SMB 1 or SMB 2 session. It will replace 'struct smbd_smb2_session' and 'user_struct' will be changed to handle just the protocol independent glue for the SMB_VFS layer. metze
2012-06-25s3:smbd: add smbXsrv_version_* infrastructureStefan Metzmacher5-0/+272
metze
2012-06-25s3:librpc/idl/smbXsrv.idl: add smbXsrv_version_* structuresStefan Metzmacher1-1/+65
metze
2012-06-25s3:librpc: add smbXsrv.idlStefan Metzmacher6-2/+23
metze
2012-06-25s3:test: make shell code more porable by elimnating "local" keywordBjörn Jacke1-4/+4
don't use "local". That is BASH only. Autobuild-User(master): Björn Jacke <bj@sernet.de> Autobuild-Date(master): Mon Jun 25 19:02:13 CEST 2012 on sn-devel-104
2012-06-25s3: Fix a typoVolker Lendecke3-4/+4
Signed-off-by: Stefan Metzmacher <metze@samba.org> Autobuild-User(master): Stefan Metzmacher <metze@samba.org> Autobuild-Date(master): Mon Jun 25 17:13:59 CEST 2012 on sn-devel-104
2012-06-25s3: Avoid a call to server_event_context()Volker Lendecke1-1/+1
Signed-off-by: Stefan Metzmacher <metze@samba.org>
2012-06-24s4-join: Setup correct DNS configurationAndrew Bartlett2-28/+76
This means we do not need to run samba_upgradedns any more. Andrew Bartlett Autobuild-User(master): Andrew Bartlett <abartlet@samba.org> Autobuild-Date(master): Sun Jun 24 18:10:10 CEST 2012 on sn-devel-104
2012-06-25s4-samba_upgradedns: Do not set DNS account for internal serverAndrew Bartlett1-32/+32
The internal DNS server does not need the samba-only NAME-dns account. Andrew Bartlett
2012-06-25s4-join: Import DNS zones in AD DC joinAndrew Bartlett3-20/+59
2012-06-24selftest: Test unix.whoami with kerberos on plugin_s4_dcAndrew Bartlett3-18/+10
This also tests the comparison with LDAP on anonymous connections and marks this as knownfail, while we investigate the correct behaviour here. Andrew Bartlett
2012-06-24s4-classicupgrade: Allow DNS backend to be specifiedAndrew Bartlett2-6/+12
2012-06-24s4-drepl: Ensure that the op->source does not get deallocated too earlyAndrew Bartlett2-9/+25
We need to have the struct dreplsrv_partition_source_dsa around until the end of the async op, so we use talloc_reference after carefully checking the callers and making the modifications required. This prevents a crash when replicating partitions in the vampire_dc test after adding DNS replication at join time. Andrew Bartlett
2012-06-23selftest: schema is not automatically reloaded now so if you modify it you ↵Matthieu Patou1-0/+9
have to reload it Autobuild-User(master): Matthieu Patou <mat@samba.org> Autobuild-Date(master): Sat Jun 23 10:48:13 CEST 2012 on sn-devel-104
2012-06-22s4-dsdb: operational handle modifyTimeStamp on the CN=aggregate DNMatthieu Patou1-1/+37
modifyTimeStamp is a generated attribute, for most object it's generated directly from the whenChanged attribute. But for the CN=aggregate object in the schema we have to handle it in a different way, that's because for this object whenChanged!=modifyTimeStamp (as checked against Windows 2003R2 DCs) instead the modifyTimeStamp reflect the timestamp of the most recently modified and loaded schema object (that is to the one with the highest USN before the schema was reload due to timeout or by the reloadSchemaNow command). Some third party are using this information to know if they have to update their schema cache and also to check that schema updates have been correctly reloaded by the DC, a good example of this behavior is exchange 2010.
2012-06-22s4-schema: improve the documentation of the dsdb_schema structureMatthieu Patou1-4/+6
2012-06-22s4-dsdb: Check for key SCHEMA_SEQ_NUM in metadata.tdb updatesMatthieu Patou2-3/+192
If the value has changed then reload the schema, this means that now the schema is only reloaded on a periodical basis or if we have been asked explicitly to do it and not necesserly if the schema partition has changed.
2012-06-22s4-dsdb: Add/Update SCHEMA_SEQ_NUM key in the metadata.tdb after schemaUpdateNowMatthieu Patou4-2/+43
The idea is to signal to other process accessing the database that the schema was forced to be reloaded and so they should reload as well.
2012-06-22s4-drs: if schema has changed during replication notify other process that ↵Matthieu Patou1-0/+55
they have to reload the schema
2012-06-22s4-dsdb: move schema_load at the top of module stackMatthieu Patou1-1/+1
2012-06-22s4-extended: do not try to fix if there is no schemaMatthieu Patou1-0/+4
2012-06-22s4-schema: keep track of the timestamp of the most recently changed/created ↵Matthieu Patou3-1/+13
object
2012-06-22s4-schema: generalized time use its own syntax nowMatthieu Patou1-1/+0
2012-06-22ldb: lay foundation for proper utc/generalized time handlingMatthieu Patou3-5/+42
We use to handle UTCtime and generalized time the same way. The thing is that it's not the case, they are different in the way they are set (most of the time) with different format and also stored and return in different format too.
2012-06-22s4-drsuapi: Fix a const warningMatthieu Patou1-1/+1
2012-06-22s4-drsuapi: rework the crackname implementation of functionnal namesMatthieu Patou1-24/+122
2012-06-22s4-dsdb-linkedattributes: register the VERIFY_NAME control, handle it when ↵Matthieu Patou1-10/+97
we are a GC In theory when presented this control and not a GC we should use the specified name as the DC to contact for cross-domain link verification. But for the moment we don't support this so we just fail when we have this control and are not a GC.
2012-06-22s4-ldap: handle VERIFY_NAME control encoding/decodingMatthieu Patou1-0/+96
2012-06-22ldb: add the VERIFY_NAME controlMatthieu Patou2-0/+68
2012-06-22s4-dsdb: support otherWellKnownObjectsMatthieu Patou1-24/+31
2012-06-22s4-dsdb: Try to avoid much of the time a db search for msDS-IntIDMatthieu Patou3-14/+97
We search in the schema if we have already this intid (using dsdb_attribute_by_attributeID_id because in the range 0x80000000 0xBFFFFFFFF, attributeID is a DSDB_ATTID_TYPE_INTID). If so generate another random value. If not check if the highest USN in the database for the schema partition is the one that we know. If so it means that's only this ldb context that is touching the schema in the database. If not it means that's someone else has modified the database while we are doing our changes too (this case should be very bery rare) in order to be sure do the search in the database.
2012-06-22dsdb-schema: do not reload more often than schema_reload_intervalMatthieu Patou5-4/+65
Samba 4 use to try to reload the schema every time dsdb_get_schema was called (which could be 20+ time per ldb request). Now we only reload at most every xx seconds (xx being the value of dsdb:"schema_reload_interval" or 120). The timestamp of the last reloaded schema is kept in the dsdb_schema object. There is also a timestamp in the ldb_context, that is used by the LDAP server to know if it has to reload the schema after handling the request. This is used to allow that the schema will be immediately reload after a schemaUpdateNow request has been issued, the reload can't occur in the handling of the LDAP request itself because we have a transaction autostarted.