new uploads to my webpage

cawf410-2020-12-13.zip
Cawf 4.10 is the last version of the cawf nroff clone. Specializes in man manpages, can handle a subset of ms, me, mnx macros. Does not do mandoc :-( Output options include FWP, epson, pcl.

epson2ps-2020-12-13.zip
does a single-pass conversion of Epson x80 printer-ready text to simple postscript. Useful with cawf!

moontool327-20201217.zip
cute litte moon-display app.

These were all recompiled for 32-bit RISC OS with RO 5.28, DDE28 on a ARMv7 Raspberry Pi 2. All archives include full source.

Thanks Willard, I like the Moon display app.

+1

Nice to see someone giving some of these old items a bit of TLC.

BTW. Did you mean to quote www.members.sdc.org/~goosey/riscos locations?
I ask because I have my browser set to default to HTTPS and the www.members.sdc.org cleanly connect to the pages on HTTPS but the https://www.sdc.org fails with a certificate mismatch.

A check with the SSL Labs scanner gives a rapid response that the certificate is not valid for the domain. Pushing through with ignore certificate mismatch shows that the servers are not set up correctly (there’s still SSL3 support for example) scan results Here

Note the top end of the report where the domains members.sdc.org and www.members.sdc.org are listed as uses for the certificate but www.sdc.org is not.

You may want to have a word with the sdc.org maintainers to fix the various vulnerabilities. Most fixes would be simple: turn off support for SSL3 and turn off support for TLS 1.0 and 1.1, also removing the weak cipher suites would improve things.

To top and tail things: Thanks for making an effort to keep these items available in a modern form.

I have forwarded your comments to the sysadmin @sdc.org.

And thanks for the responses! :-) They really mean a lot right now! :-)

I have forwarded your comments to the sysadmin @sdc.org.

No problem. At present, it’s a minor item. I thought I’d mention it and then there’s less of a rush to make things work with some new release of browsers that demand the more recent security standards.
Basically add www.sdc.org to the alternate names on the certificate, turn off support for old TLS variants and SSL3 and then tidy up by removing the cipher suites identified as weak.

They could also consider dropping support for HTTP – make sure any HTTP connection is switched/diverted into a HTTPS connection.

+1 for moontool! :)