mlapointe | 2 Oct 13:12 2014
Picon

Re: Using Pyro over 2 networks, Vol 90, Issue 1

Hi, Richard

I think my problème is very similair than your, and i think i have a part of solution

RTssh = Reverse ssh tunnelling
TSSH = Tunnelling Via SSH

PC 1 -RTSSH>-PC 2(Cloud server)-TSSH-≤---PC 3
I have this topology working (But only with standard Pyro object) i dont know Why but Pyro Flame Object not
working. Is my Thread subject to.



Martin Lapointe
Technicien
mlapointe <at> ebr.ca

Informatique EBR Inc.
365, rue Racine Est, Bureau 204
Chicoutimi (Qc) G7H 1S8 Canada
Tél.:(418) 543-2600 # 2119
Sans frais: 1 (800) 567-2336
Fax : (418) 543-0363

Devez-vous vraiment imprimer ce courriel? Pensez à l’environnement…
Ce message est confidentiel et est à l'usage exclusif de son destinataire.  Il est strictement interdit à
toute autre personne de le diffuser, le distribuer ou le reproduire.  Si le destinataire ne peut être
joint ou vous est inconnu, veuillez informer l'expéditeur par courrier électronique immédiatement
et effacer ce message et en détruire toute copie.

(Continue reading)

mlapointe | 2 Oct 13:00 2014
Picon

Pyro4 Flame SSH Reverse Tunneling

Hi,
If you have somme times guys can you just help my a bit.

