Activity for Winexe
-
Vaibhav Kumar Chaudhary posted a comment on ticket #77
How can I setup this on ubuntu machine? any help would be really appreciated
-
bill hudacek posted a comment on ticket #77
Vaibhav - Here's RPM/Yum info from fedora 32 - so you can compare. Hope this helps. I have not had SuSE since I stopped paying for it 15-20 years ago! rpm -q -i samba-winexe Name : samba-winexe Epoch : 2 Version : 4.12.10 Release : 0.fc32 Architecture: x86_64 Install Date: Sun 29 Nov 2020 09:54:02 AM EST Group : Unspecified Size : 105914 License : GPLv3 Signature : RSA/SHA256, Thu 05 Nov 2020 07:43:28 AM EST, Key ID 6c13026d12c944d0 Source RPM : samba-4.12.10-0.fc32.src.rpm Build Date : Thu 05 Nov...
-
Not really sure how this issue relates to this thread,but I was wondering is this the same winexe that is availabe on opensuse? It's version winexe version 4.8, but that isn't working anycommand
-
Henrique Martins posted a comment on ticket #77
You're welcome, and let's hope whoever put this together keeps up with any SMB changes.
-
WOW! Now that's what I call progress. Back in 2015, it was looking bleak. If it's actually in RPM via Yum repos now, I'm impressed. I'll have to test this out now. (yep, just installed it, I'm very impressed) Thanks for the pointer!
-
I was able to build winexe for some Fedora 3x, maybe late 2x., still have that binary somewhere. However, if you are on Fedora 32 ,just do "dnf install samba-winexe"
-
Funny, me resurrecting a thread I created 5 years ago :-) I'm back on this - situation is different, but I again need winexe. I have fedora 32 on backuppc server. My command line is also: ( ./waf --samba-dir=../samba configure build ) 2>&1 | tee ../waf-with-python2.7.log (This machine has python 3 as default. I got other errors trying to run 'waf' so flipped the symlink to python 2.7, and got the errors in the attached file below ("err: /usr/bin/ld: cannot find -lsmb_static"). There are instructions...
-
Steve Shoecraft modified a comment on ticket #87
Here's the source i use
-
Here's the source i use
-
Here's the source i use
-
John L Magee posted a comment on ticket #87
@Steve Is there a chance we could get the source rpms?
-
Here are the rpms
-
Updated RPMs for EL6,EL7,EL8
-
mohamedazarudeen posted a comment on ticket #86
this is bug.txt file about error
-
winexe- aborted
-
Alan Baghumian posted a comment on ticket #77
Hi Juergen, I'm not sure how you compiled it, but seems like your binary is looking for a library that is in this package: https://packages.debian.org/jessie/libgnutls-deb0-28 Try installing this and then run it to see what happens!
-
Juergen posted a comment on ticket #77
I think it compiledsuccessfully now, but when I want to start it, I get errors: 'configure' finished successfully (45m4.500s) Waf: Entering directory `/root/reevert-winexe-waf/source/build' [ 1/16] c: winexesvc_launch.c -> build/winexesvc_launch.c.1.o [ 2/16] c: winexesvc_loop.c -> build/winexesvc_loop.c.1.o [ 3/16] cprogram: build/winexesvc_launch.c.1.o build/winexesvc_loop.c.1.o -> build/winexesvc32.exe [ 4/16] c: winexesvc_launch.c -> build/winexesvc_launch.c.2.o [ 5/16] c: winexesvc_loop.c ->...
-
Hi Alan, thanks for your work! I followed your steps exactly, but I am getting that errors at the last command: Cannot continue! Please either install Samba shared libraries and re-run waf, or download the Samba source code and re-run waf with the "--samba-dir" option. (complete log in /root/reevert-winexe-waf/source/build/config.log) Which Samba version (v1 or v2) depends on which one is running on the target Windows machine, right?
-
Good morning, I want to install winexe ony my fresh installed Debian 10 x64 machine and I tried a lot of guides found in the internet. Everyone failed with different errors until now. Does anyone have a working way to install winexe on Debian 10?
-
glebrun posted a comment on ticket #77
Thanks a lot On 2019-05-16 12:17 p.m., Brad Mustin wrote: Alan, I was able to get Winexe to build for Raspberry pi Streach, on the Rasbperry Pi. I had to use your Buster Build patch. Tested with command ./reevert-winexe-waf/source/build/winexe-static -U my_domain/my_user%my_pass //my_ip "msg * test popup" Thanks for your help and patches. I also had ran these commands belowI don't believe they were required, I was getting a python error until i applied your buster patch. apt-get install locales build-essential...
-
Brad Mustin posted a comment on ticket #77
Alan, I was able to get Winexe to build for Raspberry pi Streach, on the Rasbperry Pi. I had to use your Buster Build patch. Tested with command ./reevert-winexe-waf/source/build/winexe-static -U my_domain/my_user%my_pass //my_ip "msg * test popup" Thanks for your help and patches. I also had ran these commands belowI don't believe they were required, I was getting a python error until i applied your buster patch. apt-get install locales build-essential git gcc-mingw-w64 comerr-dev libpopt-dev libbsd-dev...
-
working on el6 & el7 tested against 2008/2016/win7/win10
-
Thanks. Added this patch to the repository.
-
In case anyone is interested, I updated build instructions for Debian 10 (Buster): https://bitbucket.org/reevertcode/reevert-winexe-waf/src/master/BUILD
-
Maximo Ramos Capillo posted a comment on ticket #82
I've been in the same situation as yours. For what's worth, I am currently using the winexe binary from the following URL: https://community.opmantek.com/display/OA/Auditing+Windows+machines+from+Linux+using+SMB2 http://dl-openaudit.opmantek.com/winexe-static It does work against Windows 10!
-
ccskoba posted a comment on ticket #77
I am troubled with Alan's SMB 2 versoin. It is winexe-static built on CentOS 6(32 bit) When executed to Windows 2012(64 bit), the following error occurs. IN: async_create_recv CTRL: Sending command: get version ERROR: smb2_read_recv - NT_STATUS_INVALID_PARAMETER ERROR: on_ctrl_pipe_error - NT_STATUS_INVALID_PARAMETER Windows 2012R2(64 bit) works fine without problems. Also, winexe built on CentOS 7, Both Windows 2012(64 bit) and Windows 2012R2(64 bit) It works without problems. Why is CentOS 6(32...
-
Vivek Singh posted a comment on ticket #77
Sorry I forgot to add that I used Debian 8 and I didn’t applied any patch as it is already added in source. Did exactly same steps as mentioned in my previous post. Static binary is working fine on CentOS 7 as well. On Wed, 14 Nov 2018 at 12:29 AM, Henrique Martins mv2007@users.sourceforge.net wrote: No, I was following the instructions in the last comment on this thread before mine, i.e. the one from Vivek Singh of 4 days ago, and he does omit the patching step. I'm on Fedora 29., samba's buildtools/wafsamba/samba_perl.py...
-
I Used Debian 8 and exact steps as mentioned to compile static binary, which is working fine on CentOS 7 as well. No patch needed as its already applied to source.
-
The patch below is needed for samba 4.3.13, if "." is not in perl's @INC, as in perl 5.28.0 --- reevert-winexe-waf/samba/buildtools/wafsamba/samba_perl.py 2018-11-13 12:17:38.151959011 -0800 +++ reevert-winexe-waf-patched/samba/buildtools/wafsamba/samba_perl.py 2018-11-13 12:20:05.550139670 -0800 @@ -56,7 +56,8 @@ conf.env.PERL_LIB_INSTALL_DIR = perl_lib_install_dir perl_inc = read_perl_config_var('print "@INC"') perl_inc.remove('.') if '.' in perl_inc: perl_inc.remove('.') conf.start_msg("PERL_INC:...
-
Needed to install/start the services manually on the remote boxes and then it worked, for both a remote (enterprise) win7sp3 and win10 ltsc, local fedora 29. Thanks! Still need an RHEL version.
-
No, I was following the instructions in the last comment on this thread before mine, i.e. the one from Vivek Singh of 4 days ago, and he does omit the patching step. I'm on Fedora 29., samba's buildtools/wafsamba/samba_perl.py needs to be patched (as it has alaready been don in more recent versions) to only remove "." from @INC if it is there to begin with. Lots of warnings in the build and then I need to link against dynamic libbsd (no static that I could find) and libsystemd (yuck). When I run...
-
Are you following this? https://bitbucket.org/reevertcode/reevert-winexe-waf/src/master/BUILD
-
Apply the patches!
-
I understand, but after extracting the samba tar, there is no bin directory in the samba source, thus the link (which one can still make) points nowhere. If one configures, from the samba directory, one gets a bin directory, but only for a shared build, no smb_static subdirectory.
-
tlathm posted a comment on ticket #77
The original instructions included this (when you're under the reevert-winexe-waf directory): rm -r source/smb_static ...and then a few steps later: cd source && ln -s ../samba/bin/default/smb_static That works for sure assuming you're properly extracted and renamed the samba directory under reevert-winexe-waf.
-
There must be a step missing in these instructions. When I run waf it complains that there is no smb_static directory, and looking under the tree under samba there is no such a thing.
-
finally got is working with latest winexe source with samba-4.3.13. Steps: 1. git clone https://bitbucket.org/reevertcode/reevert-winexe-waf.git 2. wget https://download.samba.org/pub/samba/stable/samba-4.3.13.tar.gz 3. copy samba files in base dir of winexe 4. rm -fr smb_static && ln -s ../samba/bin/default/smb_static 5. ./waf --samba-dir=../samba configure build :)
-
finally got is working with latest winexe source with samba-4.3.13. :) For now I applied this patch . I will test it without patch as alan already applied patch to source.
-
Thank you all for the recent fixes! I tested and merged the submitted patch with the master branch. https://bitbucket.org/reevertcode/reevert-winexe-waf
-
Thank you all for the recent fixes! I tested and merged the submitted patch with the master branch. https://bitbucket.org/reevertcode/reevert-winexe-waf/issues
-
For anyone interested in using Alan's SMB2 versoin, I've posted a revised version of the smb2_nognutls_noaddc.patch that addresses both issue #1 as well as issue #2 that I just opened here: https://bitbucket.org/reevertcode/reevert-winexe-waf/issues An unrelated change that you may want is this change to use winexesvc as the disaplay name pf the service: --- winexe-waf/source/winexesvc.h 2018-09-12 09:38:13.624624305 -0400 +++ winexe-waf.patched/source/winexesvc.h 2018-09-12 09:39:56.181877807 -0400...
-
Deepanshu Chandna posted a comment on ticket #83
Can anyone please provide inputs on this topic?
-
Marco Gaiarin created ticket #84
Compile against samba 4.8, but SIGSEV
-
Need winexe 1.1 rpm package or steps to build and install on RHEL
-
Are you trying to run it inside chroot?
-
I can compile it (with smb2 option) from debian stretch with your instructions. I just had to add some software before building : debootstrap --arch="amd64" jessie debian-jessies/ http://deb.debian.org/debian/ chroot /usr/src/debian-jessies apt-get install locales build-essential git gcc-mingw-w64 comerr-dev libpopt-dev libbsd-dev zlib1g-dev libc6-dev python-dev libgnutls28-dev devscripts pkg-config autoconf libldap2-dev libtevent-dev libtalloc-dev git python apt-get install gcc-mingw-w64 comerr-dev...
-
Kim posted a comment on ticket #35
Hi, I am getting the same error with local users as well. IN: async_open(\ahexec, 2) IN: async_open_recv ERROR: smb_raw_open_recv - NT_STATUS_ACCESS_DENIED ERROR: on_ctrl_pipe_error - NT_STATUS_ACCESS_DENIED ERROR: Cannot open control pipe - NT_STATUS_ACCESS_DENIED and, ERROR: Cannot connect to svcctl pipe. NT_STATUS_ACCESS_DENIED. Looks like am missing something in setting up the local user. Can you please elaborate on the things we need to do for local users? Please note that I have already set...
-
Others may want to note that the current git version of this has logging to C:\winexesvc.log enabled. I disabled it with this: --- reevert-winexe-waf/source/winexesvc_launch.c-orig 2018-05-17 13:44:06.777462929 -0400 +++ reevert-winexe-waf/source/winexesvc_launch.c 2018-05-17 13:44:23.448521569 -0400 @@ -12,7 +12,7 @@ #include "winexesvc.h" -#if 1 +#if 0 #define dbg(arg...) \ ({\ FILE *f = fopen("C:\\" SERVICE_NAME ".log", "at");\
-
Correct. For my own use case, I keep two binaries. SMB v1 for legacy systems and SMB v2 for newer machines.
-
Just to clarify one thing: Am I correct in that, based on the patches applied, this can be compiled for either SMB1 only, or SMB2 only...that is for example that the SMB2 version can't possibly work with SMB1? Just wanted to make sure I had that right.
-
Great! Glad it was useful.
-
I can also confirm that this compiles and works with the SMB2 patches compiling under CentOS 6, and the resulting static binary works under CentOS 6 as well as jessie. Thank you Alan for sure!
-
Jay Jech posted a comment on ticket #77
Wow. I hadn't noticed that file until you pointed it out. Following your instructions in the BUILD file, it compiled on the first attempt and the resulting binary is working with SMBv2.0. Thank you, Alan!!
-
Jay, did you apply the SMB v2.0 patches? I am actually using this with SMB 2.0. See the BUILD file: https://bitbucket.org/reevertcode/reevert-winexe-waf/src/a7647b5e28d6260e964e479424cc22ebf772bf31/BUILD?at=master&fileviewer=file-view-default
-
Is anyone able to compile Mark Ridley's version, or does anyone have a precompiled binary that works with SMB2? (Mark?? 😊) I was able to compile Alan Baghumian's source, but the winexe binary I got from that did not work with SMB2, only SMB1. For Mark Ridley's source, I get errors about missing header files as reported by dentar. I tried manually grabbing all the headers, but ended up with recursive dependencies. I really need a winexe that works with SMB2 (don't care if it works with SMB1; that...
-
Is anyone able to compile Mark Ridley's version, or does anyone have a precompiled binary that works with SMB2? I was able to compile Alan Baghumian's source, but the winexe binary I got from that did not work with SMB2, only SMB1. For Mark Ridley's source, I get errors about missing header files as reported by dentar. I tried manually grabbing all the headers, but ended up with recursive dependencies. I really need a winexe that works with SMB2 (don't care if it works with SMB1; that has been disabled...
-
Jason Martin created ticket #82
Functional winexe with for SMB2
-
In case anyone needs to build winexe with SMBv2 or SMBv1 check this out: https://bitbucket.org/reevertcode/reevert-winexe-waf I created a few patch sets based off Mark Ridley's work to compile with Samba 4.3.13.
-
Asawari Joshi created ticket #81
winexe NT_STATUS_IO_TIMEOUT
-
In case anyone needs to build winexe with SMBv2 or SMBv1 check this out: https://bitbucket.org/reevertcode/reevert-winexe-waf I created a few patch sets based of Mark Ridley's work to compile with Samba 4.3.13.
-
sforger posted a comment on ticket #80
any ideas? thanks
-
Unable to run program on Windows 10 - no output at all
-
I've installed samba 4.5 from source under CentOS 6.8 and am attempting to compile Mike Ridley's version dynamically. I've installed under /usr/local/samba, and seem to be running into configure errors I can't resolve, especially on libraries that installed under /usr/local/samba/lib/private. One example is getting this in the log: Checking for library cli-ldap-samba4 : not found Checking for library :libcli-ldap-samba4.so.0 : not found ['/usr/bin/gcc', 'test.c.1.o', '-o', '/root/winexe/u-markr123-winexe/source/build/.conf_check_62e2888926183ee9a90e507eddf5c2a5/testbuild/testprog',...
-
Mai posted a comment on ticket #78
Nevermind, i found your fork. Thanks
-
Hi Mark, can you share the code fork ? I need to recompile winexe for SMB2 aswell. Thanks
-
Tux TouToune posted a comment on ticket #77
on ubuntu 16.04 LTS it compile fine with git clone git://git.code.sf.net/u/mstowe/winexe u-mstowe-winexe cd u-mstowe-winexe/source apt-get -y install python2.7 gcc-mingw-w64 libtevent-dev samba-dev ln -s /usr/lib/x86_64-linux-gnu/samba/libcli-ldap.so.0 /usr/lib/x86_64-linux-gnu/samba/libcli-ldap-samba4.so.0 ln -s /usr/lib/x86_64-linux-gnu/samba/libdcerpc-samba.so.0 /usr/lib/x86_64-linux-gnu/samba/libdcerpc-samba-samba4.so.0 ln -s /usr/lib/x86_64-linux-gnu/samba/liberrors.so.0 /usr/lib/x86_64-linux-gnu/samba/liberrors-samba4.so.0...
-
Correction to the above regarding psexec.py (apologies for the OT): I discovered that it was simply exiting with ErrorCode but not the ReturnCode. That aside, it seems that some things that work with winexe behave very strangely with it. For example, running simple commands with SQLCMD seems to output literal backspace characters or even nothing at all. Still looking into the command length issues.
-
Like others I've done a lot of testing with the Impacket psexec.py. I've been able to modify that to allow a static service and executable name rather than the random name. I've also been able to allow it to leave the service installed and have it check for the already existing service etc. With the latter, simultaneous commands seem pretty reliable. However I've run into enough nasty bugs to make it unusable as it stands. Just like BorderlineADD I've found that it fails all the time with commands...
-
Does anyone know if it's even possible to compile this version with a static samba4, for example under CentOS 6? From attempts I've made it appears that the various includes referencing #include "libcli/..." in the winexe code itself, as mentioned by dentar, simply may not work with the static build at all. Before even getting that far, I had to revert samba to a6bda1f2bc85779feb9680bc74821da5ccd401c5 to get around issues described here: https://sourceforge.net/p/winexe/bugs/64/ At that point I don't...
-
Armands Liepins posted a comment on ticket #77
Managed to build on Fedora 25 with "LDFLAGS='-Wl,-rpath,/usr/lib/samba' ./waf configure" then "./waf build". The only problem - now all error messages goes to stdout, not stderr.
-
Tom Dexter posted a comment on ticket #79
I hope that at some point, someone directly involved with the winexe project will submit a false positive report to Symantec on this if that hasn't happened yet. It appears that many (if not most) virus scan products have followed Symantec's lead on this one.
-
Mark Ridley modified a comment on ticket #77
-
dentar posted a comment on ticket #77
Anyone got Marks git source compiling with samba 4.5.10? I am trying on fedora25 but the compiler is complaining about missing header files like: "libcli/raw/libcliraw.h: No such file or directory" ./waf configure went fine, though... I'm pretty sure the other includes of winexe.c like: libcli/raw/smb.h, libcli/smb2/smb2.h, libcli/smb2/smb2_calls.h and libcli/libcli.h will fail as well.. Does samba4.5 still contain these files? Am i missing some important libs/devel packages? thanks for any help
-
srikar posted a comment on ticket #77
Thank you Francis and Micheal for the inputs. I was able to build winexe on Ubuntu 16.04.2 LTS after doing a git to the above link of v0.1 and doing git of old-v4-0-stable branch.
-
Michael Stowe posted a comment on ticket #77
You're exactly correct, I tagged the version that compiles against Samba 4.0-4.4 as v0.1, which is the one that you've provided the tarball link to already. v0.2 compiles against Samba 4.5, which was changed enough so that the previous version had no hope of compiling as it was.
-
Francis Lessard posted a comment on ticket #77
Hello Srikar I tried this morning with a fresh Ubuntu 16.04.2 fully patched server. I do obtain the same error as you did have. Something was changed June 01-2017 by Michael Stowe on his Winexe fork to get it to compile against samba 4.5. Our distro is still at version 4.3.11 so I beleive something was broken there. I will investigate if something could be done to adapt to the new corrected fork. In the meantime you could download the previous v0.1 at https://sourceforge.net/u/mstowe/winexe/ci/v0.1/tarball...
-
BorderlineADD modified a comment on ticket #77
We have also been putting quite a bit of time into the impacket psexec script. The last two issues we have are 1) simultaneous calls to the same Windows machine occasionally (about 0.05% probability) fail, and 2) it fails 100% of the time with command lines longer than about 253 characters. The random failures occur much less frequency when all calls are single-threaded (about 0.002% probability).
-
We have also been putting quite a bit of time into the impacket psexec script. The last two issues we have are 1) simultaneous calls to the same Windows machine occasionally (about 0.05% probability) fail. Failures occur much less frequency when all calls are single-threaded (about 0.002% probability). Yesterday we discovered that it fails 100% of the time with command lines longer than about 253 characters.
-
Colvin Wellborn posted a comment on ticket #77
So I'm actually going down the road currently with the impacket python setup dentar mentioned above. Getting good results using winexec.py, as for my use case I only ever need a single command executed synchronously. My immediate plan to to roll over to that, but I do intend to check out the winexe work from Mark so I can report how it's working for me. I'd also like to compare Mark's work with my own. If winexe is working, then it's a matter of comparing the performance of the two solutions to see...
-
This is fixed now. I have made a fork that works with SMB2
-
Hi Colvin, I think you were getiing the NT_STATUS_OBJECT_NAME_NOT_FOUND message because SMB2 does not like the \ in the share names. SMB1 didnt seem to care. I have posted a full fix. Cheers, Mark
-
Finally got it all working. This is a SMB2 version only of winexe. It does not work with SMB1. The SMB3 code in samba is also a bit suspect as it works only about 10% of the time, but I am not fixing that yet. Let me know how you get on. It is based on Michael's Samba 4.4.5 fork. just type ./waf configure and ./waf build git source
-
Hi Francis, Being a noob I ran the command you posted for winexe bug '77' on "Ubuntu 16.04 server" .I got the below error. Build of shared winexe : disabled Cannot continue! Please either install Samba shared libraries and re-run waf, or download the Samba source code and re-run waf with the "--samba-dir" option. (complete log in /root/u-mstowe-winexe/source/build/config.log) Since you have successfully installed winexe on ubuntu 16.04, can you please give me the details regarding that.Thanks in...
-
Dentar / Colvin - Apologies for not checking forum for 3 days and seeing your messages. I'e had my head buried in winexe and samba source code. Drop me an email at mark_ridley@hotmail.com
-
Dentar / Colin - Apologies for not checking forum for 3 days and seeing your messages. I'e had my head buried in winexe and samba source code. Drop me an email at mark_ridley@hotmail.com
-
Hi Dentar, Thanks for sending that over. As mentioned above, I have got a new version of winexe working on SMB2, but having problems with the last little bit. It fails 9 out of 10 times. There is a timing issue somewhere and after 2 weeks, day and night I need some coding help. If I put -d99 in the winexe line to slightly slow it down, it works 50% of the time. it is reading from the named pipes from windows that is cauing the issue. Colvin - Another I had to change in the main winexe code was to...
-
Hi Colvin, Great to hear someone is also looking at this. I've got it to work...just. but there seems to be an issue in the async_read_recv code, but it may be down to the smb2_create. Most times I am getting an NT_STATUS_INVALID_PARAMETER returned in te read code. It works 1 in 10 times and all works great, but it is just not reliable enough, After spending weeks on this, I have just about given up, re-written the winexesvc_loop code to use temp files instead of pipes and getting winexe.c to open...
-
Hi Colvin, hi Mark, i was busy looking for some alternative for winexe - and found something - look here: https://github.com/CoreSecurity/impacket/ This project contains a python script psexec.py which seems to work properly with smb2 (at least my tests succeeded). For me, this is not really an alternative to use productively because this psexec is way slower than winexe. So, what i suggest is, you two might take a look at the python sources for some inspiration? Maybe here Colvins problem filling...
-
I'm also working this problem, and am encountering an issue in the same place. Replacing smbcli_full_connection(), struct smbcli_tree, and related data structures with smb2_connect(), struct smb2_tree, etc is working correctly (after fixing the build issues). I replaced smbcli_open() and smb_composite_savefile() in svcinstall.c with smb2_create() and smb2_write(), and have the winexesvc service delivery and control working. In async.c, working with the \ahexec pipe, there doesn't seem to be 1-to-1...
-
I am having problems writing to the IPC$/ahexec named pipe that the winexesvc listens on. my samba4 / SMB2 version opens IPC$ and writes to ahexec but nothing is coming through. I have put the service into debug mode and it just says the pipe gets opened but nothing comes through. the original winexe code does 'raw' comms? What is that?
-
Hi, The problem with centos 7 is the smb_static library just does not build. I have got it to compile and build a shared library version on centos 7 using michael's version which rewrites the debug code as the debug library is now private on later versions of samba.
-
Tintn posted a comment on ticket #77
Thanks for all your work Michael and Mark. Here is the error I am getting on both CentOS 7 and Ubuntu Desktop 16.04. I look forward to the fix and/or the rewrite. Awesome tool. [3334/3819] Compiling default/smb_static/smb_static.objlist.empty.c Waf: Leaving directory `/root/u-mstowe-winexe/samba/bin' Build failed: could not find 'smb_static/smb_static.objlist.empty.c' for {task: cc smb_static.objlist.empty.c -> smb_static.objlist.empty_2.o} Checking for library smb_static : not found Build of static...
-
I am getting the same error on CentOS7 and Ubuntu Desktop 16.04... [3334/3819] Compiling default/smb_static/smb_static.objlist.empty.c Waf: Leaving directory `/root/u-mstowe-winexe/samba/bin' Build failed: could not find 'smb_static/smb_static.objlist.empty.c' for {task: cc smb_static.objlist.empty.c -> smb_static.objlist.empty_2.o} Checking for library smb_static : not found Build of static winexe : disabled
-
OK. I've found the smb2 calls in the samba4 source. They are the smb2_connect calls in source4/libcli/smb2/connect.c I'll code winexe to call them and see what happens.
-
The problem with the samba4 branch is the share or tree opening code, smbcli_full_connection does not call the smb2 code if SMB2 is required to it crashes. so for example in the cifsdd or winexe or even smbclient4 when smb1 is disabled it still calls the SMB1 code which then gets cut off. I have logged a ticket with samba but no one has picked it up yet. the smbcli_full_connection calls smb_composite_connect which is only smb1. i do not have enough knowledge to call the smb2 code. any ideas? i starting...
-
The short version is that yes, it's possible. The longer answer is that as Samba development progresses, it's becoming increasingly difficult to maintain in its current form, anyway, and that a better approach (as already suggested) is to extricate it from Samba itself and use Samba libraries, which is a larger task, but I can't guess offhand whether that's larger or smaller than reverting to Samba3 -- but I can suggest that it's likely to garner more support as CIFS continues to evolve and Winexe...
-
Dean Williams posted a comment on ticket #79
Just to add to this, here's what Symantec are saying about winexe: Files that are detected as PUA.Winexe!g1 are considered malicious. If you have reason to believe that your files are incorrectly detected by Symantec products, you can submit them to Symantec Security Response for further analysis.
-
Dave Mariano created ticket #79
Symantec Endpoint Protection False Positive PUA
-
Does anyone know if it is possible to re-write winexe to use the source3 version of samba code? source4 is broken with SMB2/3. I have emailed bugzilla at samba to let them know but do not expect a reply anytime soon. using the samba binary: cifsdd which also uses source4 it can be seen to fail to connect to windows on SMBv2: cifsdd: connecting to //192.168.1.67/C$: NT_STATUS_INVALID_PARAMETER_MIX
-
nevermind, i got it to work. I had to use commit hash '21c1ad4d17e923dd38799a5083c4001ba91d9a26' from Michael Stowe version. I applied your folder symlink and update wscript to build samba with --disable-gnutls For some reason even updating wscript_build with lib='dl gnutls' under bld.env.SAMBA_DIR , i continue to get error on undefined : 'gcry_control' I am going to retest to see if i can build samba without disabling gnutls