Hello everyone, We built clubsall, a frontend for federated content. Since the goal is to help build a reddit competitor, open sourcing is the logical next step.

However, without a review, I am afraid website could get hacked quickly.

Does someone with experience in scanning code for security issues or white hat hacking wants to help increase confidence so I can open source it?

  • SorteKaninAEnglish
    25·
    2 months ago

    Obscurity is not security, so you could argue that you should just open source it anyway. Any security holes present are also there right now - the fact that the source code is not available is irrelevant.

    But if you insist, it may help if you say what programming language is used.

  • nickwitha_k (he/him)@lemmy.sdf.orgEnglish
    6·
    2 months ago

    As someone who works in software engineering and has experience in multiple languages, infosec, as well as working through compliance with multiple certification standards, I’d be happy to help, provided one of two conditions is met:

    1. You pay me my salary rate, with a minimum of 10 hours, half in advance and report available after receipt of full payment (grew up with tradespeople and a lot about working with clients comes from what I learned from them).

    Or,

    1. The code base is fully, and permanently open-sourced, prior to code review. This means licensing under GPL, LGPL, MIT, or BSD licenses, or equivalent, not “source available”.
  • vinay_clubsall@lemmy.worldOPEnglish
    5·
    2 months ago

    Update on this request: A developer approached me and is not only helping me with review and fix security issues. We found quite concerning security issues, so I think the decision to have another person look at this was right one.

    We discussed and found that we need to do following work

    1. Redo backend/api so it is more robust, while doing that it will also become Lemmy API compatible
    2. Fix client so it adapt to any API changes
    3. Move from cloudflare workers to docker, so it can be self hosted
    4. Move from D1 to postgres (D1 has 10GB limit, ClubsAll db is already 5GB), so it is scalable
    5. Move production to a VM or k8s cluster so we can host our own DB, backend and frontend instead of CF workers

    We have some work to do but will have a good product at the end of it. We will update further once we get this work done. Thanks to everyone to your thoughts and offers to help.