Commit Graph

8 Commits

Author SHA1 Message Date
Peter Müller
90f03efea5 Core Update 166: Introduce new 2022 Pakfire key
Cc: Michael Tremer <michael.tremer@ipfire.org>
Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
2022-03-22 17:34:30 +00:00
Peter Müller
219a998412 Core Update 166: Drop old 2007 Pakfire key, and remove it from existing installations
It is not necessary to have this key present on IPFire systems anymore,
since it has not been in use for years, and we can expect systems to be
sufficiently up-to-date, so they no longer need to rely on old updates
or add-ons signed with this key.

Also, given the current key was generated in 2018, we should consider a
Pakfire key rollover soon.

Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
Acked-by: Michael Tremer <michael.tremer@ipfire.org>
2022-03-21 11:46:36 +00:00
Michael Tremer
74e715a5a2 pakfire: Import old key, too
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
2018-04-02 15:46:40 +01:00
Michael Tremer
397d3a8e15 pakfire: Rename new key to pakfire-2018.key
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
2018-04-02 15:46:40 +01:00
Michael Tremer
5e5c2e5413 Import new Pakfire Signing Key
We will swap the key that we use to sign Pakfire packages
since the current one is considered outdated cryptography.

Fixes: #11539

Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
2018-03-16 14:26:07 +00:00
Michael Tremer
065c9931ac Write /opt/pakfire/db/core/mine in stage2. 2013-09-30 21:08:44 +02:00
Arne Fitzenreiter
7f7a741d0f rootfile updates: pakfire, crda, stage2. 2011-10-04 19:29:01 +02:00
Michael Tremer
fa2bdba6f3 Rootfile update. 2011-09-17 20:11:28 +02:00