Hi ,
I have a question regarding the IPSpoofing Functionality , i have tested
the CURL loader in my Localsystem , its working fine , but i am unable to
implement the same with a internet website url.
Is this possible with curl loader.
Am i missing some thing.
The config file which i created is(The ips are not mine, they are some
random pick)
########### GENERAL SECTION ################################
BATCH_NAME= custom_hdrs2
CLIENTS_NUM_MAX =50
INTERFACE =eth1
NETMASK=20
IP_ADDR_MIN= 192.168.10.10
IP_ADDR_MAX= 192.168.10.100 #Actually - this is for self-control
CYCLES_NUM= 1
URLS_NUM = 1
########### URL SECTION ####################################
URL= http://www.curl.xxxxx.in/default.aspx
URL_SHORT_NAME=" Index-url"
REQUEST_TYPE=GET
HEADER="User-Agent: the string of my favorite browser"
HEADER="Referer: The second custom header"
TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is enforced by
cancelling url fetch on timeout
TIMER_AFTER_URL_SLEEP =50
Thank and Regards

Hi developers,
this is a feature request.
I would like to request the feature to be able to make my HTTP Basic
authentication requests using credentials (randomly) from and external
file. This feature already exists for GET/POST form based submits
(FORM_RECORDS_FILE) but the systems I need to lead test do not support
this as an authentication method.
Please feel free to reply or ask any questions necessary,
regards,
--
Emil Waijers

Hi Val,
On Mon, Mar 22, 2010 at 6:13 AM, Val Shkolnikov <val@...> wrote:
>
>> Applied the patch, thanks!
>>
>>>
>>> I also noticed that the tag FETCH_PROBAILITY_ONCE is not used, but will
>>> let you decide whether it's worth to keep.
>>>
>>
>> Please, look at the latest version in svn. Thanks!
>>
>> The array of url_fetch_decision was allocated per client only, when
>> FETCH_PROBAILITY_ONCE was defined.
>> The array is used to cache the fetching decision and to decrease
>> the calls to random() for high-load testing.
>>
>> In most of the cases, however, it will be of no use, and it was corrected
>> not to use url_fetch_decision array, when it is not supposed to be
>> allocated.
>>
>>
>
> Have you a chance to look at the version in svn and try the changes made?
> Thanks!
>
> --
> Truly,
> Robert Iakobashvili, Ph.D.
> ......................................................................
> http://www.ghotit.com
> Assistive technology that understands you
> ......................................................................
>
> Sorry, a bit busy. I might have a chance to integrate the new code into
> mine next week.
> /Val
>
Sure, take your time.
--
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
http://www.ghotit.com
Assistive technology that understands you
......................................................................

Hi Robert,
From: Robert Iakobashvili <coroberti@...>
>To: curl-loader-devel <curl-loader-devel@...>
>Sent: Sun, March 21, 2010 12:02:05 AM
>Subject: Re: url probability bug fix and random number use update
>
>>Hi Val,
>
>
>On Sun, Mar 14, 2010 at 8:54 AM, Robert Iakobashvili <coroberti@...> wrote:
>
>>>Hi Val,
>>
>>
>>On Mon, Mar 8, 2010 at 7:16 AM, Val Shkolnikov <val@...> wrote:
>>
>>>>>Hi Robert,
>>>>>> There is a major bug in the curl-loader regarding use of the FETCH_PROBABILITY tag. In loader_fsm.c, svn rev 574, line 1359 is
>>>
>>>>>>cctx->url_curr_index = (size_t) url_next;
>>>
>>>>>>The url index is updated but not the url pointer. The result of this bug is that all urls are selected regardless of the probability somewhat uniformly.
>>>
>>>>>>While debugging this I also reworked the use of probability in the curl-loader to produce better pseudo-random numbers and also added a tag RANDOM_SEED that lets you control the seed. I am attaching the patch against svn rev 574. To use it
>>>
>>>>>>cd curl-loader
>>>>>>patch -p3 <curl-loader.patch.574+vs6
>>>
>>
>>Applied the patch, thanks!
>>
>>>>>
>>>
>>>>>>I also noticed that the tag FETCH_PROBAILITY_ONCE is not used, but will let you decide whether it's worth to keep.
>>>
>>
>>Please, look at the latest version in svn. Thanks!
>>
>>The array of url_fetch_decision was allocated per client only, when FETCH_PROBAILITY_ONCE was defined.
>>>>
>>The array is used to cache the fetching decision and to decrease
>>the calls to random() for high-load testing.
>>
>>In most of the cases, however, it will be of no use, and it was corrected
>>not to use url_fetch_decision array, when it is not supposed to be allocated.
>>>>
>>
>Have you a chance to look at the version in svn and try the changes made?
>Thanks!
>
>--
>Truly,
>Robert Iakobashvili, Ph.D.
>......................................................................
>www.ghotit.com
>Assistive technology that understands you
>......................................................................
>Sorry, a bit busy. I might have a chance to integrate the new code into mine next week.
/Val

