This bug was fixed in the package wsl-pro-service - 0.1.4

---------------
wsl-pro-service (0.1.4) noble; urgency=medium

  * Vendor manually on the host as the go mod vendoring when using
    dpkg-buildpackage works in a different environment.

wsl-pro-service (0.1.3) noble; urgency=medium

  * Pin Go toolchain to 1.22.2 to fix the following security vulnerabilities:
    - GO-2024-2687
  * Use self-signed certificate chain to communicate with the Windows Agent 
over mTLS. (LP: #2060548)
  * Simplify the communication with the agent removing the double server.
  * Send the READY signal to systemd earlier.
  * Renamed ubuntu-advantage-tools to ubuntu-pro-client (LP: #2057651)
  * Restrict landscape.conf file permissions. (thanks iosifache)
  * Adds a default 'wsl' tag to Landscape configs.
  * Removed and obfuscated log messages that could leak sensitive information.
  * More robust handling output of cmd.exe commands.
  * More careful validation of the .address file contents.
  * Updated dependencies.

 -- Didier Roche-Tolomelli <didro...@ubuntu.com>  Fri, 19 Apr 2024
07:56:41 +0200

** Changed in: wsl-pro-service (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2060548

Title:
  [FFe] Update and seed wsl-pro-service in the WSL images

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in wsl-pro-service package in Ubuntu:
  Fix Released

Bug description:
  This is a new package for this release. It’s only functional with a
  Windows agent which is not publically released and under beta for now.

  As the end of the beta will be after the 24.04 release, we want to get
  as close as possible to the current code level, knowing that current
  code will still certainly grow feature-wise once with the Beta user
  feedback.

  However, having it seeded (the MIR is approved and security issues
  fixed but the certificate one, which has been discussed as minor for
  now) with the current code level will be great to diminish the diff
  when the SRU that will be needed then.

  The impact is on existing non beta users (and beta users are using a
  ppa with the ppa containing the current code level).

  Current diff is large as the development is very active and won’t
  really provide anything more. Note that it contains also a packaging
  change to fix bug #2057651.

  It also fixes a vulnerability by depending on latest Go and latest
  x/net/http.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2060548/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to