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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
linked list when moving it to another. This could cause a valgrind
error under the RPC-SCANNER test.
(This used to be commit 9ba8c008513e362fbb860af899006505cadb4a2f)
This needs to be fixed in Samba3 as well. It might be exploitable (I
haven't confirmed one way or the other), so I think this should be
fixed for 3.0.25
(This used to be commit 4766175ff2d0de8af92046e29280c7893ac8fe1f)
dcerpc_ship_next_request() logic was added the penidng queue was split
in two, but we also needed to update the code which removes requests
from the queue to know about the two queues. Following the pattern
used in other client libs, I based which queue to remove from on
req->state, and added a new state RPC_REQUEST_QUEUED. This fixes a
crash that happens when rpc requests time out.
This patch also fixes the handling of timed out bind requests, and the
talloc_reference handling in dcerpc_ndr_request_recv().
(This used to be commit f51a129b52d53059cc1567538f986400c0ea5602)
height of 100% means that if the enclosing widget is 100 pixels high, this
widget should be 100 pixels high. If this widget is then placed someplace
other than at the top of the enclosing widget, e.g. with top:20, the bottom
of this widget will fall off the bottom of the enclosing widget.
The normal way to solve this is to specify top and bottom attributes rather
than top and height attributes. Also, since widgets often look better if
they don't extend all the way to the very bottom, specifying a bottom
attribute equal to the top attribute typically has an appealing appearance.
I've fixed the tree widget so it no longer falls off the bottom of the page.
(This used to be commit 44d5f5ec6db76c981f94e7322f82592e5d85be9f)
appear. Now that the finite state machine properly ignores events from
widgets which are not handled, the initialization of the tree should be done
when the module's canvas appears (i.e. just after the canvas has had the
module's gui applied to it).
(This used to be commit ab620c9554642f1289d6d0136fb104e475f22316)
non-handled widget to be processed as if the event originated from a handled
widget. This was allowing the appear event for the module's canvas in
Mimir's Net Manager (an event which was not handled) to load the tree,
followed by the tree appear event (intended to be handled, albeit
incorrectly -- see subsequent check-in of Mimir's Fsm.js) to again load the
tree, thus the double entry.
Wow, the above paragraph is really hard to read. :-)
(This used to be commit 512dc61e846669311b1605c6c4e1b49241c1c8be)
Samba4. This only broke on global catalog queries, which turned out to
be due to changes in the partitions module that metze needed for his
DRSUAPI work.
I've reworked partitions.c to always include the 'problematic' control,
and therefore demonstrated that this is the issue. This ensures
consistency, and should help with finding issues like this in future.
As this control (DSDB_CONTROL_CURRENT_PARTITION_OID) is not intended to
be linearised, I've added logic to allow it to be skipped when creating
network packets.
I've likewise make our LDAP server skip unknown controls, when marked
'not critical' on it's input, rather than just dropping the entire
request. I need some help to generate a correct error packet when it is
marked critical.
Further work could perhaps be to have the ldap_encode routine return a
textual description of what failed to encode, as that would have saved
me a lot of time...
Andrew Bartlett
(This used to be commit eef710668f91d1bbaa2d834d9e653e11c8aac817)
Wait around for the server to start, so we don't try to contact it
during it's starup phase.
Andrew Bartlett
(This used to be commit f484b0a924809dd8c9861ade8d184fb44b3b5e1f)
was we were not checking the result of a convert_string() call, and it
was giving -1. We then passed -1 to fwrite() on stdout, which on aix
and macosx wrote all of available memory to stdout :)
To fix this, replace non-printing chars with ? in d_printf if the
string cannot be converted
(This used to be commit d20102d363f4b9214e29296ad8ec45c8d95614b5)
