linuxmint / linuxmint/mintupdate

Add the option to not be asked for password for later updates

Open
#893 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

FEATURE REQUEST
Dominant language
Python
Stars
425
Forks
190
PR merge metrics
No merged PRs in 30d

Description

At the moment, users have two choices: approve every set of changes as mintupdate notices them and be asked for their password each time OR go for automated updates "on a daily basis" without further approval.

I would like to see the option to have something in the middle: be asked to approve the changes as and when, but - after the first time following a boot - not be asked for the password. each. and. every. time.

This was first asked for about ten years ago and was declined on the basis of 'security'. Since then, the ability to have updates without entering the password again has been added, but only if you're prepared to wait up to 23h59m for them and to accept them whether or not that's convenient at the time.

'Password only once' works as the default for, say, Ubuntu MATE. (I'm not sure if you can even get that one to ask each and every time.)

Please can it be added as an option for mintupdate? Having it turned off by default would be completely fine.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests. Start by locating mintupdate's existing interactive approval and daily automated-update paths; done means adding an optional mode that asks for approval while requesting a password only once after boot, with the option disabled by default.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.