clisp
quicklisp-client
clisp | quicklisp-client | |
---|---|---|
8 | 6 | |
- | 286 | |
- | - | |
- | 0.0 | |
- | 14 days ago | |
Common Lisp | ||
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
clisp
-
Common Lisp Implementations in 2023
One should note that while it is true that the last CLISP release was a long time ago and there is not a lot of development going on right now, it's not dead. Bruno Haible just commited last week.
The repository is now at https://gitlab.com/gnu-clisp/clisp
-
Common Lisp implementations in 2023
CLISP is maintained here: https://gitlab.com/gnu-clisp/clisp/-/commits/master
-
clisp-head from Roswell now has support for package-local nicknames
Roswell has switched its clisp-head to be built from https://github.com/roswell/clisp/ which is based on the commits from CLISP's canonical repository along with patches which add package-local nicknames to it.
-
roswell (21.10.14.111-1): clisp-head support
Oh dang, there is new development on clisp! I had to do some digging to find [the repo](https://gitlab.com/gnu-clisp/clisp), but it looks like the latest commit even adds support for MacOS on ARM.
- Package local nicknames: don't use with quicklisp-targeted packages?
-
SICL: A New Common Lisp Implementation
> phoe got package local nicknames into all implementations
Unfortunately it's not yet in Clisp. I submitted a merge request[1] a year ago, but it's been silent since then.
[1]: https://gitlab.com/gnu-clisp/clisp/-/merge_requests/3
-
Common lisp or Racket as a first lisp?
Quick note, CLISP is actually an implementation of Common Lisp, and as such isn't used as an abbreviation for Common Lisp the language. Could you expand on what you mean w.r.t to package managers? As far as getting up and running with a CL environment, Portacle makes this pretty easy now.
quicklisp-client
-
Steel Bank Common Lisp
Yes, that's clear.
I'm not very familiar with how quicklisp works. I thought that “updates once a month” implies a separate update channel (distribution, ...).
Looking at the relevant issue, https://github.com/quicklisp/quicklisp-client/issues/167 , it's not clear that even hashes are in place.
I recently found out that most Nix fetchers use https, but do not actually do verification (`curl --insecure` or equivalent libcurl settings). Channel updates do verify and include hashes, so the overall chain is authenticated.
-
quicklisp security (or total lack of it)
The latest comment I see about this here from Oct. 2022 says they're working on it. There's also comment by the developer in 2016 saying want to improve the security soon, so it doesn't really seem this will actually happen soon. I realise making signature verification work cross platform in pure lisp without external dependencies isn't easy but from latest comment it seems they have that working, in a branch written 4 years ago? The simplest no-code solution is just since quicklisp is published every month or so, on each new update publish a file with sha256 hash of every package contained in quicklisp signed with same developer's pgp key they are already using to sign download of the initial quicklisp.lisp, yes then users if they care about security would have to manually download the file and verify signature every month or so but it's at least some solution that can be done now.
-
Common Lisp Implementations in 2023
> That's what regular devs do, they don't even bother writing articles or commenting on HN :-)
I'll take the bait, and roll up several of my comments into one.
First, the support contract costs from the commercial vendors can make sense. It's one of the most expensive parts of software. We joke about fixing relatives' printers, but its not false. Support costs introduce a counter-balance.
Second, a message to everyone looking into or using QuickLisp, it uses http instead of https: https://github.com/quicklisp/quicklisp-client/issues/167
You can patch your version to fix this. I'd also recommend adding firewall rules to deny in case your patches roll back. And any other mitigation. Or stricter policies, such as not using it, if it makes sense for your organization.
And the AI bots? I hope there aren't people herding them who don't want to, that's how you get unloving brats and a crappy world.
-
Securing Quicklisp through mitmproxy
I found this github issue about it, open since 2018: https://github.com/quicklisp/quicklisp-client/issues/167
-
Why do people use Quicklisp although it is known to be vulnerable to man-in-the-middle attacks?
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
What are some alternatives?
deprecated-coalton-prototype - Coalton is (supposed to be) a dialect of ML embedded in Common Lisp.
CIEL - CIEL Is an Extended Lisp. Scripting with batteries included.
trivial-cltl2 - Portable CLtL2
quicklisp-https
trivial-package-local-nicknames - Common Lisp PLN compatibility library.
BDFProxy - Patch Binaries via MITM: BackdoorFactory + mitmProxy.
ql-https - HTTPS support for Quicklisp via curl
ocicl - An OCI-based ASDF system distribution and management tool for Common Lisp
screenshotbot-oss - A Screenshot Testing service to tie with your existing Android, iOS and Web screenshot tests
cerberus - Common Lisp Kerberos v5 implementation
aserve - AllegroServe, a web server written in Common Lisp
mitm6 - pwning IPv4 via IPv6