نویسنده موضوع: استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:) (دفعات بازدید: 6511 بار)

harand · « : 17 آبان 1395، 08:16 ق‌ظ »

سلام من میخوام وصل بشم به داکر هاب ولی به ما سرویس نمیده!proxychains رو نصب کردم ولی وقتی مثلا دستور proxychain docker search centos میگه کامند نامعتبر هست:)

کد: [انتخاب]

No command 'proxychain' found, did you mean:
 Command 'proxychains' from package 'proxychains' (universe)
proxychain: command not found

لطفا راهنمایی کنید جطوری این سرویس هارو دور بزنیم:)

ارباب! · « **پاسخ #1 :** 17 آبان 1395، 10:58 ق‌ظ »

Did you mean...
?...command proxychains

harand · « **پاسخ #2 :** 17 آبان 1395، 11:07 ق‌ظ »

منظورم اینکه چطوری از تور داخل تر مینال استفاده کنم (برای کار با داکر)

دانیال بهزادی · « **پاسخ #3 :** 17 آبان 1395، 02:17 ب‌ظ »

کد: [انتخاب]

$ export http_proxy=http://IP:PORT

harand · « **پاسخ #4 :** 17 آبان 1395، 02:40 ب‌ظ »

حل نشد

کد: [انتخاب]

 export http_proxy=127.0.0.1:9150

harand · « **پاسخ #5 :** 18 آبان 1395، 07:59 ق‌ظ »

سلام

با ست کردن متغییرهای https_proxy=http://127.0.0.1:9150http_proxy=http://127.0.0.1:9150 و
http_proxy=http://127.0.0.1:9150http_proxy=http://127.0.0.1:9150 بازم مشکل حل نشد

کد: [انتخاب]

Pulling repository docker.io/library/centos
Error: Status 403 trying to pull repository library/centos: "<html><body><h1>403 Forbidden</h1>\nSince Docker is a US company, we must comply with US export control regulations. In an effort to comply with these, we now block all IP addresses that are located in Cuba, Iran, North Korea, Republic of Crimea, Sudan, and Syria. If you are not in one of these cities, countries, or regions and are blocked, please reach out to https://support.docker.com\n</body></html>\n\n"

لطفا راهنمایی کنید

ارباب! · « **پاسخ #6 :** 18 آبان 1395، 09:13 ب‌ظ »

اگه از tor استفاده می کنید احتمالا همون 9150 باشه port ولی تا جایی که یادمه شاید 9050 یا 9051 یا 9151 هم باشه.. می تونید پیداش کنید..
اما شاید شما بهتر باشه اول به protocol دقت کنید.. فک کنم tor از socks4 پشتیبانی می کنه به طور پیش فرض، نه http و https.. می خواید اینا رو هم امتحان کنید..
بعدشم proxychains خودش یه config جدا داره که براش یه فایل etc/proxychains.conf/ موجوده.. محتویاتش رو نگاه کنید.. خودش به طور پیش فرض برای من به این صورت config شده برای tor..:

کد: [انتخاب]

socks4 127.0.0.1 9050

harand · « **پاسخ #7 :** 21 آبان 1395، 08:47 ق‌ظ »

سلام

مشکل هنوز پابرجاهست و استفاده از proxychains و ست کردن متغیر http_proxy هم فایده نداشت

کد: [انتخاب]

