Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb

  • 0 Posts
  • 65 Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle

  • Makes sense… Broadcom really are speedrunning the destruction of the VMware brand, and Proxmox VE and xcp-ng are reaping the benefits.

    Some major changes Broadcom has made to VMware licensing are that they’ve killed off perpetual licenses, and subscriptions are now billed per CPU core rather than per socket. They enforce a 16-core minimum, and were trying to increase that to a 72-core minimum (but rolled that back). Competitors with enterprise support plans, like Proxmox VE, still bill per socket.

    That and all the features in Proxmox VE are free (both in cost and in free software). A company has to pay a license for all their VMware servers, whereas with Proxmox they can decide to only pay for enterprise support for production servers, while using the free version for dev/test/staging environments that don’t need stability or SLAs.


  • legacy tlds (com, net, org) tend to be more affordable

    Verisign are trying their best to make .com and .net less affordable. Their contract with ICANN is on a six year cycle, and it lets them increase the price by up to 7% for the last four years. Two years with no increases, then four years with increases. So far, they’ve always increased it the maximum amount.

    Wholesale price has gone up from $6 in 2000 to $7.85 in 2020 (before this contract structure), to $10.26 now, and they’re increasing it to $10.97 on November 1.

    Having said that, it’s still better than ccTLDs and newTLDs, where the registry can increase it as much as they want.


  • Makes sense! I didn’t realise it has a UI.

    I’ve got a bunch of snippets in /etc/nginx/snippets/, so for example I just need to add include snippets/proxy.conf to a server block to add most of the configuration needed for a reverse proxy. I’ve been using Nginx for long enough that I just write the rest of the server block by hand.




  • dan@upvote.autoSelfhosted@lemmy.world•Anyone using 6-day certs yet?
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    23 days ago

    A private key leaking is bad, since anyone with the private key can decrypt data that was encrypted with it.

    Traditionally, the way that leaked certs were handled was via Certificate Revocation Lists (CRL). CRLs contain lists of revoked certificates - their serial number, revocation date, and the reason why they were revoked.

    However, CRLs are imperfect. Checking for revoked certificates every time you go to a site would slow things down a lot, as the lists are now too large to check and download real-time. Modern browsers and other TLS clients periodically download the lists in the background. Also, it might take a while between when the certificate is compromised and when the company notices the compromise.

    Because of this, the CA/Browser forum (a group with all the major browser and TLS certificate vendors) have started dropping the max lifetime of certificates. The idea is that even if a private key does leak, the time frame that it’s usable for will be significantly shorter and any leaks should (in theory) cause less damage.

    • The original maximum duration was 39 months: Three years plus an extra three months leeway for obtaining and deploying new certificates.
    • March 2018: Reduced to 825 days
    • September 2020: Reduced to 398 days
    • March 2026: Reduced to 200 days
    • March 2027: Planned to reduce to 100 days
    • March 2028: Planned to reduce to 47 days

    All modern deployments, regardless of if they’re using free or paid certs, should have their renewals fully-automated, so in theory the validity period shouldn’t matter as much as it did in the past. All major vendors (Let’s Encrypt, DigiCert, Sectigo, GlobalSign, AWS, SSL .com, etc) support ACME now. Reducing the validity is also a forcing function t o ensure automation is actually implemented.

    somehow else in the middle and just can “ignore” certs renewals?

    I’m not sure that’s possible, since an attacker in the middle shouldn’t be able to obtain a valid certificate for the domain. Certificates have a “not valid after” date encoded into them, after which the certificate is considered invalid and you get an error.


  • dan@upvote.autolinuxmemes@lemmy.world•Linux tips
    link
    fedilink
    arrow-up
    6
    ·
    24 days ago

    The Debian version of Mint. :D

    Most Linux distros have live DVDs that let you try it out without installing it… Try a few of the major distros and see what you like best? You could also install a few and dual-boot (multi-boot I guess?)


  • dan@upvote.autolinuxmemes@lemmy.world•Linux tips
    link
    fedilink
    arrow-up
    10
    ·
    24 days ago

    causing instability and tons of graphical glitches especially in video playback

    Flashbacks to me struggling to get the fglrx drivers working.

    If you never got to experience the “joy” of that… There was a time long ago when getting graphics acceleration working with ATI/AMD GPUs on Linux needed proprietary drivers. It was a struggle, significantly worse than dealing with the Nvidia drivers today. Things improved so much when AMD released and upstreamed their modern open-source driver, around 10 years ago now.




  • COM solved all this stuff over 30 years ago. When you’re making breaking changes to an interface, you create a new one while still keeping the old one around (at least for a while). Both interfaces are shipped with the same DLL. Software written for the old interface continues to work, while newer software can take advantage of the extra features in the new interface.

    You can do something kinda similar in Linux with sonames, like libfoo.so.1, libfoo.so.2, etc. but there’s still a bunch of use cases where you need to use LD_LIBRARY_PATH, and they’re entirely separate libraries vs the COM approach where both interfaces are in a single library.

    Modern software keeps poorly reinventing the same concept. Software like Home Assistant has breaking changes between releases because they don’t have a consistent interface.




  • Makes sense! 30W is great for your system. My home server has an older 10Gbps NIC that uses an Aquantia AQC107 chip, which has poor support for ASPM and prevents the CPU from entering lower C states. I’ve been considering swapping it out for something newer (like an AQC113), I just need to work out whether it’s actually worth it.

    Mine used to cost $0 in electricity since I’ve got solar panels, but we’ve got two EVs now (my wife has a BMW iX and I’ve got an i4) so we’re back to having to pay the electricity company again.


  • Creating a cluster could help me self host more websites I create as I want to move away from using hosting services

    Just jeep an eye on electricity prices. This is probably not an issue with a phone server, but for me, hosting at home with a decent server PC costs more per month just in electricity compared to using a cheap VPS. Continuous draw of 50W 24/7 is ~37kWh per month which can cost $15 or more in California.

    I do still host some things at home, but all my sites are on VPSes. The enterprise hardware and fast, data center grade internet connection is worth it for me. Some of my VPSes are only $40/year.