If i have somme question about pyro4 (Flame) and reverse tunneling SSH.
I have looking for a while and i can do work on reverse ssh standard Pyro4 object but not Pyro4 flame object ;(

Thank for your help,

Cordialement,



Ne manquez pas notre «Symposium 2014 : LE rendez-vous des géants en TI» le mardi 28 octobre prochain à l’hôtel Château Laurier!

Inscrivez-vous dès maintenant : www.ebr.ca/evenements/symposiumqc2014

 

Martin Lapointe
Technicien
mlapointe-bqQSNgnW8RQ@public.gmane.org

Informatique EBR Inc.
365, rue Racine Est, Bureau 204
Chicoutimi (Qc) G7H 1S8
Tél.:(418) 543-2600 # 2119
Sans frais: 1 (800) 567-2336
Fax : (418) 543-0363
http://www.ebr.ca

P  Devez-vous vraiment imprimer ce courriel? Pensez à l’environnement…
Ce message est confidentiel et est à l'usage exclusif de son destinataire.  Il est strictement interdit à toute autre personne de le diffuser, le distribuer ou le reproduire.  Si le destinataire ne peut être joint ou vous est inconnu, veuillez informer l'expéditeur par courrier électronique immédiatement et effacer ce message et en détruire toute copie.

 


------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Pyro-core mailing list
Pyro-core@...
https://lists.sourceforge.net/lists/listinfo/pyro-core
Richard | 1 Oct 23:34 2014
Picon

Using Pyro over 2 networks

I would like to access remote data crossing 2 networks:
Say PC 1 can ssh to PC 2, and PC 2 can ssh to PC 3, but 1 and 3 cannot 
see each other directly - they are on different network segments.
How could I access PC 3 from PC 1 using Pyro?
I am thinking of using 2 name (or flame) servers...
Any ideas?

Richard van Bemmelen

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
Irmen de Jong | 25 Sep 22:38 2014
Picon

Pyro 4.28 released!


Hi,

Pyro 4.28 has just been released!
It's a small but important update to the previous version.

Get it from Pypi:  http://pypi.python.org/pypi/Pyro4/
Or straight from Github:  https://github.com/irmen/Pyro4
Documentation: http://pythonhosted.org/Pyro4/index.html

Most important fix in this release is that remotely accessing double-underscore
methods (__whatever__) works again. This was impossible in the previous release
because they were considered private, and they're not. Other changes:

implemented dir() on a Proxy to also return remote methods if known (useful for
autocompletion in certain python shells)
USE_MSG_WAITALL config item added because there remain certain other systems where
MSG_WAITALL is unreliable
removed Pyro4.socketutil.USE_MSG_WAITALL attribute (because it got promoted to a
config item)

Have fun!

Irmen de Jong

Irmen de Jong | 17 Sep 23:21 2014
Picon

Pyrolite 4.2 released (with important bugfix regarding floats and double arrays)


Hi,

I've released a new version (4.2) of Pyrolite, the native-Java and .Net library to
interface with Pyro and Python/pickle.

Changes:

fixed endianness mixup in decoding float and double arrays, will now actually decode
to the correct values!
metadata feature added to Pyro proxy (introduced in Pyro 4.27)
updated Flame method names (changed in Pyro 4.27)
C# proxy now is a DynamicObject and supports dynamic method calling as well.
added getattr and setattr to proxy

Get it at: https://github.com/irmen/Pyrolite
Binaries at: http://irmen.home.xs4all.nl/pyrolite/

Have fun,

Irmen de Jong
Irmen de Jong | 8 Sep 10:14 2014
Picon

pyro 4.27 breaks access to __whatever__ methods

Hi,

I think I made a mistake in the last Pyro version by considering every method starting
with _ or __ a private method. But Python itself treats "dunder" methods differently
(not private!). This means that in 4.27 it is no longer possible to access remote
methods named "__method__".

Note that the same problem already existed in the previous Pyro version (4.26) if you
enabled DOTTEDNAMES.

This is unintentional and I'm planning to fix this for 4.28. If your code depends on
remote double-underscore method names, please wait with upgrading Pyro until the next
release.  Note that an exception will be made only for the double-underscore methods,
any other method starting with an underscore will still be treated as private and
inaccessible.

https://github.com/irmen/Pyro4/issues/57

Irmen

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
F.C | 28 Aug 00:05 2014
Picon

serpent serialization

Hi!!


I can't  use Pyro, the pyro remote server is working well, but when i try to connect the client :

flame=Pyro4.utils.flame.connect("192.168.1.72:64444")

i have this error:

Pyro4.errors.ProtocolError: serializer 'serpent' is unknown or not available


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Pyro-core mailing list
Pyro-core@...
https://lists.sourceforge.net/lists/listinfo/pyro-core
Irmen de Jong | 7 Aug 23:36 2014
Picon

Pyro 4.27 released! Massive update


Hi,

Pyro 4.27 has just been released!
It's a massive update so the .01 version bump is a bit deceiving.

Get it from Pypi:  http://pypi.python.org/pypi/Pyro4/
Or straight from Github:  https://github.com/irmen/Pyro4
Documentation: http://pythonhosted.org/Pyro4/index.html

Most important new features in this version:

added  <at> Pyro4.expose and  <at> Pyro4.oneway decorators
remote attribute access works on the proxy and also actually honors 'private'
attributes (and methods) in all cases (names starting with underscore)
automatic metadata query: proxy asks server for metadata about the object (methods,
attributes)
this means you no longer have to set _pyroOneway yourself, support for this will be
dropped in the next version
the expose decorator can be used to selectively expose only certain methods. This
does require setting REQUIRE_EXPOSE config item to true (it's not enabled by default
to remain backwards compatible)
DOTTEDNAMES is deprecated and will be removed in the next version
setup script now generates a bunch of console commands such as 'pyro4-ns'
(previously you had to type 'python -m Pyro4.naming' etc.)
requires serpent 1.7 or newer

Exhaustive list of changes can be found in the change log, as usual.

Have fun!

Irmen de Jong
Nicco Kunzmann | 19 Jul 15:02 2014
Picon

Sample Project with Pyro, Pyrolite, C#, Java, Python

Hello,

in a seminar about components and middleware we created a 'slim breakout' version with Pyro.
We successfully used Pyrolite and Pyro with C#, Java and Python. https://github.com/niccokunzmann/ping/
We had a presentation and a discussion about our implementation.
Maybe you can use it to see where we had struggles.

If you have any questions, contact me,
greetings,
Nicco
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Pyro-core mailing list
Pyro-core@...
https://lists.sourceforge.net/lists/listinfo/pyro-core
Justin M Wozniak | 18 Jul 17:57 2014

Trouble with getitem

Hi
     I'm having trouble with Pyro and the getitem syntax.  I am 
basically trying to use __getitem__ on the proxy.  A stand-alone test is 
attached.

In short, the server class has:
     def __getitem__(self, key):
         message("__getitem__")
         return self.getitem(key)

and the client has:
     proxy = Pyro4.Proxy(uri)
     value3 = proxy[key3]

which results in:
TypeError: 'Proxy' object has no attribute '__getitem__'

If anyone can help me get this working it would be greatly appreciated.

     Thanks
     Justin

--

-- 
Justin M Wozniak

Attachment (TestClient1.py): text/x-python, 1250 bytes
Attachment (TestService1.py): text/x-python, 1150 bytes
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Pyro-core mailing list
Pyro-core@...
https://lists.sourceforge.net/lists/listinfo/pyro-core
obrien | 17 Jul 02:52 2014
Picon

(no subject)

Please remove me from your distribution list. I've asked at least twice.
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Pyro-core mailing list
Pyro-core@...
https://lists.sourceforge.net/lists/listinfo/pyro-core

Gmane