• 17 Posts
  • 1.46K Comments
Joined 1 year ago
cake
Cake day: June 16th, 2023

help-circle
  • Just be aware of the risks involved with running your own CA.

    You’re adding a root certificate to your systems that will effectively accept any certificate issued with your CA’s key. If your PK gets stolen somehow and you don’t notice it, someone might be issuing certificates that are valid for those machines. Also real CA’s also have ways to revoke certificates that are checked by browsers (OCSP and CRLs), they may employ other techniques such as cross signing and chains of trust. All those make it so a compromised certificate is revoked and not trusted by anyone after the fact.

    For what’s worth, LetsEncrypt with DNS-01 challenge is way easier to deploy and maintain in your internal hosts than adding a CA and dealing with all the devices that might not like custom CAs. Also more secure.



  • Yes, LetsEncrypt with DNS-01 challenge is the easiest way to go. Be it a single wildcard for all hosts or not.

    Running a CA is cool however, just be aware of the risks involved with running your own CA.

    You’re adding a root certificate to your systems that will effectively accept any certificate issued with your CA’s key. If your PK gets stolen somehow and you don’t notice it, someone might be issuing certificates that are valid for those machines. Also real CA’s also have ways to revoke certificates that are checked by browsers (OCSP and CRLs), they may employ other techniques such as cross signing and chains of trust. All those make it so a compromised certificate is revoked and not trusted by anyone after the fact.












  • If you want a git “server” quick and low maintenance then gitolite is most likely the best choice. https://gitolite.com/gitolite/index.html

    It simply acts as a server that you can clone with any git client and the coolest part is that you use git commits to create repositories and manage users as well. Very very or no maintenance at all. I’ve been using it personally for years but also saw it being used at some large companies because it simply gets the job done and doesn’t bother anyone.


  • So I want to get back into self hosting, but every time I have stopped is because I have lack of documentation to fix things that break. So I pose a question, how do you all go about keeping your setup documented? What programs do you use?

    Joplin or Obsidian? Or… plain markdown files with your favorite text editor.




  • TCB13@lemmy.worldtoPrivacy@lemmy.mlRCS vs SMS/MMS?
    link
    fedilink
    English
    arrow-up
    14
    ·
    7 days ago

    Here’s the problem, RCS isn’t a truly open thing and Google kind of maintains a lot of the software that even carriers use for it. It essentially opens the door for the tech companies to take over yet another big chunk of the carrier services and tap into more user’s data at the network level.

    In June 2019, Google announced that it would begin to deploy RCS on an opt-in basis via the Messages app, with service compliant with the Universal Profile and hosted by Google rather than the user’s carrier, if the carrier does not provide RCS

    In October 2019, the four major U.S. carriers announced an agreement to form the Cross-Carrier Messaging Initiative (CCMI) to jointly implement RCS using a newly developed app. This service was to be compatible with the Universal Profile.[33] However, this carrier-made app never came to fruition. By 2021, both T-Mobile and AT&T signed deals with Google to adopt Google’s Messages app.[34][35][36] In 2023, T-Mobile and AT&T agreed to use Google Jibe to implement RCS services, and in 2024 Verizon agreed to use Google Jibe.

    Apple stated it will not support Google’s end-to-end encryption extension over RCS, but would work with GSMA to create an RCS encryption standard.