| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Add hf for function return value.
Rename struct field members to be named after the structure name
and element name rather than element name and element type.
Remember which structure or function we are processing and use it
to generate hf fields according to the naming scheme above.
(This used to be commit fd14622d132c3f2dfd837ea7beccd0fc11a6bf3e)
|
|
(This used to be commit b2a3b0221680fb54b058631846559e6151a7b562)
|
|
I'm hoping this will allow better mapping hf fields to the structures
they are present in which isn't possible at the moment. (Line mode
allows us to use /foo/ .. /bar/ regexps and to store state during the
processing.
(This used to be commit 75b6df15f2edfac99fbcd7cefb7b404591a1ecb6)
|
|
the backend should check for
(dce_call->state_flags & DCESRV_CALL_STATE_FLAG_MAY_ASYNC)
then it's allowed to reply async
then the backend should mark that call as async with
dce_call->state_flags |= DCESRV_CALL_STATE_FLAG_ASYNC;
later it has to manualy set r->out.result
and then send the reply by calling
status = dcesrv_reply(p->dce_call);
NOTE: that ncacn_np doesn't support async replies yet
- implement an async version of echo_TestSleep
- reenable the echo_TestSleep torture test
(this need to be more strict when we have support for async ncacn_np)
metze
(This used to be commit f0a0dbeb25b034b1333078ca085999359f5f6209)
|
|
metze
(This used to be commit b467635c2dd90dc40e2358b8d18bec238a85786f)
|
|
This call uses a new IDL type, NTTIME_hyper. This is 8-byte aligned,
as the name suggests.
Expand the QuerySecret LSA calls in RPC-SAMLOGON and RPC-LSA, to
validate the behaviour of times, and of the old secrets.
Thanks to tridge for spotting the use of HYPER!
Andrew Bartlett
(This used to be commit 1fed79cb0f2ae7940639d08ef99576559d4cd06e)
|
|
one pipe
this stage does the following:
- simplifies the dcerpc_handle handling, and all the callers of it
- split out the context_id depenent state into a linked list of established contexts
- fixed some talloc handling in several rpc servers that i noticed while doing the above
(This used to be commit fde042b3fc609c94e2c7eedcdd72ecdf489cf63b)
|
|
metze
(This used to be commit 64805e5dc58ad1d1fefc3e36158131fa2d531592)
|
|
More work on the example class implementation
(This used to be commit 1f8f4dd179d5aa0472c676d115dc2fc1749ce32d)
|
|
dcerpc_alter_context and multiple context_ids in the dcerpc client
library.
This stage does the following:
- split "struct dcerpc_pipe" into two parts, the main part being "struct dcerpc_connection", which
contains all the parts not dependent on the context, and "struct dcerpc_pipe" which has
the context dependent part. This is similar to the layering in libcli_*() for SMB
- disable the current dcerpc_alter code. I've used a #warning until i
get the 2nd phase finished. I don't know how portable #warning is, but
it won't be long before I add full alter context support anyway, so it won't last long
- cleanup the allocation of dcerpc_pipe structures. The previous code
was quite awkward.
(This used to be commit 4004c69937be7e5dae56f9567ca607f982d395d3)
|
|
(This used to be commit 20f9143221021ab050802d6aed359677bee978ed)
|
|
regexps. Hopefully this will make things a bit easier to understand
later on.
(This used to be commit c325859eb6a0972638bbbb83ebb2dfda489ac8ee)
|
|
Return more ethereal types and bases for hf fields. Currently we
assume that enums always fit into a uint16 which will probably have to
change soon.
(This used to be commit 25f6e11f3156e21c1dc03afa879e9cda2f5dd341)
|
|
Start working on adding support for bitmaps and enums.
In progress tweaks for arrays of structures.
(This used to be commit d39cb7ecb4c193cbba628ee6d6f9b5c5bbf89d33)
|
|
(This used to be commit 0f8f0de00fa687920c898a56238cd3e21d83cfb1)
|
|
NDR_PAHEX is handled by ndr_print_enum() now
metze
(This used to be commit c3b2d2cca37193fead0df1a8808c3ffcd5180a89)
|
|
(This used to be commit ec70d9a740ab0b6f83b6b10c1b5313e585164383)
|
|
metze
(This used to be commit 6f75a06b8691dd0d684a51b7851696613c6a6b11)
|
|
'declare bitmap foo1;'
'declare enum foo2;'
and also allow
typedef [public] bitmap ...
typedef [public] enum ...
you need to a forward declaration of bitmaps and enums
when you want to use them in another idl file,
and you need to make the real declaration to be public
see the next commit to samr.idl and netlogon.idl
metze
(This used to be commit a8d61aa47388b82595ee02b9cfd35f15afb93c2a)
|
|
talloc_size() or talloc_array_p() where appropriate.
also fixed a memory leak in pvfs_copy_file() (failed to free a memory
context)
(This used to be commit 89b74b53546e1570b11b3702f40bee58aed8c503)
|
|
(swig stuff seems broken atm though)
(This used to be commit 9eeb976773a8d2ed26a690c73d67f5db735e8d3a)
|
|
metze
(This used to be commit 2f3aea72ee7d9d90f7b910d11bdd1e96f9f0ebe1)
|
|
typedef bitmap {
FLAG1 = 0x01
} fooflags;
typedef struct {
fooflags flags;
}
metze
(This used to be commit 052a7d4f9a3a178149c65a616fdfd87152dff7eb)
|
|
metze
(This used to be commit afef9b10481da3857d3cba598a71c01b827f29de)
|
|
typedef [bitmap16bit] bitmap {
FLAG1 = 0x0001,
FLAG2 = 0x8000
} fooflags;
metze
(This used to be commit 192f2495468d5d0c5889d94ca791aa8f371514e8)
|
|
is less efficient, but I really doubt that matters.
- use enum in epmapper.idl for protocol type
- added support for "enum8bit" flag, used in epmapper.idl
(This used to be commit 1a24a50384b7f588844cd012f1218ca242ca4507)
|
|
thought. This puts in a workaround
that fixes things for now
(This used to be commit 0939b83a0f07563edc6448fb6a87a573dbaa9f6c)
|
|
(This used to be commit 73d5a033e8e9de536239c53e8a063e9be0eff701)
|
|
support enum
(This used to be commit dee8eff2590be58c59b0db089fcca4af3e011c42)
|
|
as types in switch
statements and variable types, and the value will be printed with its string name and value
(This used to be commit 1852033f2ec7584657d586e44d25a280959e4d81)
|
|
Generate code to display using proto_tree_add_bytes() instead.
(This used to be commit 6e480fab3a0f70ae17dd7c0b39da924361a354d5)
|
|
(This used to be commit b9432130959aeaab6d1720ac2c6f99e3d8f9e037)
|
|
(This used to be commit 0f50ed8260ce37c21d8ad62b5a257f22ab4a5534)
|
|
(This used to be commit 60f266bf6a30eee485c4f498569201ac50f85120)
|
|
various types of arrays and relative structures.
(This used to be commit 9f99d94ff5863b2da05f2283639852306bfbc74d)
|
|
(This used to be commit 446b2cf99641956b9bdede4364c93232d914c678)
|
|
(This used to be commit 973acf7bbdb7bd71f052aca15d0189f2e2069fd4)
|
|
based on the idea of manipulating the .c and .h files generated by
parser.pm with perl regexps and glueing it all together to make an
ethereal plugin.
I thought this was a pretty crazy idea to start off with but it has
turned out to be not as complicated as I thought and has the huge advantage
of not duplicating any of the difficult code in parser.pm.
(This used to be commit 7007522f83740f41f9a47f5ad5942ea46320d405)
|
|
prototypes for ndr push/pull/print functions.
(This used to be commit 1fe95ad1720f48a353ec77178e303b437bb13fed)
|
|
main rpc server code. let the backends specify a ndr_push/ndr_pull function
like we already do with the dispatch() function.
this allows an interface implmentation to work as real proxy
without needing to know the idl for an interface that means
just the plain decrypted payload can be forwarded
If someone want to write such a backend, patches are wellcome
metze
(This used to be commit a150bdf140d9165a05cbc7cac40b6e3c03a7bd3c)
|
|
separately)
(This used to be commit e399834ae1aa9731d5d29c04d5b7b90e356dad6f)
|
|
(This used to be commit 3040cd65151dbcc54404f9be9d1fbcf539c7b635)
|
|
check that the server
hasn't given us a null pointer, otherwise we can segv when we dereference it. For example:
[size_is(*size)] *x;
uint32 *size;
if a broken server gave us x != NULL and size == NULL then we would crash. I've added
a check_null_pointer() call in pidl to catch this.
(This used to be commit 8cbd3f47a95367e861c6b99c44416a9ccef3c9ca)
|
|
(This used to be commit 83221a0da07bf7c45757e737782f2f4ee541ad88)
|
|
that depend on variables that come after the array in the structure or function.
This has been something that has been problematic for a while, but the
winreg QueryValue problem finally prompted me to fix it properly. We
should now go back and fix up all the ugly workarounds we have used to
avoid this problem in other calls.
Unfortunately the solution is fairly complex, and involves the use of
the internal ndr token lists (similar to the solution for relative
pointers). I wonder if anyone else will be able to follow the logic if
I get run over by a bus :-)
(This used to be commit e839b19ec5581f669f2a7705b1fb80845313251c)
|
|
dcerpc_ndr_request_send()
- this allows us to call dcerpc_log_packet() when we receive a packet we
can't parse correctly
metze
(This used to be commit a7a6cea112a180a28188997ca99f30d8dd286bb8)
|
|
metze
(This used to be commit 979c453c4dedf0006997dfc9994331e49643b741)
|
|
metze
(This used to be commit 2647b47557c880dd5f24a4cd15475badfd7fdc94)
|
|
metze
(This used to be commit 7264a2227d7a1881db01964d0d713c144eb77152)
|
|
metze
(This used to be commit 44f168c44de908fdf38b39aae8bf10e80206410a)
|
