SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Ubuntu 26.04 switches default sudo to Rust-based sudo-rs, raising compatibility risks

0
·2 views

Ubuntu 26.04 LTS makes sudo-rs, a Rust rewrite, the default sudo implementation instead of the traditional sudo.ws version. Most users will notice no difference, but scripts, Ansible playbooks, custom sudoers files, or CI pipelines relying on less common flags or options could fail silently. sudo-rs deliberately omits some features, including plugin support, LDAP-stored sudoers, and several Defaults such as mail and logging options. Unrecognized directives may either cause parse errors that lock out root access or be ignored, leaving intended policies inactive. The article recommends inventorying all sudo usage, testing on an ubuntu:26.04 container, and rolling out gradually, with update-alternatives offering a temporary fallback.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Is GitHub Actions with ArgoCD or Flux Still the Right Continuous Delivery Stack in 2026?

For years, pairing GitHub Actions with ArgoCD or Flux has been the default choice for continuous delivery, linking build-and-test automation with GitOps-based Kubernetes deployments. The article notes that the rise of microservices and multi-cloud architectures exposes limits in this combination, such as pipeline bottlenecks and weak cross-platform support without extra configuration. It also points to specialized alternatives like Spinnaker, Tekton, and Harness, which offer advanced orchestration, canary analysis, and policy-based deployments. The piece argues that teams should weigh total cost of ownership, tool sprawl, observability, and regulatory needs before choosing their toolset. It presents a decision framework to help teams select the most suitable continuous delivery solution for 2026.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Hex editor gains mirror view for referencing another offset in the same binary

A developer has added a mirror view to a hex editor they are building, letting users select any offset in a binary file to refer to while working. The feature lets a user keep a second location visible alongside the one they are editing. The developer describes it as a capability they had wanted for a long time. The post was published on DEV Community and presents the addition as a personal project update.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Idempotency Keys Are Not HTTP Caching: Lessons From Wiring Payment Replay

A developer explains why idempotency keys for paid API calls should not be treated as simple HTTP caching. The article describes the payment-identifier extension in @x402/extensions 2.30.0, which maps the same ID and same request to a replayed response, a conflicting request to a 409, and an in-flight request to a 503 with Retry-After. The author found that keying on the router template was flawed, since every route shares that string, and that the key must include the concrete path and a hash of the request body, plus the query string for cached GETs. The piece also recommends returning machine-readable retry guidance in the response body, avoiding replay of sensitive headers like CORS and CSP, and explicitly marking replayed responses. Finally, it advises bounding the cache by TTL, body size, and total entries, noting that the in-flight marker is lost on restart and a persisted replay lock is needed.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Crypto store cut to one wallet address and unique payment amounts across six chains

A small digital goods seller initially accepted only BEP20 USDT on BSC, and despite a working payment setup, made zero sales over two weeks. Buyers who had funds on other chains left at the payment screen because they could not pay with the assets they held. The seller rebuilt the checkout around a single wallet address that accepts two stablecoins across six chains. Orders are identified by unique micro-amounts rather than per-chain order numbers, with a watcher scanning all enabled chains for matching transfers. The article also covers pitfalls such as differing token decimals between chains and the need for server-side log filtering to keep RPC usage manageable.

0 comments Read more at DEV Community