From opensource at ronnypfannschmidt.de Sun Dec 4 09:03:56 2016 From: opensource at ronnypfannschmidt.de (Ronny Pfannschmidt) Date: Sun, 4 Dec 2016 15:03:56 +0100 Subject: [execnet-dev] Fwd: Windows support In-Reply-To: References: Message-ID: <20161204150356.122fba49@ronny-ownpc> windows is supported natively, remote Windows node startup is tricky because usually windows nodes do not have the ssh server, which is used to bootstrap a socketserver is shipped with execnet to enable ease of access to windows nodes. -- Ronny Am Mon, 28 Nov 2016 10:04:27 -0800 schrieb Prasanna Mulgaonkar : > Execnet documentation says Windows is supported. What I have is an > environment where the master node is a Ubuntu node, connecting to > clients. To date we have connected to various linux clients. > > Is Windows supported as a client node? Are there any specific > instructions on what needs to be installed on the Windows clients > (cigwin? versions of python?) that anyone has? Would love to find > out if this has been done (or is doable). > > Thanks. > > --prasanna > From anto.cuni at gmail.com Tue Dec 6 05:22:49 2016 From: anto.cuni at gmail.com (Antonio Cuni) Date: Tue, 6 Dec 2016 11:22:49 +0100 Subject: [execnet-dev] Fwd: Windows support In-Reply-To: <20161204150356.122fba49@ronny-ownpc> References: <20161204150356.122fba49@ronny-ownpc> Message-ID: Hi Ronny, On Sun, Dec 4, 2016 at 3:03 PM, Ronny Pfannschmidt < opensource at ronnypfannschmidt.de> wrote: > > windows is supported natively, > > remote Windows node startup is tricky because usually windows nodes do > not have the ssh server, which is used to bootstrap > > a socketserver is shipped with execnet to enable ease of access to > windows nodes. > ?what about security? I had a quick look to socketserver.py and it seems it does not perform any kind of authentication. Does it mean that if I start socketserver.py, everyone can execute arbitrary code on my machine? ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at merlinux.eu Tue Dec 6 06:08:16 2016 From: holger at merlinux.eu (holger krekel) Date: Tue, 6 Dec 2016 12:08:16 +0100 Subject: [execnet-dev] Fwd: Windows support In-Reply-To: References: <20161204150356.122fba49@ronny-ownpc> Message-ID: <20161206110816.GO3538@merlinux.eu> On Tue, Dec 06, 2016 at 11:22 +0100, Antonio Cuni wrote: > Hi Ronny, > > On Sun, Dec 4, 2016 at 3:03 PM, Ronny Pfannschmidt < > opensource at ronnypfannschmidt.de> wrote: > > > > > windows is supported natively, > > > > remote Windows node startup is tricky because usually windows nodes do > > not have the ssh server, which is used to bootstrap > > > > a socketserver is shipped with execnet to enable ease of access to > > windows nodes. > > > > ?what about security? I had a quick look to socketserver.py and it seems it > does not perform any kind of authentication. Does it mean that if I start > socketserver.py, everyone can execute arbitrary code on my machine? > ? Yes, exactly! It kind of presumes some kind of VPN or other ways of narrowing network access. holger From prasanna.mulgaonkar at gmail.com Tue Dec 6 11:56:48 2016 From: prasanna.mulgaonkar at gmail.com (Prasanna Mulgaonkar) Date: Tue, 6 Dec 2016 08:56:48 -0800 Subject: [execnet-dev] Fwd: Windows support In-Reply-To: <20161206110816.GO3538@merlinux.eu> References: <20161204150356.122fba49@ronny-ownpc> <20161206110816.GO3538@merlinux.eu> Message-ID: <9cdbd213-b6b7-15e9-511a-1ca381bfb40c@gmail.com> Has anyone experimented with the Microsoft provided Win32 OpenSSH implementation from https://github.com/PowerShell/Win32-OpenSSH? We are planning to play with it in the next few days and will report back what we find. --prasanna On 12/06/2016 03:08 AM, holger krekel wrote: > On Tue, Dec 06, 2016 at 11:22 +0100, Antonio Cuni wrote: >> Hi Ronny, >> >> On Sun, Dec 4, 2016 at 3:03 PM, Ronny Pfannschmidt < >> opensource at ronnypfannschmidt.de> wrote: >> >>> windows is supported natively, >>> >>> remote Windows node startup is tricky because usually windows nodes do >>> not have the ssh server, which is used to bootstrap >>> >>> a socketserver is shipped with execnet to enable ease of access to >>> windows nodes. >>> >> ?what about security? I had a quick look to socketserver.py and it seems it >> does not perform any kind of authentication. Does it mean that if I start >> socketserver.py, everyone can execute arbitrary code on my machine? >> ? > Yes, exactly! It kind of presumes some kind of VPN or other ways of narrowing network access. > > holger -------------- next part -------------- An HTML attachment was scrubbed... URL: From krisp1506 at gmail.com Wed Dec 14 02:46:34 2016 From: krisp1506 at gmail.com (Kishor Pawar) Date: Wed, 14 Dec 2016 07:46:34 +0000 Subject: [execnet-dev] getting execnet work from linux to windows Message-ID: Hello Devs, I am trying to execute some python/powershell code from linux box to remote windows machine on aws. I have install openSSH on window machine, I can connect to windows machine from terminal. Though I could not be able connect same windows machine using *execnet.* I have explain this scenario on stackoverflow . I doubt that firewall on windows is restricting *execnet* if *execnet* is trying to connect on port other than 22. May I know if that is the case, so that I can add rule to allow inbound connection on that port. Thanks -- *Thanks & Regards* *Kishor Pawar* *The Trouble with the world is that Stupids are Full of Confidence and The Intelligent are Full of Doubts.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel at danielstender.com Tue Dec 27 08:30:56 2016 From: daniel at danielstender.com (Daniel Stender) Date: Tue, 27 Dec 2016 14:30:56 +0100 Subject: [execnet-dev] testing/test_gateway.py::TestBasicGateway::test_gateway_status_busy[thread-popen] FAILED Message-ID: <41800a3e-86c3-dc91-8e55-11d3d261ba37@danielstender.com> Hi, with our Debian package, we've got this test failure here during a test build: testing/test_gateway.py::TestBasicGateway::test_gateway_status_busy[thread-popen] FAILED =========================== short test summary info ============================ SKIP [3] /<>/testing/conftest.py:148: no python3.2 found SKIP [3] /<>/testing/conftest.py:148: no jython found SKIP [3] /<>/testing/conftest.py:148: no python2.6 found SKIP [3] /<>/testing/conftest.py:148: no pypy found SKIP [3] /<>/testing/conftest.py:148: no python3.3 found SKIP [36] /usr/lib/python2.7/dist-packages/_pytest/config.py:1142: no 'gspecs' option found =================================== FAILURES =================================== ___________ TestBasicGateway.test_gateway_status_busy[thread-popen] ____________ self = gw = def test_gateway_status_busy(self, gw): numchannels = gw.remote_status().numchannels ch1 = gw.remote_exec("channel.send(1); channel.receive()") ch2 = gw.remote_exec("channel.receive()") ch1.receive() status = gw.remote_status() assert status.numexecuting == 2 # number of active execution threads assert status.numchannels == numchannels + 2 ch1.send(None) ch2.send(None) ch1.waitclose() ch2.waitclose() for i in range(10): status = gw.remote_status() if status.numexecuting == 0: break else: > pytest.fail("did not get correct remote status") E Failed: did not get correct remote status testing/test_gateway.py:88: Failed Could this be prevented somehow? Thanks for comments, DS P.S. I've got three test failures more, I'm going to post this as separate emails each. -- 4096R/DF5182C8 Debian Developer (stender at debian.org) LPIC-1 (LPI000329859 64mz6f7kt4) http://www.danielstender.com/ From daniel at danielstender.com Tue Dec 27 08:35:42 2016 From: daniel at danielstender.com (Daniel Stender) Date: Tue, 27 Dec 2016 14:35:42 +0100 Subject: [execnet-dev] testing/test_channel.py::TestStringCoerce::test_2to3 FAILED Message-ID: <7a02bb9e-7157-f0d6-eb9b-5a6ec77b67f2@danielstender.com> A failure on Python 2.7 from Debian CI testing [1]: testing/test_channel.py::TestStringCoerce::test_2to3 FAILED {...} =================================== FAILURES =================================== __________________________ TestStringCoerce.test_2to3 __________________________ self = makegateway = > @pytest.mark.skipif('sys.version>="3.0"') def test_2to3(self, makegateway): python = _find_version('3') gw = makegateway('popen//python=%s' % python) ch = gw.remote_exec('channel.send(channel.receive());'*2) ch.send('a') > res = ch.receive() testing/test_channel.py:351: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = , timeout = None def receive(self, timeout=None): """receive a data item that was sent from the other side. timeout: None [default] blocked waiting. A positive number indicates the number of seconds after which a channel.TimeoutError exception will be raised if no item was received. Note that exceptions from the remotely executing code will be reraised as channel.RemoteError exceptions containing a textual representation of the remote traceback. """ itemqueue = self._items if itemqueue is None: raise IOError("cannot receive(), channel has receiver callback") try: x = itemqueue.get(timeout=timeout) except self.gateway.execmodel.queue.Empty: raise self.TimeoutError("no item after %r seconds" % (timeout)) if x is ENDMARKER: itemqueue.put(x) # for other receivers > raise self._getremoteerror() or EOFError() E EOFError: couldnt load message header, expected 9 bytes, got 0 execnet/gateway_base.py:737: EOFError ----------------------------- Captured stderr call ----------------------------- Exception ignored in: Traceback (most recent call last): File "", line 602, in __del__ AttributeError: 'Channel' object has no attribute '_closed' Thanks for comments, DS [1] https://ci.debian.net/data/packages/unstable/amd64/e/execnet/20161225_212223.autopkgtest.log.gz -- 4096R/DF5182C8 Debian Developer (stender at debian.org) LPIC-1 (LPI000329859 64mz6f7kt4) http://www.danielstender.com/ From daniel at danielstender.com Tue Dec 27 08:38:08 2016 From: daniel at danielstender.com (Daniel Stender) Date: Tue, 27 Dec 2016 14:38:08 +0100 Subject: [execnet-dev] testing/test_basics.py::test_stdouterrin_setnull[thread] FAILED Message-ID: And finally, another failure running on Python 3.5 [1]: testing/test_basics.py::test_stdouterrin_setnull[thread] FAILED =========================== short test summary info ============================ SKIP [3] /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:148: no pypy found SKIP [3] /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:148: no python3.3 found SKIP [3] /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:148: no python2.7 found SKIP [3] /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:148: no jython found SKIP [3] /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:148: no python3.2 found SKIP [3] /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:148: no python2.6 found =================================== FAILURES =================================== _______________________ test_stdouterrin_setnull[thread] _______________________ execmodel = @pytest.mark.skipif("not hasattr(os, 'dup')") def test_stdouterrin_setnull(execmodel): cap = py.io.StdCaptureFD() gateway_base.init_popen_io(execmodel) os.write(1, "hello".encode('ascii')) if os.name == "nt": os.write(2, "world") os.read(0, 1) out, err = cap.reset() assert not out > assert not err E assert not "/tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/test_basics.py:215: ResourceWarning...file <_io.TextIOWrapper name=1 mode='w' encoding='UTF-8'>\n setattr(sys, patchsysdict[self.targetfd], self._oldsys)\n" testing/test_basics.py:222: AssertionError ----------------------------- Captured stderr call ----------------------------- /usr/lib/python3/dist-packages/py/_io/capture.py:77: ResourceWarning: unclosed file <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'> setattr(sys, patchsysdict[self.targetfd], self._oldsys) ============================ pytest-warning summary ============================ WI1 /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:21 'pytest_runtest_setup' hook uses deprecated __multicall__ argument WC1 None pytest_funcarg__specsocket: declaring fixtures using "pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 4.0. Please remove the prefix and use the @pytest.fixture decorator instead. WC1 None pytest_funcarg__specssh: declaring fixtures using "pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 4.0. Please remove the prefix and use the @pytest.fixture decorator instead. !!!!!!!!!!!!!!!!!!!! Interrupted: stopping after 1 failures !!!!!!!!!!!!!!!!!!!! ====== 1 failed, 18 passed, 18 skipped, 3 pytest-warnings in 0.78 seconds ====== Thank you for any comments in advance, Daniel Stender [1] https://ci.debian.net/data/packages/unstable/amd64/e/execnet/20161225_212223.autopkgtest.log.gz -- 4096R/DF5182C8 Debian Developer (stender at debian.org) LPIC-1 (LPI000329859 64mz6f7kt4) http://www.danielstender.com/ From daniel at danielstender.com Tue Dec 27 08:33:27 2016 From: daniel at danielstender.com (Daniel Stender) Date: Tue, 27 Dec 2016 14:33:27 +0100 Subject: [execnet-dev] testing/test_gateway.py::TestTracing::test_popen_stderr_tracing FAILED Message-ID: <80f93e8e-de3f-d514-28d0-1505cb009ca4@danielstender.com> Another test failure, from another environment: testing/test_gateway.py::TestTracing::test_popen_stderr_tracing FAILED {...} =================================== FAILURES =================================== ____________________ TestTracing.test_popen_stderr_tracing _____________________ self = capfd = <_pytest.capture.CaptureFixture instance at 0x7f439eae9710> monkeypatch = <_pytest.monkeypatch.MonkeyPatch instance at 0x7f439eae97e8> makegateway = > def test_popen_stderr_tracing(self, capfd, monkeypatch, makegateway): monkeypatch.setenv('EXECNET_DEBUG', "2") gw = makegateway("popen") pid = gw.remote_exec("import os ; channel.send(os.getpid())").receive() out, err = capfd.readouterr() slave_line = "[%s] creating slavegateway" % pid > assert slave_line in err E assert '[13247] creating slavegateway' in '8>\n[13247] gw0-slave [serve] spawning receiver thread\n[13247] gw0-slave [serve] integrating as primary thread\n[13247]...hed\n[13247] gw0-slave sent \n[13247] gw0-slave 1 sent channel close message\n' testing/test_gateway.py:391: AssertionError ============================ pytest-warning summary ============================ WI1 /build/execnet-1.4.1/testing/conftest.py:21 'pytest_runtest_setup' hook uses deprecated __multicall__ argument WC1 None pytest_funcarg__specsocket: declaring fixtures using "pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 4.0. Please remove the prefix and use the @pytest.fixture decorator instead. WC1 None pytest_funcarg__specssh: declaring fixtures using "pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 4.0. Please remove the prefix and use the @pytest.fixture decorator instead. !!!!!!!!!!!!!!!!!!!! Interrupted: stopping after 1 failures !!!!!!!!!!!!!!!!!!!! 1 failed, 229 passed, 607 skipped, 5 xfailed, 3 pytest-warnings in 15.21 seconds Thanks for any comments, DS -- 4096R/DF5182C8 Debian Developer (stender at debian.org) LPIC-1 (LPI000329859 64mz6f7kt4) http://www.danielstender.com/ From holger at merlinux.eu Wed Dec 28 04:56:25 2016 From: holger at merlinux.eu (holger krekel) Date: Wed, 28 Dec 2016 10:56:25 +0100 Subject: [execnet-dev] testing/test_basics.py::test_stdouterrin_setnull[thread] FAILED In-Reply-To: References: Message-ID: <20161228095625.GC3079@merlinux.eu> Please submit issues and describe how to reproduce it: https://bitbucket.org/hpk42/execnet/issues?status=new&status=open thanks, holger On Tue, Dec 27, 2016 at 14:38 +0100, Daniel Stender wrote: > And finally, another failure running on Python 3.5 [1]: > > > testing/test_basics.py::test_stdouterrin_setnull[thread] FAILED > =========================== short test summary info ============================ > SKIP [3] /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:148: no pypy found > SKIP [3] /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:148: no python3.3 found > SKIP [3] /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:148: no python2.7 found > SKIP [3] /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:148: no jython found > SKIP [3] /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:148: no python3.2 found > SKIP [3] /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:148: no python2.6 found > > =================================== FAILURES =================================== > _______________________ test_stdouterrin_setnull[thread] _______________________ > > execmodel = > > @pytest.mark.skipif("not hasattr(os, 'dup')") > def test_stdouterrin_setnull(execmodel): > cap = py.io.StdCaptureFD() > gateway_base.init_popen_io(execmodel) > os.write(1, "hello".encode('ascii')) > if os.name == "nt": > os.write(2, "world") > os.read(0, 1) > out, err = cap.reset() > assert not out > > assert not err > E assert not "/tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/test_basics.py:215: ResourceWarning...file <_io.TextIOWrapper name=1 mode='w' encoding='UTF-8'>\n setattr(sys, patchsysdict[self.targetfd], self._oldsys)\n" > > testing/test_basics.py:222: AssertionError > ----------------------------- Captured stderr call ----------------------------- > /usr/lib/python3/dist-packages/py/_io/capture.py:77: ResourceWarning: unclosed file <_io.TextIOWrapper name=0 mode='r' encoding='UTF-8'> > setattr(sys, patchsysdict[self.targetfd], self._oldsys) > ============================ pytest-warning summary ============================ > WI1 /tmp/autopkgtest-virt-lxc.shared._hf0fuxh/downtmp/build.zbb/execnet-1.4.1/testing/conftest.py:21 'pytest_runtest_setup' hook uses deprecated __multicall__ argument > WC1 None pytest_funcarg__specsocket: declaring fixtures using "pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 4.0. Please remove the prefix and use the @pytest.fixture decorator instead. > WC1 None pytest_funcarg__specssh: declaring fixtures using "pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 4.0. Please remove the prefix and use the @pytest.fixture decorator instead. > !!!!!!!!!!!!!!!!!!!! Interrupted: stopping after 1 failures !!!!!!!!!!!!!!!!!!!! > ====== 1 failed, 18 passed, 18 skipped, 3 pytest-warnings in 0.78 seconds ====== > > > Thank you for any comments in advance, > Daniel Stender > > [1] https://ci.debian.net/data/packages/unstable/amd64/e/execnet/20161225_212223.autopkgtest.log.gz > > -- > 4096R/DF5182C8 > Debian Developer (stender at debian.org) > LPIC-1 (LPI000329859 64mz6f7kt4) > http://www.danielstender.com/ > _______________________________________________ > execnet-dev mailing list > execnet-dev at python.org > https://mail.python.org/mailman/listinfo/execnet-dev