Dear all,

I am currently working hard on getting the developers documentation
on the Wiki into good shape. As part of this, I have moved the
page with SFTP login instructions from the Users Corner into
Development, where we have a whole new section on how to use the
SF.net services.

On this occasion, may I remind everyone that any information posted
on the Wiki is publicly visible. There are probably a gazillion
crackers out there just waiting to get their hands on a valid SF.net
account to use our project as a spam machine. So please:

1. Do not post any critical information, such as valid account names
and passwords on the Wiki (or any of other web sites). This includes
screenshots, where such information is visible or text files that
may contain such information.

2. Do not use trivial passwords for your SF.net accounts. First and
foremost, do not use the same password as your user name. Avoid stuff
that any cracker will guess:

http://www.whatsmypass.com/the-top-500-worst-passwords-of-all-time

Remember: since the valid accounts' user names are publicly visible
on SF.net, crackers only need to guess the second token, which is
the password.

I don't want to be paranoid, but I much less want to lose our
hard work to some 16 year old script kiddies who think they are
cool...

Best,

Ben


------
Files attached to this email may be in ISO 26300 format (OASIS Open Document 
Format). If you have difficulty opening them, please visit http://iso26300.info 
for more information.


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Gvsigce-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gvsigce-community

Reply via email to