samba.git/examples, branch talloc-2.3.0

winexe: Add support for connecting to a host on an alternate port

2019-07-05T03:33:19+00:00

This commit allows an optional port number to be specified after the
hostname on the winexe command line. If no port is given, it defaults
to port 445, just like it used before. Although this is probably a
pretty uncommon use-case, it allows port-forwarding the service through
a firewall to an alternate port, which can occassionally be helpful.

$ ./bin/winexe -U karl%password1 //127.0.0.1:5445 cmd.exe
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>

Signed-off-by: Karl Lenz 
Reviewed-by: Andrew Bartlett 
Reviewed-by: Gary Lockyer

winexe: Fix translation of the winexesvc binaries to C

2019-07-05T03:33:19+00:00

Two small Windows binaries that winexe uses to execute commands on a
remote system, winexesvc32.exe and winexesvc64.exe, are compiled then
translated into a C byte array as hex so that they can be embedded into
the winexe binary. Although the winexesvc binaries were built properly,
the Python method that does the translation to C tried to open them in
text mode, which would have worked in Python 2 before the concept of
bytearrays was introduced, but instead raises an exception in Python 3.
The exception was unfortunately suppressed, so the build didn't stop,
and the winexe binary that was produced was effectively useless because
it didn't contain either winexesvc binary as expected. After winexe
successfully authenticated with a Windows host, it showed the error
message below rather than executing the given command on the remote
system.

$ ./bin/winexe -U karl%password1 -d 2 //192.168.56.3 cmd
winexe_svc_install: dcerpc_svcctl_StartServiceW failed: WERR_BAD_EXE_FORMAT
main: winexe_svc_install failed: NT_STATUS_BAD_INITIAL_PC

This commit fixes that problem by opening the winexesvc binaries in
binary mode rather than text mode when the winexe build script reads
them to translate them to C. Furthermore it adds an additional
sanity check that will cause the winexesvc binary generator commands to
fail if the winexesvc binaries cannot be opened or read correctly to
guarantee that the build does not silently "succeed" if something like
this ever happens again.

Signed-off-by: Karl Lenz 
Reviewed-by: Andrew Bartlett 
Reviewed-by: Gary Lockyer

vfs: Remove unused "msg_ctx" from SMB_VFS_BRL_UNLOCK_WINDOWS

2019-07-02T17:01:27+00:00

Signed-off-by: Volker Lendecke 
Reviewed-by: Jeremy Allison

vfs: Remove "blocking_lock" from SMB_VFS_BRL_LOCK_WINDOWS

2019-07-02T17:01:27+00:00

Signed-off-by: Volker Lendecke 
Reviewed-by: Jeremy Allison

s3:vfs: add SMB_VFS_FS_FILE_ID()

2019-07-01T21:43:24+00:00

Not yet used, that comes next.

Signed-off-by: Ralph Boehme 
Reviewed-by: Jeremy Allison

vfs: Remove SMB_VFS_BRL_CANCEL_WINDOWS

2019-06-20T18:34:20+00:00

This is not called anymore, bump the VFS version number in a separate
commit

Signed-off-by: Volker Lendecke 
Reviewed-by: Jeremy Allison 

Autobuild-User(master): Jeremy Allison 
Autobuild-Date(master): Thu Jun 20 18:34:20 UTC 2019 on sn-devel-184

winexe: Use C99 initializer for poptOption in winexe.c

2019-05-28T10:34:24+00:00

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Ralph Boehme

libsmb: add in/out cblobs to cli_smb2_create_fnum

2019-03-01T00:32:12+00:00

This is driven by the imminent smb2 unix extensions, we'll want to make use of
it from source3/libsmb.

Signed-off-by: Volker Lendecke 
Reviewed-by: Jeremy Allison

libsmb: Reformat the cli_smb2_create_fnum_send args

2019-03-01T00:32:12+00:00

We'll add parameters in the next commit, make that commit a bit more obvious

Signed-off-by: Volker Lendecke 
Reviewed-by: Jeremy Allison

examples: Use C99 initializer for poptOption in testacl

2019-01-28T09:29:12+00:00

Signed-off-by: Andreas Schneider 
Reviewed-by: Douglas Bagnall