Why do people use Quicklisp although it is known to be vulnerable to man-in-the-middle attacks?

• quicklisp-client

  6 285 0.0 Common Lisp

  Quicklisp client.

I agree 100% about needing to test and audit for security. But based on the information I've seen and public activity in repos, I assumed Xach was going for home-grown CL implementation. https://github.com/quicklisp/quicklisp-client/blob/pgp/quicklisp/openpgp.lisp

• quicklisp-projects

  8 412 8.2

  Metadata for projects tracked by Quicklisp.

As for the packages themselves, you can look at the repository information for each package at https://github.com/quicklisp/quicklisp-projects and use that to get the packages yourself manually. Most of them just use the latest commit in the package's respective git repos. A few use specific tags. Some, have to be gotten by other means. It is always possible, by looking at the quicklisp update data listing all the packages, to get the url for the package tarballs on the quicklisp server and download them manually.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• quicklisp-https

  3 1 0.0 Common Lisp

https://github.com/snmsts/quicklisp-https/blob/master/quicklisp-https.asd#L7 ?

• aserve

  3 189 4.7 Common Lisp

  AllegroServe, a web server written in Common Lisp

i believe Allegroserve on ACL also natively supports TLS v1.0.

Suggest a related project