Would I be right in assuming that the example echoserv_ssl.py and
echoclient_ssl.py will only result in encryption from the client to server and
not from the server back to the client?
Im referencing these examples specifically,
http://twistedmatrix.com/projects/core/documentation/examples/echoc
Can somebody point me into the right direction in how to switch out
checkers.InMemoryUsernamePasswordDatabaseDontUse with something that would
authenticate linux users, like root?
On some things i just cant seem to get past documentation and api docs.
Hoping for a slight push in the right dire
-
From: "Paul Swartz"
Sent: Thursday, May 14, 2009 12:11 PM
To: as...@impactdamage.com, "Twisted general discussion"
Subject: SPAM-LOW: Re: [Twisted-Python] Conch Checkers Help
On 05/14/2009 07:14 PM, asset wrote:
> Can somebody point me into the rig
Ive been at it for several days now trying to get at the username
(avatarId), session id (SSHChannel session # I imagine), and terminal
protocol instance (recvline.HistoricRecvLine) of my application's SSH
terminal service's clients. Specifically, I'm trying to expose these three
things (for a
!
--
On Sat, 4 Jul 2009 02:11:36 -0700, asset wrote:
>Ive been at it for several days now trying to get at the username
>(avatarId), session id (SSHChannel session # I imagine), and terminal
>protocol instance (recvline.HistoricRecvLine) of my application's SSH
>terminal
Using the current trunk r27366 (which is after #4014 fixed a related
issue), I am having trouble with an implementation of web.guard wrapped
XMLRPC. This is a new test implementation to expose both a soap and xmlrpc
interface. SOAP works, but xmlrpc throws UnsupportedMethod POST.
Here is my
I was indeed being tricked. I actually tested soap with a real client, but
with xmlrpc i was using the browser. I was expecting to see the same error
message, and instead got a new one that was presented by the modifications
I pulled out of the trunk to support the issue in #4014. I was expect
