[Simh] Transferring data

[Sampsa Laine]

> On 22 Apr 2016, at 17:44, Johnny Billquist <bqt at softjar.se> wrote:
> 
> On 2016-04-22 16:39, Johnny Billquist wrote:
>> On 2016-04-22 16:25, Sampsa Laine wrote:
>>> 
>>> Actually we had this idea with Steve Davidson where we’d build a
>>> crypto-coprocessor in Python on the host OS and somehow hook it up
>>> (via say a serial port) to a PDP-11 and have the host OS do all the
>>> RSA, AES, SHA, MD5 operations that way and the SSH server on the
>>> PDP-11 would just be a shim to implement the SSH protocol.
>>> 
>>> It’s quite easily doable in Python since it comes with all the crypto
>>> libraries pre-built, Johnny, you interested in something like this for
>>> adding SSH to your RSX TCP/IP stack?
>> 
>> No. That would be pretty much meaningless, as there are options and
>> stuff done in SSH which affects what should happen on the system as
>> well. You cannot move ssh outside, and still have the functionality in
>> place.
> 
> Actually, if you talk about just offloading the crypto-work, I guess that could be done. But then you'd need some kind of device where you could pass certificates and encrypted streams, and get the results after those steps, as well as the reverse.

That is EXACTLY what we were thinking of doing..

> But that would mean implementing a sortof ssh that would depend on this special ssh-cyrpto-device to work, so not usable on a real pdp-11 (not that ssh will ever be possible on a real pdp-11 anyway).

Well, you COULD have the python-crypto-engine hooked up to a serial port on the PDP-11 and a UNIX box :)

> 
> I seriously doubt I'd ever do this, but if someone else wants to, they could grab my telnet server (sources are included), and just add the work in that code to deal with ssh.

If you do, let me know, I’m happy to write the crypto-engine..

> 
>> How do you think something like sftp works?
> This is somewhere where it gets even more interesting, as you here then need to fire off a process instead of giving a shell (or equivalent). And then deal with all the details of it.

No comments on this :)

Sampsa

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20160422/680aca04/attachment.sig>