●● IRC: #techbytes @ Techrights IRC Network: Sunday, December 14, 2025 ●● ● Dec 14 [05:39] schestowitz[TR2]
  • [05:39] schestowitz[TR2]
    NetworkManager 1.54.3 Improves Certificate Access Checks
    [05:39] schestowitz[TR2]
    [05:39] schestowitz[TR2]

    This additional check prevents situations where a connection profile references credentials that the intended user cannot read, reducing the risk of misconfigurations and unexpected connection failures, especially in multi-user or enterprise setups.

    [05:39] schestowitz[TR2]
    [05:39] schestowitz[TR2]
  • [05:39] schestowitz[TR2] [05:39] -TechBytesBot/#techbytes-linuxiac.com | NetworkManager 1.54.3 Improves Certificate Access Checks [05:49] schestowitz[TR2]
  • [05:49] schestowitz[TR2]
    Rethinking sudo with object capabilities
    [05:49] schestowitz[TR2]
    [05:49] schestowitz[TR2]

    Systems built around identity-based access control tend to rely on ambient authority: policy is centralized and errors in the policy configuration or bugs in the policy engine can allow attackers to make full use of that ambient authority. In the case of a SUID binary like doas or sudo, that means an attacker can obtain root access in the event of a bug or misconfiguration.

    [05:49] schestowitz[TR2]

    What if there was a better way? Instead of thinking about privilege escalation as becoming root for a moment, what if it meant being handed a narrowly scoped capability, one with just enough authority to perform a specific action and nothing more? Enter the object-capability model.

    [05:49] schestowitz[TR2]
    [05:49] schestowitz[TR2]
  • [05:49] -TechBytesBot/#techbytes-ariadne.space | Rethinking sudo with object capabilities Ariadne's Space ● Dec 14 [09:00] *psydroid3 (~psydroid@36imbvshpgubk.irc) has joined #techbytes [09:37] *x-amarsh04 has quit (Quit: Konversation terminated!) [09:45] *x-amarsh04 (~amarsh04@atu2uhbvxaeyw.irc) has joined #techbytes ● Dec 14 [15:04] *psydroid3 has quit (Quit: KVIrc 5.2.6 Quasar http://www.kvirc.net/) [15:18] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [15:26] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes ● Dec 14 [17:45] *psydroid3 (~psydroid@yu29f4abyrsnc.irc) has joined #techbytes ● Dec 14 [18:37] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes ● Dec 14 [19:01] *croissant has quit (Quit: Leaving) [19:14] *croissant (~croissant@3mqmbt748svnk.irc) has joined #techbytes ● Dec 14 [21:17] *psydroid3 has quit (Quit: KVIrc 5.2.6 Quasar http://www.kvirc.net/) ● Dec 14 [22:51] schestowitz[TR2]
  • I tried Pop!_OS for a week: Here's what worked for me and what didnt
    [22:51] schestowitz[TR2]
    [22:51] schestowitz[TR2]

    When I decided to try a different Linux distro, I did what most people would do: I typed the best Linux distros for beginners into my search bar. The AI overview and top ten organic search results recommended Ubuntu LTS, Linux Mint, Zorin OS, Pop!_OS, Elementary OS, and a few other Linux distros. I ran with Pop!_OS because it promised a fast, organized, intuitive, and modern UI, customizations, security, and hardware compa [22:51] schestowitz[TR2] tibility. [22:51] schestowitz[TR2]

    My first impression of Pop!_OS as someone whos never used it
    [22:51] schestowitz[TR2] The Pop!_OS UI felt polished, modern, user-friendly, and not too different from the Ubuntu, which I'd been using for a while. The installation and setup process was seamless, and since the first-run and onboarding experiences were also guided, the entire process was beginner-friendly, and I was up and running in no time. [22:51] schestowitz[TR2]

    [22:51] schestowitz[TR2]
  • [22:51] -TechBytesBot/#techbytes-www.howtogeek.com | I tried Pop!_OS for a week: Here's what worked for me and what didnt