1. Forum
  2. Usenet
  3. COMP.SYS.APPLE2

  • Re: Is TLS for the IIgs coming later?

    From Andrew Roughan@21:1/5 to Stephen Heumann on Sat Jul 27 13:49:43 2024
    Stephen Heumann <stephenheumann@gmail.com> wrote:
    On 7/23/24 9:46 AM, D Finnigan wrote:
    Availability of these hashes and ciphers brings us one step closer to a TLS >> library for the Apple IIgs.

    I actually wrote most of the 65816-crypto package years ago, partially
    with TLS in mind

    Following up publicly after private email seems to have not gotten through (spam perhaps)

    I see you have your own crypto routine library.
    Were you aware of the hashtool and crypto toolsets? I’d be interested in hearing your thoughts about this model of providing routines for
    application reuse. And perhaps you may consider contributing your code to
    them or taking them over?
    QKumba has implemented cha-cha which I requested and should include at some point.

    I think all the available ciphers for IIgs are now deprecated which makes establishing a connection more challenging when the goal posts keep
    changing. Perhaps we can offload the encryption / decryption to some other mechanism (perhaps UltimateDrive could be used).

    Regards
    Andrew

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Oliver Schmidt@21:1/5 to All on Tue Jul 30 06:38:47 2024
    Hi Stephen,

    Perhaps we can offload the encryption / decryption to some other
    mechanism (perhaps UltimateDrive could be used).

    [...] some sort of offload mechanism
    might well be more practical than doing everything on the GS.

    I don't know what the UltimateDrive brings to the table that you desire,
    but...

    1.

    The A2Pico:
    * is software-defined hardware
    * is open source - both hardware and firmware
    * is very DIY friendly due to its through-hole variant without any chips to
    be programmed
    * is available as completely assembled SMD variant for a pretty affordable price
    * comes with a reusable library that contains the code necessary to
    communicate with the A2
    * can easily be programmed in C

    2.

    If you define a "crypto accelerator" software interface based on a
    SmartPort character device, then this interface can be implemented both
    * internally (i.e. based on A2Pico)
    * externally (i.e. based on FujiNet)
    in a similar way a "usual" SmartPort block device can be implemented both internally (i.e. CFFA3000) and externally (i.e. Floppy Emu).

    Oliver

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)