proxychains docker pull centos
ProxyChains-3.1 (http://proxychains.sf.net)
Using default tag: latest
Pulling repository docker.io/library/centos
Error: Status 403 trying to pull repository library/centos: "<html><body><h1>403 Forbidden</h1>\nSince Docker is a US company, we must comply with US export control regulations. In an effort to comply with these, we now block all IP addresses that are located in Cuba, Iran, North Korea, Republic of Crimea, Sudan, and Syria. If you are not in one of these cities, countries, or regions and are blocked, please reach out to https://support.docker.com\n</body></html>\n\n"

کد: [انتخاب]

export http_proxy="http://127.0.0.1:9150"
hosein@hosein-EP43-UD3L:~$ docker pull centos
Using default tag: latest
Pulling repository docker.io/library/centos
Error: Status 403 trying to pull repository library/centos: "<html><body><h1>403 Forbidden</h1>\nSince Docker is a US company, we must comply with US export control regulations. In an effort to comply with these, we now block all IP addresses that are located in Cuba, Iran, North Korea, Republic of Crimea, Sudan, and Syria. If you are not in one of these cities, countries, or regions and are blocked, please reach out to https://support.docker.com\n</body></html>\n\n"

ارباب! · « **پاسخ #8 :** 21 آبان 1395، 04:16 ب‌ظ »

سلام دوست عزیز..
یه اشاره ای در پست قبل کردم که ‌proxychains فایل config اختصاصی خودش رو داره و اصن نیازی نیس اون متغیر رو set کنید..
شما فقط اون فایل رو ویرایش کنید.. توی اون فایل protocol باید روی socks4 باشه (‌tor ظاهرا از http protocol پشتیبانی نمی کنه..) و port رو هم توضیح دادم ماجراشو..
جهت تست شاید بخواید از یه همچین دستوری استفاده کنید مثلا..:

کد: [انتخاب]

proxychains w3m facebook.com

harand · « **پاسخ #9 :** 21 آبان 1395، 08:14 ب‌ظ »

ممنون که جواب میدی خب ‌proxychainsکه به صصورت پیشفرض روی تور ست هست ولی نمیدونم چرا جواب نمیده یه تیکه از فایل proxychains.conf

کد: [انتخاب]

# defaults set to "tor"
socks4  127.0.0.1 9150

ولی جواب نمیده

ارباب! · « **پاسخ #10 :** 22 آبان 1395، 01:34 ق‌ظ »

خواهش می کنم.. مطمئنید tor در حال اجرائه..؟ من از tor browser bundle..
برای این که بفهمید چه port هایی بازه برای LISTEN این دستور رو خروجیش رو چک کنید..:

کد: [انتخاب]

netstat -ntlp | grep LISTENاگه حل نمی شه خروجیشو بذارید ببینیم اوضاع از چه قراره..

harand · « **پاسخ #11 :** 22 آبان 1395، 08:10 ق‌ظ »

خروجی دستور netstat -ntlp | grep LISTEN

کد: [انتخاب]

 netstat -ntlp | grep LISTEN
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 127.0.0.1:9150          0.0.0.0:*               LISTEN      -               
tcp        0      0 127.0.0.1:46879         0.0.0.0:*               LISTEN      2775/obfs4proxy 
tcp        0      0 127.0.0.1:9151          0.0.0.0:*               LISTEN      -               
tcp        0      0 127.0.0.1:36128         0.0.0.0:*               LISTEN      2775/obfs4proxy 
tcp        0      0 127.0.0.1:33350         0.0.0.0:*               LISTEN      2775/obfs4proxy 
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      -               
tcp        0      0 127.0.1.1:53            0.0.0.0:*               LISTEN      -               
tcp        0      0 127.0.0.1:34521         0.0.0.0:*               LISTEN      2775/obfs4proxy 
tcp        0      0 127.0.0.1:9050          0.0.0.0:*               LISTEN      -               
tcp6       0      0 :::80                   :::*                    LISTEN      -

harand · « **پاسخ #12 :** 23 آبان 1395، 08:42 ق‌ظ »

دوستان لطفا راهنمایی کنید

s1mpleworld · « **پاسخ #13 :** 23 آبان 1395، 12:21 ب‌ظ »

درود دوست عزیز

لطفا کانفیگ فایل /etc/tor/torrc و /etc/proxychains.conf مال خود را در اینجا قرار دهید

harand · « **پاسخ #14 :** 23 آبان 1395، 12:54 ب‌ظ »

درود

محتویات فایل torrc

کد: [انتخاب]

## Configuration file for a typical Tor user
## Last updated 22 September 2015 for Tor 0.2.7.3-alpha.
## (may or may not work for much older or much newer versions of Tor.)
##
## Lines that begin with "## " try to explain what's going on. Lines
## that begin with just "#" are disabled commands: you can enable them
## by removing the "#" symbol.
##
## See 'man tor', or https://www.torproject.org/docs/tor-manual.html,
## for more options you can use in this file.
##
## Tor will look for this file in various places based on your platform:
## https://www.torproject.org/docs/faq#torrc

## Tor opens a SOCKS proxy on port 9050 by default -- even if you don't
## configure one below. Set "SOCKSPort 0" if you plan to run Tor only
## as a relay, and not make any local application connections yourself.
#SOCKSPort 9050 # Default: Bind to localhost:9050 for local connections.
#SOCKSPort 192.168.0.1:9100 # Bind to this address:port too.

## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SOCKSPolicy is set, we accept
## all (and only) requests that reach a SOCKSPort. Untrusted users who
## can access your SOCKSPort may be able to learn about the connections
## you make.
#SOCKSPolicy accept 192.168.0.0/16
#SOCKSPolicy accept6 FC00::/7
#SOCKSPolicy reject *

## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many Log lines as
## you want.
##
## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
##
## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
#Log notice file /var/log/tor/notices.log
## Send every possible message to /var/log/tor/debug.log
#Log debug file /var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
#Log notice syslog
## To send all messages to stderr:
#Log debug stderr

## Uncomment this to start the process in the background... or use
## --runasdaemon 1 on the command line. This is ignored on Windows;
## see the FAQ entry if you want Tor to run as an NT service.
#RunAsDaemon 1

## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
#DataDirectory /var/lib/tor

## The port on which Tor will listen for local connections from Tor
## controller applications, as documented in control-spec.txt.
#ControlPort 9051
## If you enable the controlport, be sure to enable one of these
## authentication methods, to prevent attackers from accessing it.
#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C
#CookieAuthentication 1

############### This section is just for location-hidden services ###

## Once you have configured a hidden service, you can look at the
## contents of the file ".../hidden_service/hostname" for the address
## to tell people.
##
## HiddenServicePort x y:z says to redirect requests on port x to the
## address y:z.

#HiddenServiceDir /var/lib/tor/hidden_service/
#HiddenServicePort 80 127.0.0.1:80

#HiddenServiceDir /var/lib/tor/other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServicePort 22 127.0.0.1:22

################ This section is just for relays #####################
#
## See https://www.torproject.org/docs/tor-doc-relay for details.

## Required: what port to advertise for incoming Tor connections.
#ORPort 9001
## If you want to listen on a port other than the one advertised in
## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as
## follows.  You'll need to do ipchains or other port forwarding
## yourself to make this work.
#ORPort 443 NoListen
#ORPort 127.0.0.1:9090 NoAdvertise

## The IP address or full DNS name for incoming connections to your
## relay. Leave commented out and Tor will guess.
#Address noname.example.com

## If you have multiple network interfaces, you can specify one for
## outgoing traffic to use.
# OutboundBindAddress 10.0.0.5

## A handle for your relay, so people don't have to refer to it by key.
#Nickname ididnteditheconfig

## Define these to limit how much relayed traffic you will allow. Your
## own traffic is still unthrottled. Note that RelayBandwidthRate must
## be at least 20 kilobytes per second.
## Note that units for these config options are bytes (per second), not
## bits (per second), and that prefixes are binary prefixes, i.e. 2^10,
## 2^20, etc.
#RelayBandwidthRate 100 KBytes  # Throttle traffic to 100KB/s (800Kbps)
#RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB (1600Kb)

## Use these to restrict the maximum traffic per day, week, or month.
## Note that this threshold applies separately to sent and received bytes,
## not to their sum: setting "40 GB" may allow up to 80 GB total before
## hibernating.
##
## Set a maximum of 40 gigabytes each way per period.
#AccountingMax 40 GBytes
## Each period starts daily at midnight (AccountingMax is per day)
#AccountingStart day 00:00
## Each period starts on the 3rd of the month at 15:00 (AccountingMax
## is per month)
#AccountingStart month 3 15:00

## Administrative contact information for this relay or bridge. This line
## can be used to contact you if your relay or bridge is misconfigured or
## something else goes wrong. Note that we archive and publish all
## descriptors containing these lines and that Google indexes them, so
## spammers might also collect them. You may want to obscure the fact that
## it's an email address and/or generate a new address for this purpose.
#ContactInfo Random Person <nobody AT example dot com>
## You might also include your PGP or GPG fingerprint if you have one:
#ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>

## Uncomment this to mirror directory information for others. Please do
## if you have enough bandwidth.
#DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised in
## DirPort (e.g. to advertise 80 but bind to 9091), you can do it as
## follows.  below too. You'll need to do ipchains or other port
## forwarding yourself to make this work.
#DirPort 80 NoListen
#DirPort 127.0.0.1:9091 NoAdvertise
## Uncomment to return an arbitrary blob of html on your DirPort. Now you
## can explain what Tor is if anybody wonders why your IP address is
## contacting them. See contrib/tor-exit-notice.html in Tor's source
## distribution for a sample.
#DirPortFrontPage /etc/tor/tor-exit-notice.html

## Uncomment this if you run more than one Tor relay, and add the identity
## key fingerprint of each Tor relay you control, even if they're on
## different networks. You declare it here so Tor clients can avoid
## using more than one of your relays in a single circuit. See
## https://www.torproject.org/docs/faq#MultipleRelays
## However, you should never include a bridge's fingerprint here, as it would
## break its concealability and potentially reveal its IP/TCP address.
#MyFamily $keyid,$keyid,...

## A comma-separated list of exit policies. They're considered first
## to last, and the first match wins.
##
## If you want to allow the same ports on IPv4 and IPv6, write your rules
## using accept/reject *. If you want to allow different ports on IPv4 and
## IPv6, write your IPv6 rules using accept6/reject6 *6, and your IPv4 rules
## using accept/reject *4.
##
## If you want to _replace_ the default exit policy, end this with either a
## reject *:* or an accept *:*. Otherwise, you're _augmenting_ (prepending to)
## the default exit policy. Leave commented to just use the default, which is
## described in the man page or at
## https://www.torproject.org/documentation.html
##
## Look at https://www.torproject.org/faq-abuse.html#TypicalAbuses
## for issues you might encounter if you use the default exit policy.
##
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down.
##
## For security, by default Tor rejects connections to private (local)
## networks, including to the configured primary public IPv4 and IPv6 addresses,
## and any public IPv4 and IPv6 addresses on any interface on the relay.
## See the man page entry for ExitPolicyRejectPrivate if you want to allow
## "exit enclaving".
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports on IPv4 and IPv6 but no more
#ExitPolicy accept *:119 # accept nntp ports on IPv4 and IPv6 as well as default exit policy
#ExitPolicy accept *4:119 # accept nntp ports on IPv4 only as well as default exit policy
#ExitPolicy accept6 *6:119 # accept nntp ports on IPv6 only as well as default exit policy
#ExitPolicy reject *:* # no exits allowed

## Bridge relays (or "bridges") are Tor relays that aren't listed in the
## main directory. Since there is no complete public list of them, even an
## ISP that filters connections to all the known Tor relays probably
## won't be able to block all the bridges. Also, websites won't treat you
## differently because they won't know you're running Tor. If you can
## be a real relay, please do; but if not, be a bridge!
#BridgeRelay 1
## By default, Tor will advertise your bridge to users through various
## mechanisms like https://bridges.torproject.org/. If you want to run
## a private bridge, for example because you'll give out your bridge
## address manually to your friends, uncomment this line:
#PublishServerDescriptor 0

و محتویات فایل proxychains.conf

کد: [انتخاب]


# proxychains.conf  VER 3.1
#
#        HTTP, SOCKS4, SOCKS5 tunneling proxifier with DNS.
#	

# The option below identifies how the ProxyList is treated.
# only one option should be uncommented at time,
# otherwise the last appearing option will be accepted
#
#dynamic_chain
#
# Dynamic - Each connection will be done via chained proxies
# all proxies chained in the order as they appear in the list
# at least one proxy must be online to play in chain
# (dead proxies are skipped)
# otherwise EINTR is returned to the app
#
strict_chain
#
# Strict - Each connection will be done via chained proxies
# all proxies chained in the order as they appear in the list
# all proxies must be online to play in chain
# otherwise EINTR is returned to the app
#
#random_chain
#
# Random - Each connection will be done via random proxy
# (or proxy chain, see  chain_len) from the list.
# this option is good to test your IDS :)

# Make sense only if random_chain
#chain_len = 2

# Quiet mode (no output from library)
#quiet_mode

# Proxy DNS requests - no leak for DNS data
proxy_dns 

# Some timeouts in milliseconds
tcp_read_time_out 15000
tcp_connect_time_out 8000

# ProxyList format
#       type  host  port [user pass]
#       (values separated by 'tab' or 'blank')
#
#
#        Examples:
#
#            	socks5	192.168.67.78	1080	lamer	secret
#		http	192.168.89.3	8080	justu	hidden
#	 	socks4	192.168.1.49	1080
#	        http	192.168.39.93	8080	
#		
#
#       proxy types: http, socks4, socks5
#        ( auth types supported: "basic"-http  "user/pass"-socks )
#
[ProxyList]
# add proxy here ...
# meanwile
# defaults set to "tor"
socks4 	127.0.0.1 9150

انجمن‌های فارسی اوبونتو

نویسنده موضوع: استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:) (دفعات بازدید: 6511 بار)

harand

استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:)

ارباب!

پاسخ : استفاده از سرویس های که کشور ما رو تحریم کردند:)

harand

پاسخ : استفاده از سرویس های که کشور ما رو تحریم کردند:)

دانیال بهزادی

پاسخ : استفاده از سرویس های که کشور ما رو تحریم کردند:)

harand

پاسخ : استفاده از سرویس های که کشور ما رو تحریم کردند:)

harand

پاسخ : استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:)

ارباب!

پاسخ : استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:)

harand

پاسخ : استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:)

ارباب!

پاسخ : استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:)

harand

پاسخ : استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:)

ارباب!

پاسخ : استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:)

harand

پاسخ : استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:)

harand

پاسخ : استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:)

s1mpleworld

پاسخ : استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:)

harand

پاسخ : استفاده از سرویس های داخل ترمینال که کشور ما رو تحریم کردند:)