Apparemment une des choses à faire pour sécuriser mon blog est de restreindre les acces
Pour cela il faut créer des fichiers .htacces
Si je comprends bien, je dois creer un fichier .htacces et copier coller le texte ci desous, le seulhic , c'est que les fichiers .htaccess sont invisible sur mon mac (10.4) et que je ne sais plus comment les rendre visible.
Pour créer un ficher sécurisé, il est mieux d'utiliser textedit ou dreamweaver?

Step 1 - Restricting wp-content and wp-includes

Using htaccess <files> directive, we can restrict all files accept images, CSS and JavaScript. The .htaccess file will look as follows:

Order Allow,Deny
Deny from all
<Files ~ "\.(css|jpe?g|png|gif|js)$">
Allow from all
</Files>

If we want to allow certain plugins such as Democracy, we can append the following to our wp-content/.htaccess file:

<Files "democracy.php">
Allow from all
</Files>

Put this into your .htaccess file within your wp-content and wp-includes directories. As a side note, you can also allow specific files to get your plugins and/or templates to work, if needs be. This is a much cleaner method to do it then discussed in a previous version of this document.

If you got through that, well done.
Step 2 - Restricting access to wp-admin

Now to restrict wp-admin you have two choices. Put a .htaccess file into your wp-admin directory with one of the two choices below.

You can resrict it by IP:

order deny,allow
allow from a.b.c.d # This is your static IP
deny from all

The above code will prevent browser access to any file in these directories other than "a.b.c.d" which you should change to be your static IP address.

OR restrict the directory with a password:

AuthUserFile /etc/httpd/htpasswd
AuthType Basic
AuthName "restricted"
Order Deny,Allow
Deny from all
Require valid-user
Satisfy any

OR improved version:

There is a bug where the above rules will cause a password box to appear to the user if they submit a comment without an e-mail address. This occurs, because some CSS and image files are located inside the wp-admin directory. To get around this we can wrap the above rule set in a file directive which disallows .PHP files but permits the rest. This still prevents alot of direct attacks and also provides alot of additional features.

<Files ~ "\.(php)$">
AuthUserFile /etc/httpd/htpasswd
AuthType Basic
AuthName "restricted"
Order Deny,Allow
Deny from all
Require valid-user
Satisfy any
</Files>

Regarde le fichier wp-config-sample.php et recopie dans ton wp-config.php les lignes concernant la clé secrète.
Pour le point Directory Browsing, comme tu ne pourras pas modifier la configuration Apache d'OVH, je ne sais pas si c'est possible, je ne suis pas spécialiste.

Oui ! c'est ça.
Attention à ne pas glisser par mégarde d'apostrophe dans ta phrase secrète.

define('SECRET_KEY', 'j'aime wordpress');  => KO
define('SECRET_KEY', 'j\'aime wordpress');  => OK