IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
we should only use 255.255.255.255 for group records,
only when we reply, not when the name is registered.
the real address is used for replication
metze
(This used to be commit 45a774c63c)
- as the old records are broken sinse the last winsdb_dn() changes, (the dn components order was reversed)
we can use nicer attribute and objectClass names...
- use much more verbose error handling for winsdb_*
- print a debug message when we found a corrupted record
metze
(This used to be commit 82bad3f3ef)
create winsdb_record() and winsdb_message() as public functions
so that they can be used in the wrepl_server/
metze
(This used to be commit b8b48c8aa5)
- load our wins partners at start time:
# this is a sample partner record:
dn: name=SERNOX4-1,CN=PARTNERS
objectClass: wreplPartner
name: SERNOX4-9
address: 172.31.1.1
ourAddress: 172.31.9.1
type: 0x3
pullInterval: 3600
- go through all winsdb records in the database and create the wins_owner table,
but don't add ourself to it as out nbt task will update the db too, we refetch
the local max_versiion, each time we need it, (that typicaly onces per replication cycle)
metze
(This used to be commit 4490a2864e)
- store the wins owner on the record and the wins owner and expire time on each address
- we use "0.0.0.0" to mark entries which are registered at the local wins server
- we use this ldif-format:
address: 172.31.9.1;winsOwner:0.0.0.0;expireTime:20050923032337.0Z
address: 172.31.1.1;winsOwner:172.31.9.202;expireTime:20050923032330.0Z
metze
(This used to be commit 752025a0e1)
move to struct winsdb_addr, (I'll add expiry_time and the wins_owner later
tridge: can you please review the new winsdb_addr_* functions carefull, look for off-by-one bugs, etc.
metze
(This used to be commit 72eba90465)
add wrapper functions for the "address" attribute in the winsdb,
the goal is to store the expiry time and the wins owner per address,
which is needed for wins replication
metze
(This used to be commit 2fd3bbd044)
- add winsdb_connect() function, so that the winsdb can be opened by the wrepl_server/ code
- remove maintaining of a min_version field, as it was implemented incorrect, and is maybe not needed at all
- fix handling of max_version, (we started with 0, on each server start)
metze
(This used to be commit e6106e21a0)
- w2k just ignores invalid packets, so we do now
- w2k only checks the assoc_ctx when the opcode has the sepcific obcode bit's set
- terminate the connection, when getting a WREPL_STOP_ASSOCIATION packet
- some more special error handling
proper torture test for all this cases are following later
metze
(This used to be commit 42b69461aa)
r10113@SERNOX: metze | 2005-09-09 18:00:02 +0200
rename libcli/wins to libcli/wrepl
metze
r10115@SERNOX: metze | 2005-09-09 18:01:49 +0200
bind client connection to the best interface, to the partner
metze
r10116@SERNOX: jelmer | 2005-09-09 18:23:50 +0200
Print out a couple more warnings.
(This used to be commit 66f931071e)
- move structs to a seperate header file
- move the code for the wreplsrv_in_call handling to a seperate file
metze
(This used to be commit c9a8544446)
This is the start of a WINS-Replicaton server:
The design is to handle incoming and outgoing connections,
in one process, because it make thing much easier, and there's
no need to it otherwise.
The current code only parses incoming packets, and can reply
to them, but currently only a standard error packets STOP_ASSOCIATON
with reason == 4 (I think it means your are not configured as a wins partner of me)
(the server service is called "wrepl")
metze
(This used to be commit 55a2016ba3)
add struct nbt_peer_socket and use it instead of passing const char *addr, uint16 port everyhwere
(tridge: can you review this please, (make test works)
metze
(This used to be commit a599d7a4ae)
needed to represent all the current records on a ADS LDAP server. The
idea is we will use something based on this code to work out exactly
what schema elements we will need for our initial ADS schema. I plan
on expanding this code to automatically work out attribute properties,
and write out a schema file that we can load into ldb.
Interestingly, it looks like we only need 43 objectclasses and around
200 attributes to represent all records of a newly installed w2k3 ADS
server.
(This used to be commit 7b0ae77757)
authentication out of the various callers and into the kitchen
sink.. err, credentials subsystem.
This should ensure consistant logic, as well as get us one step closer
to security=server operation in future.
Andrew Bartlett
(This used to be commit 09c9576330)
this sometimes crashes the windows server
- add the first replication conflict tests
we now test that replica records are always overwritten
when the owner is the same
metze
(This used to be commit f93353ac41)
The problem was that the samdb module was auto-adding objectClass=user
for these accounts. That would be OK, as computer accounts are
supposed to be in that objectClass, but mmc cares about the order of
the values in the objectClass attribute! It looks for the last value,
and takes that as the value to use when deciding how to manipulate the record.
So, this patch adds an explicit objectClass=user to the record when it
gets created, which tells the samdb module to not add it as well. That
fixes the order. I suspect we are missing something else though - is
objectClass supposed to auto-sort based on the schema?
(This used to be commit 68c5f807fd)
