quicklisp-client
cl-community-spec
quicklisp-client | cl-community-spec | |
---|---|---|
6 | 6 | |
286 | 75 | |
- | - | |
0.0 | 8.8 | |
14 days ago | 4 months ago | |
Common Lisp | HTML | |
MIT License | 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.
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
cl-community-spec
-
Help with CLHS license
A possible approach could be to load the GCL info files from here: https://github.com/fonol/cl-community-spec/tree/main/info
-
Is there a version of Hyperspec with better user experience?
This is our best bet, I think. We should all contribute and make it better: https://github.com/fonol/cl-community-spec
- Common Lisp Implementations in 2023
-
HyperSpec rendition produced from ANSI spec draft
A very crude first version can be found at https://cl-community-spec.github.io/pages/index.html. I called it community-spec, because ideally, after I have the generated HTML on an okay-ish level (which will still take some time probably), corrections to the output could be made by anyone who finds an error. The repository can be found here: https://github.com/fonol/cl-community-spec
-
Legal question on using the HyperSpec
Someone already pointed me to them on GitHub: https://github.com/fonol/cl-community-spec/issues/2 The new version that is online now is actually made from the sources already.
What are some alternatives?
CIEL - CIEL Is an Extended Lisp. Scripting with batteries included.
ql-https - HTTPS support for Quicklisp via curl
quicklisp-https
parrot - A cross-platform Common Lisp editor
BDFProxy - Patch Binaries via MITM: BackdoorFactory + mitmProxy.
ready-lisp - A distribution of Aquamacs, SBCL and SLIME which offers the simplest way to run Common Lisp on Mac OS X
ocicl - An OCI-based ASDF system distribution and management tool for Common Lisp
cerberus - Common Lisp Kerberos v5 implementation
aserve - AllegroServe, a web server written in Common Lisp
mitm6 - pwning IPv4 via IPv6
defstar - Type declarations for defun et all. Just a mirror. Ask for push acess!
npt - ANSI Common Lisp implementation