Auto-Update functionality for netbird client #319

Open
opened 2025-11-20 05:09:33 -05:00 by saavagebueno · 9 comments
Owner

Originally created by @giezi on GitHub (May 3, 2023).

Is your feature request related to a problem? Please describe.
Client Updates are currently manual.

Describe the solution you'd like
It would be great if the netbird client had an auto update function. Users who don't want to should be able to disable it and update the client manually with a button in the client settings.

Originally created by @giezi on GitHub (May 3, 2023). **Is your feature request related to a problem? Please describe.** Client Updates are currently manual. **Describe the solution you'd like** It would be great if the netbird client had an auto update function. Users who don't want to should be able to disable it and update the client manually with a button in the client settings.
Author
Owner

@support-tt commented on GitHub (May 3, 2023):

yes this feature would be super nice because if you have like 100 peers the update stuff is very nasty especially on clients with users.

@support-tt commented on GitHub (May 3, 2023): yes this feature would be super nice because if you have like 100 peers the update stuff is very nasty especially on clients with users.
Author
Owner

@lfarkas commented on GitHub (May 8, 2023):

if your os packaging system can do it for you (rpm, deb) from it's repo. android, ios also do it (will do it). what else?

@lfarkas commented on GitHub (May 8, 2023): if your os packaging system can do it for you (rpm, deb) from it's repo. android, ios also do it (will do it). what else?
Author
Owner

@support-tt commented on GitHub (May 8, 2023):

if your os packaging system can do it for you (rpm, deb) from it's repo. android, ios also do it (will do it). what else?

yes for linux thats works but in Windows you have to do it manually.
Another point from my experience client user never click on update if the admin doesnt advise to do it so a "force" update button for the admin would be awesome maybe with a option to force update on the whole linux client (apt upgrade ...)

@support-tt commented on GitHub (May 8, 2023): > if your os packaging system can do it for you (rpm, deb) from it's repo. android, ios also do it (will do it). what else? yes for linux thats works but in Windows you have to do it manually. Another point from my experience client user never click on update if the admin doesnt advise to do it so a "force" update button for the admin would be awesome maybe with a option to force update on the whole linux client (apt upgrade ...)
Author
Owner

@giezi commented on GitHub (May 8, 2023):

if your os packaging system can do it for you (rpm, deb) from it's repo. android, ios also do it (will do it). what else?

MacOS - I don't know if netbird would like to enter the Mac App Store... An auto-update of just the client would also be useful for Linux systems which are used for subnet routing.

@giezi commented on GitHub (May 8, 2023): > if your os packaging system can do it for you (rpm, deb) from it's repo. android, ios also do it (will do it). what else? MacOS - I don't know if netbird would like to enter the Mac App Store... An auto-update of just the client would also be useful for Linux systems which are used for subnet routing.
Author
Owner

@lfarkas commented on GitHub (May 8, 2023):

auto update overwrite some file on the filesystem. in a normal os the filesystem integrity is very critical. which means replacing a file which checksum is calculated at build time is a security nightmare. of i know for windows the security is never been so critical, but from a security software...
may be a beta version can do it, may be some as playground it can be done, but in a real production environment it's never a option...
to show a popup or log a notice it's ok. to automatically do the update it's not.

@lfarkas commented on GitHub (May 8, 2023): auto update overwrite some file on the filesystem. in a normal os the filesystem integrity is very critical. which means replacing a file which checksum is calculated at build time is a security nightmare. of i know for windows the security is never been so critical, but from a security software... may be a beta version can do it, may be some as playground it can be done, but in a real production environment it's never a option... to show a popup or log a notice it's ok. to automatically do the update it's not.
Author
Owner

@giezi commented on GitHub (May 8, 2023):

auto update overwrite some file on the filesystem. in a normal os the filesystem integrity is very critical. which means replacing a file which checksum is calculated at build time is a security nightmare. of i know for windows the security is never been so critical, but from a security software... may be a beta version can do it, may be some as playground it can be done, but in a real production environment it's never a option... to show a popup or log a notice it's ok. to automatically do the update it's not.

Of course, the auto-update functionality should be an optional feature.

@giezi commented on GitHub (May 8, 2023): > auto update overwrite some file on the filesystem. in a normal os the filesystem integrity is very critical. which means replacing a file which checksum is calculated at build time is a security nightmare. of i know for windows the security is never been so critical, but from a security software... may be a beta version can do it, may be some as playground it can be done, but in a real production environment it's never a option... to show a popup or log a notice it's ok. to automatically do the update it's not. Of course, the auto-update functionality should be an optional feature.
Author
Owner

@Rob787 commented on GitHub (Nov 25, 2024):

+1 From our side as well. It is now a nightmare to manage. If at least the Windows client would trigger/ask users to update to new version that would help enormously already.

@Rob787 commented on GitHub (Nov 25, 2024): +1 From our side as well. It is now a nightmare to manage. If at least the Windows client would trigger/ask users to update to new version that would help enormously already.
Author
Owner

@ruairinewman commented on GitHub (Mar 30, 2025):

auto update overwrite some file on the filesystem. in a normal os the filesystem integrity is very critical. which means replacing a file which checksum is calculated at build time is a security nightmare. of i know for windows the security is never been so critical, but from a security software... may be a beta version can do it, may be some as playground it can be done, but in a real production environment it's never a option... to show a popup or log a notice it's ok. to automatically do the update it's not.

From an Enterprise perspective, being able to push upgrades from the management console to a given machine, or group of machines, to a specified version (meaning that we can run a couple of versions behind release if desired, for example), would be a great feature to have.

By groups of machines, I mean being able to allocate upgrades to machines:

  1. in a specific network, or
  2. currently running a specific version or
  3. currently running a version older than a given release, or
  4. machines matching a given tag within Netbird (a basic tagging API would probably be a prerequisite for this - did I miss one? There doesn't seem to be one referred to in the API docs, at a glance.)
@ruairinewman commented on GitHub (Mar 30, 2025): > auto update overwrite some file on the filesystem. in a normal os the filesystem integrity is very critical. which means replacing a file which checksum is calculated at build time is a security nightmare. of i know for windows the security is never been so critical, but from a security software... may be a beta version can do it, may be some as playground it can be done, but in a real production environment it's never a option... to show a popup or log a notice it's ok. to automatically do the update it's not. From an Enterprise perspective, being able to push upgrades from the management console to a given machine, or group of machines, to a specified version (meaning that we can run a couple of versions behind release if desired, for example), would be a great feature to have. By groups of machines, I mean being able to allocate upgrades to machines: 1. in a specific network, or 2. currently running a specific version or 3. currently running a version older than a given release, or 4. machines matching a given tag within Netbird (a basic tagging API would probably be a prerequisite for this - did I miss one? There doesn't seem to be one referred to in the API docs, at a glance.)
Author
Owner

@Dyc9 commented on GitHub (Oct 28, 2025):

Hi,
Is this feature planned for release, or will it not be implemented?
We have over 100 users, and doing manual updates is quite a pain.

@Dyc9 commented on GitHub (Oct 28, 2025): Hi, Is this feature planned for release, or will it not be implemented? We have over 100 users, and doing manual updates is quite a pain.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#319