[Oberon] Oberon and TLS; was A2.

eas lab lab.eas at gmail.com
Wed Oct 12 05:14:10 CEST 2016


!! You've just given me a new idea:
Because the RPi can do the required magic-HCI via ALO and wily,
and Win8.1-laptop can do the inet fetching,
a simple Ethernet-cable between RPi & laptop gives a usable system.

How difficult is it to talk from Win8.1 x64 to Linux?

It was no problem between RPi & a x86-linux.

Thanks for any pointers.

== Chris Glur.


On 10/9/16, eas lab <lab.eas at gmail.com> wrote:
> Peter, this old post only read now, since I lost my Gmail access.
>
> ]> Can it handle the <TLS> protocol needed for gmail;
>
> ]As I understand, you intend an Oberon workstation.  Native Oberon on
> ] a PC or Oberon as a subsystem of another system.  You require
> ] non-local communication to be within TLS.  Possible with a little
> ] elaboration.
>
> No, I just want to fetch my gmail; but they use TLS. And I want to
> use ETHO's system: where you can see/edit several received & pending
> texts, at one time, together, and you can freely edit a new/extra
> "Cc: entry", instead of a KFC pre-baked mentality thing where you
> must scroll to the top/or-bottom to read the controls, and lose your
> place in the text.
>
> ] * PC Native Oberon
> ]
> ] Years ago Guenter Feldmann implemented SSL for Oberon.  That might
> ] work for receiving mail from a smarthost.  I haven't tried
>
> Yes, I know about that. When I restore Linux-Oberon I'd like to be
> able to use that; but I don't find the documentation of how to
> interface his SSL to the mail-client and the ppp-transport.
>
> Or since LEO apparently interfaces to the linux <tcp/ip - sockets>:
> if perhaps linux can do the SSL?
> ................
> ] For receiving mail, install stunnel on the router.  Communication
> ] between Oberon and the router is through port 110 without TLS.
> ] Between the router and smarthost TLS is provided by stunnel.  In
> ] the example in https://en.wikipedia.org/wiki/Stunnel substitute
> ] POP3 for SMTP.
>
> I'm still trying to get Win-x64 httpS *TEXT-based* access.
> Full-browser http is intolerable, although perhaps not wikipedia.
>
> ] * Oberon subsystem running on another system.
> ]
> ] This is the above arrangement running on one machine rather than
> ] two.  The Oberon subsystem sends messages to localhost and
> ] retrieves from localhost.
>
> OK, that could be a tidy way to do it, because I can test the stages
> independantly. Have you tested a linux based ETHO communicating
> to <local host>? I've got a working RPi:ALO, but I've never confirmed
> if/that ALO communicates with the underlying linux <tcp/ip>, like LEO
> does.
>
> Nor do I understand how it works - at a physical level, compared to
> the old days, where the bytes where sent to the serial-port to drive
> the modem; so you could visualise the passage of bit3 of char("A")
> on its route to creating an audio-fequency wave of a calculatable
> duration, on the telephone-line.
>
> I miss my access to Guenter Feldmann's LEO which integated ETHO's
> magical interface with the inet and file-system of the underlying
> linux.
>
> ---- How would ETHO modified to ride-on-linux access <local host>?
> AFAIK: whereas <local host>'s *contents* is in the linux file-system;
> the <local host> is accessed by the <socket-system> which I know
> nothing about?
>
> ==Chris Glur.
>
>
> On 9/8/16, peter at easthope.ca <peter at easthope.ca> wrote:
>> Chris,
>>
>> From lab.eas at gmail.com  Mon Jan 18 19:08:45 2016
>>> Can it handle the <TLS> protocol needed for gmail;
>>
>> As I understand, you intend an Oberon workstation.  Native Oberon on
>> a PC or Oberon as a subsystem of another system.  You require
>> non-local communication to be within TLS.  Possible with a little
>> elaboration.
>>
>> * PC Native Oberon
>>
>> Years ago Guenter Feldmann implemented SSL for Oberon.  That might
>> work for receiving mail from a smarthost.  I haven't tried.  As
>> Oberon is distributed, authentication is absent    from SMTP; an
>> obvious snag for sending to some smarthosts.
>>
>> In addition to your workstation, set up a router system.  A Linux
>> router works nicely.  It should have a firewall such as provided by
>> Shorewall.  Nowadays it can be a machine fitting in the palm of
>> your hand.  The Oberon workstation sends a message to the Linux
>> router using port 25; no TLS.  The MTA on the router forwards the
>> message under TLS.  The default MTA in Debian Linux is Exim4. It
>> works here.
>>
>> For receiving mail, install stunnel on the router.  Communication
>> between Oberon and the router is through port 110 without TLS.
>> Between the router and smarthost TLS is provided by stunnel.  In
>> the example in https://en.wikipedia.org/wiki/Stunnel substitute
>> POP3 for SMTP.
>>
>> * Oberon subsystem running on another system.
>>
>> This is the above arrangement running on one machine rather than
>> two.  The Oberon subsystem sends messages to localhost and
>> retrieves from localhost.
>>
>> Regards,                ... Lyall E.
>>
>> --
>> 123456789 123456789 123456789 123456789 123456789 123456789 123456789
>> Tel +1 360 639 0202
>> http://easthope.ca/Peter.html Bcc: peter at easthope. ca
>>
>> --
>> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
>> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>>
>


More information about the Oberon mailing list