From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] new package: proxychains
Date: Tue, 08 Jan 2013 23:10:00 +0200 [thread overview]
Message-ID: <50EC8B28.6090207@petroprogram.com> (raw)
In-Reply-To: <50EC7403.9010309@petroprogram.com>
Thomas, All.
This is something that I susbect most of you already know but I repeat
it here anyway:
Newer completely trust those free public proxies that are listed outside
in the Net.
Ever.
Some of them like https://hidemyass.com/proxy-list will offer free
"anonymous" proxies for your use.
I did some testing and found out that not single one of those so called
free high "anonymous" proxies in
that list did what it was suppose to do but happily revealed your true
IP-address.
Some free anonymous proxy sites on the other hand do what they promise
for example: http://www.freeproxylists.net/?pr=HTTPS&a[]=2&s=rs
Bottom line is this:
If you are using this proxychains program to bybass censorhip
(a' la Great Firewall of China, so that you can watch Youtube) of your
country then please take care
and *always test your proxy or proxies beforehand!!!*
There are plenty of sites like http://www.whatsmyip.org and others that
can show if your IP is the same
as proxy or if the proxy(proxies) will reveal your true IP.
(I even made one IP sniffing page myself
http://www.petroprogram.com/ProxyCheckSimple2.php )
So always remember to test those free proxies beforehand and newer do
any e-mail checking or online bank
stuff throught those proxies. Even if it's HTTPS enabled proxy.
Ever!
Regards
Stefan
8.1.2013 21:31, Stefan Fr?berg kirjoitti:
> Hi Thomas
>
> 8.1.2013 21:18, Thomas Petazzoni kirjoitti:
>> Dear Stefan Fr?berg,
>>
>> On Tue, 08 Jan 2013 20:57:07 +0200, Stefan Fr?berg wrote:
>>
>>> Hmmm... could this be a some weird parallel compiling problem ????
>> No. proxychains is a program that LD_PRELOAD a library to overload some
>> of the C library functions. So it reimplements some functions of the C
>> library, but in this case, it reimplements getnameinfo() with a
>> prototype that doesn't match the one of the C library.
> That's really strange because it did match my headers and I had no problem.
>
>> Maybe an idea would be to upgrade to proxychains 4.4:
>> http://sourceforge.net/projects/proxychains/forums/forum/644747/topic/6519406.
>>
>> The main page of proxychains mentions 3.1 as the latest version, but it
>> is not the case. The official Git repo at
>> https://github.com/rofl0r/proxychains contains many more recent
>> versions. Most likely the problem is already fixed in a more recent
>> version than 3.1.
>>
>> Could you test a more recent version and submit the corresponding patch?
>>
>> Thanks!
>>
>> Thomas
> Ok, Ill take a look and try a newer version.
>
> Stefan
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2013-01-08 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-23 0:20 [Buildroot] [PATCH] new package: proxychains Stefan Fröberg
2012-12-23 21:17 ` Peter Korsgaard
2013-01-08 17:09 ` Thomas Petazzoni
2013-01-08 18:17 ` Stefan Fröberg
2013-01-08 18:47 ` Stefan Fröberg
2013-01-08 18:57 ` Stefan Fröberg
2013-01-08 19:18 ` Thomas Petazzoni
2013-01-08 19:31 ` Stefan Fröberg
2013-01-08 21:10 ` Stefan Fröberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50EC8B28.6090207@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox