Edit History Actions Discussion

Diff for "Info/Security"

Differences between revisions 2 and 5 (spanning 3 versions)
Revision 2 as of 2006-12-20 19:39:56
Size: 1733
Comment:
Revision 5 as of 2007-08-14 21:07:15
Size: 2232
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#acl Known:read Default
Line 4: Line 5:
== Encryption ==
The shell server only accepts encrypted logins. For SSH, only protocol v2 is allowed.

Normal non-encrypted FTP is not supported, instead SFTP from the OpenSSH package is used to transfer files to and from the shell server.

Sensitive webpages such as phpMyAdmin and Webmail is only available over HTTPS. The certificate is a class 3 certificate from CAcert. If you do not have CAcert's root certificate installed in your browser, follow these instructions to get it: http://wiki.cacert.org/wiki/BrowserClients
Line 5: Line 13:
Do not use the same password for your shell account as you use for other services. Especially not services that communicate over non-secure protocols like most connections via IRC. Do not use the same password for your shell account as you use for other services. Especially not services that communicate over non-secure protocols like IRC or webpages.
Line 10: Line 18:
Phising is starting to become a more eminent threat, therefore I've decided to make some policies about how communication with users regarding sensitive information (passwords) should be handled No one at Blinkenshell will ever ask you for your password. Do not ''ever'' give away your password, not even to someone saying he/she is an admin.
Line 12: Line 20:
Firstly, all messages sent by me to users will always start with a ''personal'' greeting. It will say "Hi George" if your name is george, never trust emails from me without this personal greeting. On IRC, there often is no really good way to protect your nickname, so anyone can use anyone else's nickname. Don't trust someone to be an admin just because of the username. Check things like connecting host and if the user is identified with NickServ.
Line 14: Line 22:
Secondly, I will always send an OpenPGP signature with all my emails. If you do not know what OpenPGP is, you can read more about it at Wikipedia: http://en.wikipedia.org/wiki/OpenPGP Email can be sent from addresses other than one's own, so don't trust emails asking you to reply with your password or similar just because the sender address is from a trusted domain.

Use common sense and a certain ammount of paranoia and you will be allright :-)

If you want me to send emails to you encrypted or signed with PGP, that's no problem, just ask.
Line 18: Line 30:
Communication that is not regarding sensitive information like passwords might not be signed. Also, automatically sent information like the email activation step in the signup program does not currently send signed messages.

Lastly, I will never ask you to enter your password for the shell on any form on any website, especially not over a non-secure connection.
Line 23: Line 31:
http://www.dewinter.com/gnupg_howto/english/GPGMiniHowto.html  * Pretty Good Privacy (PGP): http://en.wikipedia.org/wiki/Pretty_Good_Privacy
 * Gnu Privacy Guard (GPG, Gnu PGP-thingy): http://www.dewinter.com/gnupg_howto/english/GPGMiniHowto.html

Security

Here you can find some general information and pointers about security in general and more specifically Blinkenshell.

Encryption

The shell server only accepts encrypted logins. For SSH, only protocol v2 is allowed.

Normal non-encrypted FTP is not supported, instead SFTP from the OpenSSH package is used to transfer files to and from the shell server.

Sensitive webpages such as phpMyAdmin and Webmail is only available over HTTPS. The certificate is a class 3 certificate from CAcert. If you do not have CAcert's root certificate installed in your browser, follow these instructions to get it: http://wiki.cacert.org/wiki/BrowserClients

Passwords

Do not use the same password for your shell account as you use for other services. Especially not services that communicate over non-secure protocols like IRC or webpages.

Also, check out our password policy: PasswordPolicy

Phising and trust

No one at Blinkenshell will ever ask you for your password. Do not ever give away your password, not even to someone saying he/she is an admin.

On IRC, there often is no really good way to protect your nickname, so anyone can use anyone else's nickname. Don't trust someone to be an admin just because of the username. Check things like connecting host and if the user is identified with NickServ.

Email can be sent from addresses other than one's own, so don't trust emails asking you to reply with your password or similar just because the sender address is from a trusted domain.

Use common sense and a certain ammount of paranoia and you will be allright :-)

If you want me to send emails to you encrypted or signed with PGP, that's no problem, just ask.

You can download my OpenPGP public key signature on my personal page: JohanMarcusson. You can not fully trust this however, since you downloaded it over the internet. But I'll make sure that no one else publishes an OpenPGP signature on this website trying to say it's mine.

Read more