[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file /includes/functions.php on line 4770: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3884)
[phpBB Debug] PHP Warning: in file /includes/functions.php on line 4772: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3884)
[phpBB Debug] PHP Warning: in file /includes/functions.php on line 4773: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3884)
[phpBB Debug] PHP Warning: in file /includes/functions.php on line 4774: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3884)
 Forum eduweb.pl • Wyświetl temat - WP atak brute force
Z uwagi na dużą liczbę wpisów stworzonych bez wątpienia wyłącznie w celu pozycjonowania stron na określone frazy, dodaliśmy do wszystkich linków (w postach i podpisach) atrybut rel="nofollow". Z tego względu wszystkie dodane linki straciły swoją moc pozycjonerską. Forum jest dla Was, dlatego prosimy o zamieszczanie wyłącznie "prawdziwych" tematów i odpowiedzi.

WP atak brute force

Joomla!, Drupal, WordPress i inne...
  • Wiadomości
Offline

Tamten

  • Posty: 265
  • Rejestracja: 5 mar 2010, o 21:48
  • Lokalizacja: Lublin

WP atak brute force

Post30 cze 2015, o 14:46

Witam wiele się o tym pisze i sam doświadczyłem tematu, więc pytam czy ktoś zna skuteczną metodę oby zapobiec tego typu atakom zanim serwer klęknie :)
Dzięki.
Offline

Tamten

  • Posty: 265
  • Rejestracja: 5 mar 2010, o 21:48
  • Lokalizacja: Lublin

Re: WP atak brute force

Post30 cze 2015, o 16:24

Póki co dodałem dodatkowe uwierzytelnianie w pliku .htaccess - ale czy to skutecznie zmniejszy obciażenie serwera ?
Offline
Awatar użytkownika

Piotr Palarz

Ekspert

Ekspert

  • Posty: 685
  • Rejestracja: 24 kwie 2012, o 00:37

Re: WP atak brute force

Post30 cze 2015, o 21:14

Nie testowałem, ale wygląda naprawdę ciekawie: https://wordpress.org/plugins/bruteprotect/
Offline

Tamten

  • Posty: 265
  • Rejestracja: 5 mar 2010, o 21:48
  • Lokalizacja: Lublin

Re: WP atak brute force

Post1 lip 2015, o 10:13

Faktycznie może być przydatna, przetestuję na "gołym" Wordpresie i dam znać za jakiś czas...
Dzięki.
Offline

marcelinakusmier

  • Posty: 1
  • Rejestracja: 9 sie 2015, o 14:17

Re: WP atak brute force

Post9 sie 2015, o 14:23

Podepnij sobie również pod stronę cloudflare ;)
Offline

urszulamania95

  • Posty: 2
  • Rejestracja: 27 lis 2013, o 11:26
  • Lokalizacja: Wrocław

Re: WP atak brute force

Post17 wrz 2015, o 08:43

ja też miałam ten problem ale teraz już mam wdrożone podwójne logowanie i niech ich .. ale nie dobiorą się do mojej strony

Wróć do Systemy CMS

Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 1 gość