mirror of
https://github.com/opensim/opensim.git
synced 2026-05-15 03:15:41 +08:00
441449e240
Some successful collision attacks have been carried out on sha1 with speculation that more are possible. http://en.wikipedia.org/wiki/Cryptographic_hash_function#Cryptographic_hash_algorithms No successful attacks have been shown on sha256, which makes it less likely that anybody will be able to engineer an asset hash collision in the future. Tradeoff is more storage required for hashes, and more cpu to hash, though this is neglible compared to db operations and network access.
27 lines
692 B
Plaintext
27 lines
692 B
Plaintext
# -----------------
|
|
:VERSION 1
|
|
|
|
BEGIN;
|
|
|
|
CREATE TABLE `xassetsmeta` (
|
|
`id` char(36) NOT NULL,
|
|
`hash` binary(32) NOT NULL,
|
|
`name` varchar(64) NOT NULL,
|
|
`description` varchar(64) NOT NULL,
|
|
`asset_type` tinyint(4) NOT NULL,
|
|
`local` tinyint(1) NOT NULL,
|
|
`temporary` tinyint(1) NOT NULL,
|
|
`create_time` int(11) NOT NULL,
|
|
`access_time` int(11) NOT NULL,
|
|
`asset_flags` int(11) NOT NULL,
|
|
`creator_id` varchar(128) NOT NULL,
|
|
PRIMARY KEY (`id`)
|
|
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Version 1';
|
|
|
|
CREATE TABLE `xassetsdata` (
|
|
`hash` binary(32) NOT NULL,
|
|
`data` longblob NOT NULL,
|
|
PRIMARY KEY (`hash`)
|
|
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Version 1';
|
|
|
|
COMMIT; |