SYSKEY, TNG freeze, 2.0.x->TNG merge and other thoughts

[Jean Francois Micouleau]

On Thu, 10 Feb 2000, Luke Kenneth Casson Leighton wrote:

> you know those large, stupid buffers you receive at the server end, the
> ones that contain trash?

non-zeroed [in out] buffers for the pure and young ears :-)

> well, they're sent over-the-wire, right (you know this)?

yes I damn know ! I'm currently spending between 8 and 10 hours a day
rewritting that code ! 

> and the server says, error, buffer too small, you need 1megabyte buffer to
> contain the 10,000 printers on this server, right?

yes.

> so the client says, ok!  and sends you an msrpc request with a TRASH,
> blank, unused 1megabyte char* buffer, right, and then you fill the
> 1megabyte buffer in with real data, and send it back?

yes.

> well, the msrpc request is split into multiple PDUs.  those PDUs are sent
> _to_ you with SMBtrans+SMBtranssecondary OR SMBwriteXes, depending on
> client/server DCE/RPC negotiations.
> 
> therefore, in order to support spoolss properly, you need that code.

what's the size of the PDUs ?

But in 2.0.x you can have RpcEnumShares with 10000 shares, and that's
split in multiples PDUs ?