search for: rpctorture

Displaying 4 results from an estimated 4 matches for "rpctorture".

Did you mean: gctorture
2006 Aug 13
1
Building 23b
Building 3.0.23b I get these errors: [...] torture/rpctorture.c:377: error: (Each undeclared identifier is reported only once torture/rpctorture.c:377: error: for each function it appears in.) torture/rpctorture.c:535: warning: passing argument 5 of 'create_procs' from incompatible pointer type torture/rpctorture.c:539: warning: passing argument 5 of...
2002 May 29
0
Need help compiling on HPUX 11.00 for 2.2.4
...IQX_OBJ) $(LIB_OBJ) SMBCACLS_OBJ = utils/smbcacls.o $(LOCKING_OBJ) $(LIBSMB_OBJ) $(PARAM_OBJ) \ $(UBIQX_OBJ) $(LIB_OBJ) $(RPC_PARSE_OBJ) $(PASSDB_OBJ) \ $(LIBMSRPC_OBJ) LOCKTEST2_OBJ = utils/locktest2.o $(LOCKING_OBJ) $(LIBSMB_OBJ) $(PARAM_OBJ) \ $(UBIQX_OBJ) $(LIB_OBJ) RPCTORTURE_OBJ = utils/rpctorture.o \ rpcclient/display.o \ rpcclient/cmd_lsarpc.o \ rpcclient/cmd_wkssvc.o \ rpcclient/cmd_samr.o \ rpcclient/cmd_srvsvc.o \ rpcclient/cmd_netlogon.o \ $(PARAM_OBJ) $(LIBSMB_OBJ) $(UBIQX...
2002 May 28
0
link errors compiling 2.2.4 on HP-UX 11.00
...IQX_OBJ) $(LIB_OBJ) SMBCACLS_OBJ = utils/smbcacls.o $(LOCKING_OBJ) $(LIBSMB_OBJ) $(PARAM_OBJ) \ $(UBIQX_OBJ) $(LIB_OBJ) $(RPC_PARSE_OBJ) $(PASSDB_OBJ) \ $(LIBMSRPC_OBJ) LOCKTEST2_OBJ = utils/locktest2.o $(LOCKING_OBJ) $(LIBSMB_OBJ) $(PARAM_OBJ) \ $(UBIQX_OBJ) $(LIB_OBJ) RPCTORTURE_OBJ = utils/rpctorture.o \ rpcclient/display.o \ rpcclient/cmd_lsarpc.o \ rpcclient/cmd_wkssvc.o \ rpcclient/cmd_samr.o \ rpcclient/cmd_srvsvc.o \ rpcclient/cmd_netlogon.o \ $(PARAM_OBJ) $(LIBSMB_OBJ) $(UBIQX...
1999 Aug 24
0
Vulnerabilities needed in Windows NT!
...denial of service attack) then at the risk of alienating microsoft (but not microsoft's customers), ISS releases a report. the person that finds the problem (originator) is credited at the end of these reports. if anyone finds that Windows NT crashes whilst using samba (smbd, nmbd, rpcclient, rpctorture, smbtorture) then please either provide a report to myself (lkcl@iss.net) or contact secure@microsoft.com directly (but also please let me know as well, e.g by cc on the message!) this message is also intended to encourage people to _actively_ find ways to crash Windows NT... AND TO BE RESPONSIBLE...