changelog
-
+
version 132
+ - merged two complicated serverside account tables into two simpler tables +
- with this action, was able to clean out a lot of rubbish old server account code +
- made it so accounts can only be on one service. existing (admin) accounts that straddled sevices will have new access keys printed in a text file in the base installation directory on server update +
- rewrote the account object to be simpler and easier to maintain +
- swapped the old rubbish 'account_id' identifier in the account object for the much better 'account_key' identifier +
- harmonised some conflicting account-related variable names +
- refined the way the unknown account is stored and identified +
- split serverside account verification and identification into two separate paths, to reduce chance of security problems +
- reworked account identifiers (a general purpose account identifying object that is used in admin-server interactions) and their associated db functions to be more secure and reliable +
- simplified account data use checking +
- simplified and harmonised the way used bytes and used requests are stored and retrieved in the account and account type +
- with guarantee of account_key uniqueness across entire server, I have simplified session code in several places +
- updated help to reflect the new relationship between access keys and account keys +
- added 'copy account key' button to review services, which will now be the thing for users to use if they need an admin to modify their account +
- fixed serverside credential verification for non-instantiated (still have a registration key) access keys +
- added a bit of explaining text to the 'waiting' autocomplete state +
- fixed a typo when deleting files from a file repo +
version 131
- removed tag service precedence and its various expensive and overly complicated effects diff --git a/help/faq.html b/help/faq.html index b2a3d883..d285fffd 100755 --- a/help/faq.html +++ b/help/faq.html @@ -35,12 +35,14 @@
-
+
Hashes are a subject one usually has to be a software engineer to find interesting. If you don't care to digest the wiki page, the simple answer is that hashes are unique names for things. It can be proven that f099b5823f4e36a4bd6562812582f60e49e818cf445902b504b5533c6a5dad94 refers to one particular file and no other. Hashes make excellent—if ugly—identifiers. In the client's normal operation, you will never encounter a file's hash; if you want to see a thumbnail bigger, double-click it; the software handles the mathematics.
For those who are interested: hydrus uses SHA-256, which spits out 32-byte (256-bit) hashes. The software stores the hash densely, as 32 bytes, only encoding it to 64 hex characters when the user views it or copies to clipboard. SHA-256 is not perfect, but it is a great compromise candidate; it is secure for now, it is reasonably fast, it is available for most programming languages, and newer CPUs perform it more efficiently all the time.
hold up, what is an access key?
-The hydrus network's repositories do not use username/password, but instead a single combination identifier-password like this:
+The hydrus network's repositories do not use username/password, but instead a single strong identifier-password like this:
7ce4dbf18f7af8b420ee942bae42030aab344e91dc0e839260fcd71a4c9879e3
These hex numbers give you access to a particular account on a particular repository, and are often combined like so:
7ce4dbf18f7af8b420ee942bae42030aab344e91dc0e839260fcd71a4c9879e3@hostname.com:45871
They are long enough to be impossible to guess, and also randomly generated, so they reveal nothing personally identifying about you. Many people can use the same access key (and hence the same account) on a repository without consequence, although they will have to share bandwidth limits, and if one person screws around and gets the account banned, everyone will lose access.
-The access key is the account.
+The access key is the account. Do not give it to anyone you do not want to have access to the account. An administrator will never need it; instead they will want your account key.
+hold up, what is an account key?
+This is another long string of random hexadecimal that identifies your account without giving away any information about you. If you need to identify yourself to a repository administrator (say, to get your account's permissions modified), you will need to tell them your account key. You can copy it to your clipboard in services->review services.
why aren't my swfs showing?
If an Internet Explorer "Navigation Cancelled" page appears whenever you click on a swf thumbnail, try installing Flash Player for Internet Explorer. Just having it installed for Firefox/Opera is not enough; you need the ActiveX component that comes with the specific IE version. Just boot IE and download/run the installer from Adobe's site.
why can my friend not see what I just uploaded?
diff --git a/help/glossary.html b/help/glossary.html index dcf3a9b9..d613662d 100755 --- a/help/glossary.html +++ b/help/glossary.html @@ -6,23 +6,24 @@access key A 32-byte identifier-password that gives you certain permissions with a repository. Usually represented as a 64-character hex string like so: 7ce4dbf18f7af8b420ee942bae42030aab344e91dc0e839260fcd71a4c9879e3
+access key A 32-byte identifier-password that gives you access to an account that has certain permissions with a repository. Usually represented as a 64-character hex string like so: 7ce4dbf18f7af8b420ee942bae42030aab344e91dc0e839260fcd71a4c9879e3
+account key A 32-byte identifier for a hydrus service account. Usually represented as a 64-character hex string like so: 0c3b554cb6fe7d55c945df88b2f6cf6ca0ae40824bca7534aa2fd483da7fb219
address The pairing of both a server's host (be that an IP or a domain) with its port number, like so: 74.125.225.18:80, or google.com:80
archive The store of files you have chosen to keep.
file repository A service in the hydrus network that hosts files.
filtering A method of quickly deleting and archiving files within the client.
-hash A file's unique identifier. The hydrus network uses SHA-256.
+hash A file's unique identifier. The hydrus network uses SHA-256, which generates 32-byte hashes.
hydrus client An application that manages media and connects to services on the hydrus network.
hydrus network A loose collection of clients and servers that attempt to make media management and distribution easier.
-hydrus server An executable that can run any number of hydrus services for any number of clients to plug into. It is controlled entirely by the client.
+hydrus server An executable that can run any number of hydrus services for any number of clients to plug into. It is managed entirely by the client.
inbox A special tag the client gives to newly imported and downloaded files to make them easier to find and review.
mapping The pairing of a particular file with a particular tag.
message depot A service in the hydrus network that stores messages.
metadata Information about a file, but not stored within the file. Filename, size, hash, modified dates, tags and location are all good examples.
petition A request from an uploader for particular content to be removed from a repository.
-registration key A single-use 32-byte password that, when submitted to a repository, gives an access key. It allows moderators to distribute accounts through insecure channels. +
registration key A single-use 32-byte password that, when submitted to a repository, generates an account and an access key. They add a bit of privacy to the account creation process.
tag A short string of text describing a file.
-tag repository The service in the hydrus network that hosts mappings.
+tag repository A service in the hydrus network that hosts mappings.