Security FAQ: Różnice pomiędzy wersjami

Z MoodleDocs
Skocz do:nawigacja, szukaj
(How can I increase privacy in Moodle?)
(amending manage authentication location as per talk page comment)
 
(Nie pokazano 18 wersji utworzonych przez 3 użytkowników)
Linia 1: Linia 1:
==How can I report a security issue?==
{{Security}}
==How do I report a security issue?==


Please "Create a new issue" in the [http://tracker.moodle.org Moodle Tracker] describing the problem (and solution if possible) in detail. Make sure you set the Security Level accurately to make sure that the security team sees it. Bugs classified as a "Serious security issue" will be hidden from the general public until the security team (led by Petr Skoda) is able to resolve it and publish fixes to registered Moodle sites (see below).
Please create a new issue in the [http://tracker.moodle.org Moodle Tracker] describing the problem in detail. (You'll need a tracker account in order to create a new issue.) Set the security level to "Serious security issue", then only the security team and yourself as the reporter will be able to view it.
 
Previously fixed security issues are listed in the [http://moodle.org/security/ Moodle.org Security news]. If you are unsure whether a problem has been fixed or not, it's best to report it anyway.


==How can I keep my site secure?==
==How can I keep my site secure?==


* The usual way is to update your whole Moodle to the latest stable release of the version you are using. It is very safe to go from 1.8.1 to 1.8.2+, for example, at any time. [[CVS for Administrators|CVS]] is a very easy way to do this.
It's good practice to always use the latest stable release of the version you are using. [[Git for Administrators|Downloading via Git]] is a very easy way to do this.
* Many of the notices will include patch information. If you are fairly confident with editing scripts, then it may be easier for you to just patch the affected file.
 
==How do I keep track of recent security issues?==
 
* [[Site registration | Register your Moodle site with moodle.org]], making sure to enable the option of being notified about security issues and updates. After your registration is accepted, your email address will be automatically added to our low-volume security alerts mailing list.


==How can I keep track of recent security issues?==
* Eventually, all important security issues are published to the general public via the [http://moodle.org/mod/forum/view.php?f=996 Moodle Security forum]. You can subscribe to the [http://moodle.org/rss/file.php/1/1/forum/996/rss.xml forum RSS feed] to automatically add new issues in your favourite feed reader or portal. You can also follow [http://twitter.com/moodlesecurity moodlesecurity on Twitter].


* Register your [http://moodle.org/sites Moodle sites] with moodle.org (visit admin/index.php in your installation to see the registration button), making sure to enable the option of being notified about security issues and updates. After your registration is accepted, your email address will be automatically added to our low-volume securityalerts mailing list.
==Who is able to view security issues in the Tracker?==


* Eventually, all important security issues are published to the general public via the [http://moodle.org/mod/forum/view.php?f=996 Moodle Security forum]. You can subscribe to the [http://moodle.org/rss/file.php/1/1/forum/996/rss.xml forum RSS feed] to automatically add new issues in your favourite feed reader or portal.
Depending upon the security level of a Tracker issue, access is restricted to developers, testers or members of the security team.


==Which versions are supported?==
==Which versions of Moodle are supported?==


* All versions available for download from [http://download.moodle.org/ download.moodle.org] (1.6, 1.7, 1.8 and 1.9) are supported.
Currently supported versions are listed on [http://download.moodle.org/ download.moodle.org].
* The latest development branch of Moodle is not intended for production use and while security problems are fixed, security announcements are not issued. If you are using the development branch for testing or evaluation, we assume that you will update your code regularly.
 
* Our security officer Petr Škoda oversees the security of the code found in the standard Moodle distribution. The security of contributed code lies with the individual maintainers.  
==My site was hacked. What do I do?==
 
See [[Hacked site recovery]].


==How can I reduce spam in Moodle?==
==How can I reduce spam in Moodle?==
Linia 33: Linia 41:


#Obtain a reCAPTCHA key from http://recaptcha.net by [https://admin.recaptcha.net/accounts/signup/?next= signing up for an account] (free) then entering a domain.
#Obtain a reCAPTCHA key from http://recaptcha.net by [https://admin.recaptcha.net/accounts/signup/?next= signing up for an account] (free) then entering a domain.
#Copy and paste the public and private keys provided into the ''recaptchapublickey'' and ''recaptchaprivatekey'' fields in the manage authentication common settings in ''Administration > Users > Authentication > [[Manage authentication]]''.
#Copy and paste the public and private keys provided into the ''recaptchapublickey'' and ''recaptchaprivatekey'' fields in the manage authentication common settings in ''Administration > Plugins > Authentication > [[Manage authentication]]''.
#Click the "Save changes" button at the bottom of the page.
#Click the "Save changes" button at the bottom of the page.
#Follow the settings link for email-based self-registration in ''Administration > Users > Authentication > Manage authentication'' and enable the reCAPTCHA element.
#Follow the settings link for email-based self-registration in ''Administration > Plugins > Authentication > Manage authentication'' and enable the reCAPTCHA element.
#Click the "Save changes" button at the bottom of the page.
#Click the "Save changes" button at the bottom of the page.
==How can I run the security overview report?==
To run the [[Security overview|security overview report]], go to ''Administration > Site administration > Reports > Security overview''.


==See also==
==See also==


*[[Security]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=7301 Security and Privacy forum]


[[Category:FAQ]]
[[Category:FAQ]]
[[Category:Security]]

Aktualna wersja na dzień 06:53, 4 lut 2014

How do I report a security issue?

Please create a new issue in the Moodle Tracker describing the problem in detail. (You'll need a tracker account in order to create a new issue.) Set the security level to "Serious security issue", then only the security team and yourself as the reporter will be able to view it.

Previously fixed security issues are listed in the Moodle.org Security news. If you are unsure whether a problem has been fixed or not, it's best to report it anyway.

How can I keep my site secure?

It's good practice to always use the latest stable release of the version you are using. Downloading via Git is a very easy way to do this.

How do I keep track of recent security issues?

  • Register your Moodle site with moodle.org, making sure to enable the option of being notified about security issues and updates. After your registration is accepted, your email address will be automatically added to our low-volume security alerts mailing list.

Who is able to view security issues in the Tracker?

Depending upon the security level of a Tracker issue, access is restricted to developers, testers or members of the security team.

Which versions of Moodle are supported?

Currently supported versions are listed on download.moodle.org.

My site was hacked. What do I do?

See Hacked site recovery.

How can I reduce spam in Moodle?

See Reducing spam in Moodle.

How can I increase privacy in Moodle?

See Increasing privacy in Moodle.

How do I enable reCAPTCHA?

To add spam protection to the Email-based self-registration new account form with a CAPTCHA element:

  1. Obtain a reCAPTCHA key from http://recaptcha.net by signing up for an account (free) then entering a domain.
  2. Copy and paste the public and private keys provided into the recaptchapublickey and recaptchaprivatekey fields in the manage authentication common settings in Administration > Plugins > Authentication > Manage authentication.
  3. Click the "Save changes" button at the bottom of the page.
  4. Follow the settings link for email-based self-registration in Administration > Plugins > Authentication > Manage authentication and enable the reCAPTCHA element.
  5. Click the "Save changes" button at the bottom of the page.

How can I run the security overview report?

To run the security overview report, go to Administration > Site administration > Reports > Security overview.

See also