Fossil

Check-in [ac2c2c77]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Updated the paragraph on SHA1 hashes in www/concepts.wiki to also talk about SHA3-256.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: ac2c2c77ff10f9cb1d0a43ebd5a8dccbcd898d1fb87401f9a020c62c443d81ee
User & Date: wyoung 2019-01-06 04:10:04.878
Context
2019-01-06
04:27
Updated the hash policy document, mainly to put it in past tense and to cover the current situation. ... (check-in: df8baf94 user: wyoung tags: trunk)
04:10
Updated the paragraph on SHA1 hashes in www/concepts.wiki to also talk about SHA3-256. ... (check-in: ac2c2c77 user: wyoung tags: trunk)
2019-01-05
01:29
Increase the version number to 2.8 and update the change log, in case we decide to do a new release soon. ... (check-in: f143b606 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to www/concepts.wiki.
︙︙
80
81
82
83
84
85
86
87
88
89

90


91
92
93

94
95
96
97
98
99
100
101
102
103

Communication between repositories is via HTTP.  Remote
repositories are identified by URL.  You can also point a web browser
at a repository and get human-readable status, history, and tracking
information about the project.

<h3>2.1 Identification Of Artifacts</h3>

A particular version of a particular file is called an "artifact".
Each artifact has a universally unique name which is the
<a href="http://en.wikipedia.org/wiki/SHA1">SHA1</a> hash of the content

of that file expressed as 40 characters of lower-case hexadecimal.  Such


a hash is referred to as the Artifact Identifier or Artifact ID
for the artifact.  The SHA1 algorithm is created with the purpose of
providing a highly forgery-resistant identifier for a file.  Given any

file it is simple to find the artifact ID for that file.  But given a
artifact ID it is computationally intractable to generate a file that will
have that Artifact ID.

Artifact IDs look something like this:

<blockquote><b>
6089f0b563a9db0a6d90682fe47fd7161ff867c8<br>
59712614a1b3ccfd84078a37fa5b606e28434326<br>
19dbf73078be9779edd6a0156195e610f81c94f9<br>








|
|
|
>
|
>
>
|
<
|
>
|
|
|








80
81
82
83
84
85
86
87
88
89
90
91
92
93
94

95
96
97
98
99
100
101
102
103
104
105
106

Communication between repositories is via HTTP.  Remote
repositories are identified by URL.  You can also point a web browser
at a repository and get human-readable status, history, and tracking
information about the project.

<h3>2.1 Identification Of Artifacts</h3>

A particular version of a particular file is called an "artifact".  Each
artifact has a universally unique name which is the <a
href="http://en.wikipedia.org/wiki/SHA1">SHA1</a> or <a
href="http://en.wikipedia.org/wiki/SHA3">SHA3-256</a> hash of the
content of that file expressed as either 40 or 64 characters of
lower-case hexadecimal. (See the [./hashpolicy.wiki|hash policy
document] for information on which algorithm is used, when.) Such a hash
is referred to as the Artifact ID. These hash algorithms were created

with Fossil's purpose in mind: to provide a highly forgery-resistant
identifier for a blob of data, such as a file. Given any file, it is
simple to find the artifact ID for that file. But given an artifact ID,
it is computationally intractable to generate a file that will have that
same artifact ID.

Artifact IDs look something like this:

<blockquote><b>
6089f0b563a9db0a6d90682fe47fd7161ff867c8<br>
59712614a1b3ccfd84078a37fa5b606e28434326<br>
19dbf73078be9779edd6a0156195e610f81c94f9<br>
︙︙