The term "blown" is jargon, I don't think we should use it. All messages should give the user guidance as to what course of action to take, and what the implications of the various messages are.
Ian. On Thu, Jan 31, 2013 at 3:44 PM, Matthew Toseland <[email protected] > wrote: > Some strings that users hopefully will never see. But if they do see them, > they need to be clear. Any comments welcome. > > RevocationKeyFoundUserAlert.text=The Freenet auto-update system appears to > have been compromized! A trusted member of the Freenet team has uploaded a > special signed message to Freenet to say that the keys for the auto-updater > have been stolen, leaked, or somebody has them who shouldn't. We have > turned off auto-update to prevent malware from being installed on your > computer. Please check the website ( https://freenetproject.org/ ) for > updates (if you can do so safely), but be careful as that may not be secure > either. The thief might even have the keys for the message below, so please > don't blindly follow instructions given without confirmation. Sorry we > messed up! > RevocationKeyFoundUserAlert.textDetail=The message is: ${message} > RevocationKeyFoundUserAlert.textDisabled=The auto-updater has been > disabled. This might be because of a local problem, such as running out of > disk space, or the auto-updating system may have been compromized. > RevocationKeyFoundUserAlert.textDisabledDetail=The reason is: ${message}. > RevocationKeyFoundUserAlert.title=URGENT: The Freenet auto-update system > has been compromised! > RevocationKeyFoundUserAlert.titleDisabled=The auto-updater may have been > compromised! We have turned it off for now, please click for more details. > > PeersSayKeyBlownAlert.fetching=Your node is attempting to download the > revocation certificate to find out more details. > PeersSayKeyBlownAlert.failedFetch=Your node has been unable to download > the revocation certificate. Possible causes include an attack on your node > to try to get you to update despite the key being blown, or your nodes > lying about the key being blown. Please contact the developers or other > Freenet users to sort out this mess. > PeersSayKeyBlownAlert.connectedSayBlownLabel=These connected nodes say > that the key has been blown (we are trying to download the revocation cert > from them): > PeersSayKeyBlownAlert.disconnectedSayBlownLabel=These nodes told us that > the key has been blown, but then disconnected, so we could not fetch the > revocation certificate: > PeersSayKeyBlownAlert.failedTransferSayBlownLabel=These nodes told us that > the key has been blown, but then failed to transfer the revocation > certificate: > PeersSayKeyBlownAlert.titleWithCount=Auto-update key blown according to > ${count} peer(s)! > PeersSayKeyBlownAlert.short=According to some of your peers it is not safe > to auto-update. Auto-update has been disabled until we know if they are not > making it up. > > RevocationChecker.revocationFetchFailedMaybeInternalError=The auto-update > system has failed due to an unexpected error: "${detail}". This might be > because the auto-update key has been compromized (e.g. the keys have been > stolen), so we have turned off auto-update as it may not be safe. However > it might also be due to a local problem such as running out of disk space. > If this is true, please fix the problem and restart Freenet. If this > message does not go away, please check the website ( > https://freenetproject.org/ ) and seek help. It might be useful to try > fetching the key manually, but bear in mind it might have been inserted by > the person who stole the keys: ${key} > RevocationChecker.revocationFetchFailedFatally=The auto-update system has > been compromized! The private key may have been stolen, so auto-update has > been turned off permanently. The file that should explain what has happened > cannot be fetched due to an unexpected error: "${detail}". Please try > fetching the key manually (the key might have been inserted incorrectly > e.g. be too big; for safety's sake we have to turn off auto-update straight > away rather than wait for the whole key): ${key} > > _______________________________________________ > Devl mailing list > [email protected] > https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl > -- Ian Clarke Personal blog: http://blog.locut.us/
_______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
