Quicklisp client. (by quicklisp)

Quicklisp-client Alternatives

Similar projects and alternatives to quicklisp-client

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better quicklisp-client alternative or higher similarity.

quicklisp-client reviews and mentions

Posts with mentions or reviews of quicklisp-client. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-30.
  • Steel Bank Common Lisp
    9 projects | news.ycombinator.com | 30 Jun 2023
    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)
    6 projects | /r/lisp | 26 Feb 2023
    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
    10 projects | news.ycombinator.com | 23 Feb 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
    2 projects | /r/Common_Lisp | 19 Mar 2022
    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?
    5 projects | /r/lisp | 30 Jan 2021
    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
    5 projects | /r/lisp | 30 Jan 2021
    Relevant bug report: Use HTTPS instead of HTTP
  • A note from our sponsor - SonarQube
    www.sonarqube.org | 30 Sep 2023
    Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free. Learn more →


Basic quicklisp-client repo stats
3 months ago

quicklisp/quicklisp-client is an open source project licensed under MIT License which is an OSI approved license.

The primary programming language of quicklisp-client is Common Lisp.

Collect and Analyze Billions of Data Points in Real Time
Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.