Hi Val,
On Sun, Mar 14, 2010 at 8:54 AM, Robert Iakobashvili <coroberti@...>wrote:
> Hi Val,
>
> On Mon, Mar 8, 2010 at 7:16 AM, Val Shkolnikov <val@...> wrote:
>
>> Hi Robert,
>> There is a major bug in the curl-loader regarding use of the
>> FETCH_PROBABILITY tag. In loader_fsm.c, svn rev 574, line 1359 is
>>
>> cctx->url_curr_index = (size_t) url_next;
>>
>> The url index is updated but not the url pointer. The result of this bug
>> is that all urls are selected regardless of the probability somewhat
>> uniformly.
>>
>> While debugging this I also reworked the use of probability in the
>> curl-loader to produce better pseudo-random numbers and also added a tag
>> RANDOM_SEED that lets you control the seed. I am attaching the patch
>> against svn rev 574. To use it
>>
>> cd curl-loader
>> patch -p3 <curl-loader.patch.574+vs6
>>
>
> Applied the patch, thanks!
>
>>
>> I also noticed that the tag FETCH_PROBAILITY_ONCE is not used, but will
>> let you decide whether it's worth to keep.
>>
>
> Please, look at the latest version in svn. Thanks!
>
> The array of url_fetch_decision was allocated per client only, when
> FETCH_PROBAILITY_ONCE was defined.
> The array is used to cache the fetching decision and to decrease
> the calls to random() for high-load testing.
>
> In most of the cases, however, it will be of no use, and it was corrected
> not to use url_fetch_decision array, when it is not supposed to be
> allocated.
>
>
Have you a chance to look at the version in svn and try the changes made?
Thanks!
--
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
http://www.ghotit.com
Assistive technology that understands you
......................................................................

Hi Val,
On Tue, Mar 9, 2010 at 7:26 AM, Val Shkolnikov <val@...> wrote:
> Hi Robert,
> sorry for the flood of fixes but this particular problem annoyed me for a
> while, and I finally got around to it. Attached is a fix for the above tag
> parsing that caused sporadic errors. The reason was that the strtok_r
> delimiter argument is supposed to be a string, not a character address. The
> same bug is also in another part of the same source (comma). I also added
> line number printing to the error diagnostic.
> Regards,
> /Val
>
Thanks, applied!
--
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
http://www.ghotit.com
Assistive technology that understands you
......................................................................

Hi Val,
On Mon, Mar 8, 2010 at 7:16 AM, Val Shkolnikov <val@...> wrote:
> Hi Robert,
> There is a major bug in the curl-loader regarding use of the
> FETCH_PROBABILITY tag. In loader_fsm.c, svn rev 574, line 1359 is
>
> cctx->url_curr_index = (size_t) url_next;
>
> The url index is updated but not the url pointer. The result of this bug
> is that all urls are selected regardless of the probability somewhat
> uniformly.
>
> While debugging this I also reworked the use of probability in the
> curl-loader to produce better pseudo-random numbers and also added a tag
> RANDOM_SEED that lets you control the seed. I am attaching the patch
> against svn rev 574. To use it
>
> cd curl-loader
> patch -p3 <curl-loader.patch.574+vs6
>
Applied the patch, thanks!
>
> I also noticed that the tag FETCH_PROBAILITY_ONCE is not used, but will let
> you decide whether it's worth to keep.
>
Please, look at the latest version in svn. Thanks!
The array of url_fetch_decision was allocated per client only, when
FETCH_PROBAILITY_ONCE was defined.
The array is used to cache the fetching decision and to decrease
the calls to random() for high-load testing.
In most of the cases, however, it will be of no use, and it was corrected
not to use url_fetch_decision array, when it is not supposed to be
allocated.
>
> Regards,
> /Val
>
Best wishes!
Robert Iakobashvili, Ph.D.
......................................................................
http://www.ghotit.com
Assistive technology that understands you
......................................................................

Hi Val,
On Tue, Mar 9, 2010 at 7:26 AM, Val Shkolnikov <val@...> wrote:
> Hi Robert,
> sorry for the flood of fixes but this particular problem annoyed me for a
> while, and I finally got around to it. Attached is a fix for the above tag
> parsing that caused sporadic errors. The reason was that the strtok_r
> delimiter argument is supposed to be a string, not a character address. The
> same bug is also in another part of the same source (comma). I also added
> line number printing to the error diagnostic.
> Regards,
> /Val
>
>
> Correct fix, Thanks!
>
> --
> Truly,
> Robert Iakobashvili, Ph.D.
> ......................................................................
> http://www.ghotit.com
> Assistive technology that understands you
> ......................................................................
>

