Activity for dentar
-
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
-
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...
-
Mark, looking at your other posts, your problem seems to be the communication protocol used by winexe. As you already mentioned, smbclient can be configured to use smb2/smb3 protocol (in case NT1 was disabled on the windows machines). Winexe, in contrast, seems to uses NT1 exclusively, at least this was my finding when disabling NT1. Do you know about how to parameterize winexe to change protocols? Or is this hardcoded somewhere in the sources? You said, since 4.3.12 of samba we could use smb2/smb3....
-
btw, i just checked: docker + winexe v.1.1 + samba v.4.3.12
-
Why docker? 'cause it's cool :-) And it solves the dll-hell equivalent in linux... I chose docker because i already had winexe running in fedora23, and by lazyness all went into the container. Since then, all is fine with fedora24, fedora25, ... Winexe still uses samba 4.3.x of course, but no problems at all (and i am using winexe a lot to access different windows installations)
-
My approach is to use a docker container. In my case, i used a fedora23 base image (which was using samba 4.3.x) and added winexe + dynamically loaded samba. At this time, i had a 'full' fedora23 system to properly compile the winexe executable, so all left over was to include it into the container. Runs smoothly as a containerized shell command, if you accept the container-loading time overhead ;-)
-
Thanks for the workarounds so far, all is ok up to samba 4.3.12 Anyone got winexe...
1
