Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

37 Excellent

About cas

  • Rank

Contact / Social Media

Profile Information

  • Gender
  • Interests
    Atari 8Bit
  1. this can be true, I'm pretty sure I've found window.obj somewhere and used it from Turbo-Basic. When I switched over to ACTION!, I've made the ACTION! glue code, but never used it, as in ACTION! it is just simple to write own windowing routines. -- CS
  2. Thanks for giving this information, I'm always interested in programming language concepts. I need to find some time to work with PL65 it seems
  3. the current blog system is too heavy-weight, I plan to move to a lightweight static page blog system. I do not have much free time, so it is moving slowly. But there will be a new content and a new blog at some point of time. The regional group in Frankfurt is still doing strong, but I now live 300 KM away and have a small kid, so I'm not able to attend their meetings. But I meet with Beetle (Stefan) from time to time and do Atari stuff. Greetings Carsten
  4. I've now added WINDOW.OBJ to the atariwiki page (attachment). I remember using these ASM routines first from Turbo-Basic, them later I wrote the ACTION! interface, but never really used it in any applicaitons. The WINDOW.OBJ has not been written by me, I don't remember the origins. -- CS
  5. Sorry, my fault. I will look for the missing file in my disk collection and upload it. Wait for a message here ... Carsten
  6. Just HTTP. I've build a protoype of the new Infothek system, but there was never consensus among the team members how to proceed, that is the reason why the files are still only available this way.
  7. https://atariwiki.orgnow has a Certificate from the "let's encrypt" (Beta) project. To get a A+ ranking from ssllabs.com, I had to cut off some old operating-systems and browsers. This certificate should be trusted by major browsers. Please let me know if you encounter any issues
  8. It has been almost 10 years since I've worked on this, as far as I remember I've contacted LCSI first and they connected me with Mr. Papert, as they didn't had any traces of Atari Logo (at the time). It might be worth a try to start the process again with contacting LCSI, or Cynthia Solomon ( https://en.wikipedia.org/wiki/Cynthia_Solomon).
  9. Well, no. I was in contact with Mr. Seymour Papert (or his office) about Atari Logo back in Summer 2006. Then Mr. Papert had a terrible accident in December 2006 ( https://en.wikipedia.org/wiki/Seymour_Papert#Accident_in_Hanoi) and was unavailable, and I did not follow up. Not sure if I would like to bother him again with the question.
  10. The certificate on the site changes every 6 month. Publishing a cert fingerprint in email or forum-posts does not scale, importing the sites certificate into the browser trust store also does not scale. The real solution is certificate verification via DNSSEC secured DNS, aka DANE. Unfortunaly DANE is not supported natively in the browsers today and requires an extension plugin. I guess we have to wait until the Mozilla/EFF certs are being available in summer.
  11. I know them and I know the Mozilla blog post. I would trust them much less than CACert. Starting and running a certification authority, especially one that has the root-cert in the browsers, is not cheap. It is expensive. How can they offer for free? Some people in the security business I've talked to have suspicion that these two companies are at least partly controlled by their governments/secret services (StartSSL = Israel, Wosign = China). With StartSSL, the inital certificate is free, but any change/revoke in case of a security incident (such as Heartbleed) costs money https://www.techdirt.com/articles/20140409/11442426859/shameful-security-startcom-charges-people-to-revoke-ssl-certs-vulnerable-to-heartbleed.shtml I don't see these two companies as a trustworthy option for getting TLS certificates. I meet (some) CACert people at open source conferences. In person. Their procedures might not be without flaws, but in my view much more trustworthy than WoSign or StartSSL. Carsten
  12. Hi Ken, I'm the admin of "atariwiki.org" and responsible for the TLS cert. Currently, there are no free and trustworthy TLS certs available. The cert we currently use is issued by CACert http://cacert.org/ CACert is a community certificate authority. The CACert Root-Certificate is not shipped by default in common browsers. In order to resolve the issue, users need to import the CACert Root-Certificate into their browser. The CACert root-certificate can be found on their website. Given that the common Internet-User is trusting all kinds of shady CAs that are shipped with the browser, adding CACert should not be an issue. Later this year Mozilla and EFF will start issuing free TLS certs as part of their "let's encrypt" campaing https://letsencrypt.org/ Once these certs are available, I will switch. Mozilla has promised that the root-certs for "lets encrypt" will be in the browser default root-certs store. A trustworthy TLS cert costs around 350 Euro per domain-name and year. For the Atariwiki-Site, we have 3 domains. The cost would be around 1.000 Euro per year. I'm open for donations. Authentication of the TLS cert independent of the CACert root-cert can be done by installing the DNSSEC-Validator plugin: https://www.dnssec-validator.cz/
  13. Correct. But no user should (blindly) "trust" the CAs pre-installed in their browser. IMHO CACert, as a community driven CA, is more trustworthy than many of the government or commercial CAs. The current CA "trust" model is very much broken, the new DANE model of checking the certificates against a fingerprint in DNSSEC secured DNS is the way forward (instead of a long list of "trusted" CAs in the browser). Once the certificates from EFF/Mozilla "let's encrypt" will be available in summer 2015, I will probably switch to their certificates, which EFF/Mozilla promise will also be in the browsers CA store.
  14. In my view collaboration (working in a team) on Github is easier. It is not so much about 'git' as a tool, which is also available from SF. I will use SF, as JAC is more familliar with it. I had my projects on SF too, but after SF has been sold multiple times, my feeling is that the new owners just try to make as much money as possible with advertising and tracking of users. Github has a better business model, they charge for non-open-source projects, and the page is advertising free. But the main benefit is the way how code can be forked into local repos and then merged again, that makes collaboration on a project easier.
  15. Hi JAC, I would have preferred github over sourceforge, the quality of sf is poor these days, it is a faint copy of its better days, it has so many advertising, tracking and even add-on-downloads. Too commercial for my taste. For collaborating, github is so much nicer.
  • Create New...