Hi Robert,
sorry for the flood of fixes but this particular problem annoyed me for a while, and I finally got around to it. Attached is a fix for the above tag parsing that caused sporadic errors. The reason was that the strtok_r delimiter argument is supposed to be a string, not a character address. The same bug is also in another part of the same source (comma). I also added line number printing to the error diagnostic.
Regards,
/Val

Hi Val,
On Mon, Mar 8, 2010 at 7:16 AM, Val Shkolnikov <val@...> wrote:
> Hi Robert,
> There is a major bug in the curl-loader regarding use of the
> FETCH_PROBABILITY tag. In loader_fsm.c, svn rev 574, line 1359 is
>
> cctx->url_curr_index = (size_t) url_next;
>
> The url index is updated but not the url pointer. The result of this bug
> is that all urls are selected regardless of the probability somewhat
> uniformly.
>
Thank you. I'll investigate, when it was broken.
>
> While debugging this I also reworked the use of probability in the
> curl-loader to produce better pseudo-random numbers and also added a tag
> RANDOM_SEED that lets you control the seed. I am attaching the patch
> against svn rev 574. To use it
>
> cd curl-loader
> patch -p3 <curl-loader.patch.574+vs6
>
> I also noticed that the tag FETCH_PROBAILITY_ONCE is not used, but will let
> you decide whether it's worth to keep.
>
> Regards,
> /Val
Thank you very much for your reproting and the patch.
I will look into these issues.
--
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
http://www.ghotit.com
Assistive technology that understands you
......................................................................

Hi Robert,
There is a major bug in the curl-loader regarding use of the FETCH_PROBABILITY tag. In loader_fsm.c, svn rev 574, line 1359 is
cctx->url_curr_index = (size_t) url_next;
The url index is updated but not the url pointer. The result of this bug is that all urls are selected regardless of the probability somewhat uniformly.
While debugging this I also reworked the use of probability in the curl-loader to produce better pseudo-random numbers and also added a tag RANDOM_SEED that lets you control the seed. I am attaching the patch against svn rev 574. To use it
cd curl-loader
patch -p3 <curl-loader.patch.574+vs6
I also noticed that the tag FETCH_PROBAILITY_ONCE is not used, but will let you decide whether it's worth to keep.
Regards,
/Val

Dear WP,
On Wed, Mar 3, 2010 at 5:07 PM, 王鹏 <sjzwpeng@...> wrote:
> Hi Robert,
>
> Thanks for your quickly response, for curl-loader, I have search docs, but
> can not find parameters/tags which receive thousands users to realize
> multiple proxy auth, could you point out how to set it?
>
> Thanks,
> WP
>
Got it. You wish to test the authentication of proxy with
thousand of users, where each user possesses his own and unique credentials.
Sorry, we do not have such functionality for proxy, whereas it exists
for non-proxy.
--
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
http://www.ghotit.com
Assistive technology that understands you
......................................................................

Hi WP,
On Wed, Mar 3, 2010 at 3:56 PM, 王鹏 <sjzwpeng@...> wrote:
> Hi Everyone,
>
> I get a question about authenticate mutiple users to an explicit proxy. I
> don't know how curl-loader specify username and password from conf file so
> that I can proxy auth with multiple users instead of only set one user
> credential in the tag PROXY_AUTH_CREDENTIALS
>
> FAQ does not mention that scenario, looks like it only have config for
> forms, such as FORM_USAGE_TYPE= "RECORDS_FROM_FILE"
>
> I can auth successfully with one user.
> PROXY_AUTH_METHOD=NTLM
> PROXY_AUTH_CREDENTIALS=Username:password
>
>
> Any assistance would be greatly appreciated.
>
> Thanks,
> WP
>
libcurl may be broken for NTLM.
All other methods of authentication can be used for thousands of users and
more.
--
Truly,
Robert Iakobashvili, Ph.D.
......................................................................
http://www.ghotit.com
Assistive technology that understands you
......................................................................

Hi Everyone,
I get a question about authenticate mutiple users to an explicit proxy. I
don't know how curl-loader specify username and password from conf file so
that I can proxy auth with multiple users instead of only set one user
credential in the tag PROXY_AUTH_CREDENTIALS
FAQ does not mention that scenario, looks like it only have config for
forms, such as FORM_USAGE_TYPE= "RECORDS_FROM_FILE"
I can auth successfully with one user.
PROXY_AUTH_METHOD=NTLM
PROXY_AUTH_CREDENTIALS=Username:password
Any assistance would be greatly appreciated.
Thanks,
WP

Community

Help

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

CountryState

JavaScript is required for this form.

I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. I understand that I can withdraw my consent at any time. Please refer to our Privacy Policy or Contact Us for more details