Debarshi Ray 5c59f1b2a8 dir: Use SHA256, not SHA1, to name the cache for a filtered remote
SHA1 hashes are considered weak these days. Some distributions have
static analysis tools to detect the use of such weak hashes, and they
get triggered by flatpak. While this particular use of SHA1 in flatpak
is likely not security sensitive, it's also easy to move to SHA256 to
avoid any debate.

Here, the SHA1 hash of a named remote's filter file is used to generate
the name of the directory where the refs from that remote are cached.
One can reasonably assume that the cache is frequently invalidated
because the list of refs on the remote changes all the time. Hence,
it's not big problem if it gets invalidated once more because of this
change.
2022-02-08 17:56:34 +00:00
2019-04-08 12:50:42 +00:00
2022-01-22 07:39:00 -06:00
2021-08-23 12:19:03 +02:00
2022-02-05 09:10:43 -08:00
2021-05-25 11:11:03 +02:00
2021-11-15 10:44:55 +01:00
2021-10-25 23:32:00 +01:00
2021-03-10 10:33:51 +01:00
2018-02-05 15:21:40 +00:00
2022-01-18 17:34:01 +00:00
2015-03-31 15:36:29 +01:00
2016-06-02 18:05:22 -04:00
2022-01-18 17:34:01 +00:00
2021-12-03 18:16:02 +01:00

Flatpak icon

Flatpak is a system for building, distributing, and running sandboxed desktop applications on Linux.

See https://flatpak.org/ for more information.

Community discussion happens in #flatpak:matrix.org, on the mailing list, and on the Flathub Discourse.

Read documentation for Flatpak here.

Contributing

Flatpak welcomes contributions from anyone! Here are some ways you can help:

Hacking

See CONTRIBUTING.md

Related Projects

Here are some notable projects in the Flatpak ecosystem:

  • Flatseal: An app for managing permissions of Flatpak apps without using the CLI
  • Flat-manager: A tool for managing Flatpak repositories
Description
No description provided
Readme 60 MiB
Languages
C 91.1%
Shell 5.1%
Python 1.8%
Meson 1.1%
Yacc 0.8%