From 622ed701a52899b84fbce7e8e4cceab51b039dd2 Mon Sep 17 00:00:00 2001 From: Tim Potter Date: Mon, 20 May 2002 01:00:56 +0000 Subject: There's probably a pointer to a buffer at the end of a enumprinterdrivers() rpc call which we currently don't parse - just added a comment about it for the moment as not parsing it is harmless. (This used to be commit 2429c4cc796576aa2d816a14b10fdd932b672a02) --- source3/rpc_parse/parse_spoolss.c | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'source3') diff --git a/source3/rpc_parse/parse_spoolss.c b/source3/rpc_parse/parse_spoolss.c index bcfaa1d42f..3e3ddb9a01 100644 --- a/source3/rpc_parse/parse_spoolss.c +++ b/source3/rpc_parse/parse_spoolss.c @@ -4261,6 +4261,10 @@ BOOL spoolss_io_q_enumprinterdrivers(char *desc, SPOOL_Q_ENUMPRINTERDRIVERS *q_u if (!prs_uint32("offered", ps, depth, &q_u->offered)) return False; + /* According to MSDN there is another [in] parameter for this rpc + which could be a pointer to a buffer. NT4 puts four zero bytes + here which we currently don't parse. -tpot */ + return True; } -- cgit