open this link to study security about Firewall
Wednesday, 24 August 2011
How to open restricted web sites from school / college / company
So you want to access Facebook or use instant messenger from school or work? By connecting to your cable/DSL internet connection from school/work, you can! Here's how:
Web Proxy
If you only need access to restricted web sites from school or work, read this tutorial.
SOCKS Proxy
If you need to access restricted web sites and instant messenger, ftp, or other restricted protocols, read this tutorial (easier for Windows users). or this one (easier for linux/osx/unix users). Both tutorials work for Windows and *nix-based operating systems.
----------------------------------------------------------------------------------------------------
Let's begin.
- Download the latest version of Apache httpd from here. Click the "Other files" link to download binaries.
- Install. For Windows, it's just like any other Windows installation. You'll be prompted for a few things during installation like domain name. You can enter your IP address or, better yet, get a free dynamic domain name at no-ip.com or DynDNS.org. On Windows, you should choose the option to install as a service. Otherwise, you'll have an annoying command-prompt on your desktop when apache runs.
- Open the file httpd.conf installed by apache. This is the configuration file for the web server. On Windows, the default location is c:\Program Files\Apache Group\Apache2\conf\httpd.conf. Comments in the file start with "#".
- Around line 120, you'll see Listen 8080 or Listen 80. Change this to the port on which you'd like to expose the proxy server. If this proxy server will be running on a residential cable/DSL connection, many ISPs prevent inbound connections on to residential connections on ports 80 and 25 as well as others. To find out which inbound ports your ISP prevents connection to, find the FAQ for your ISP at dslreports.com. Additionally, if you will be connecting to this proxy server from a corporate environment, be aware that some corporate firewalls only permit outbound connections on a few ports to machines outside their firewall. Often outbound ports 21, 23, 80, and 443 are permitted because they are typically used for FTP, telnet, HTTP, and SSL, respectively.
- If your IP address is in one of these ranges:
- 10.0.0.0 - 10.255.255.255
- 172.16.0.0 - 172.31.255.255
- 192.168.0.0 - 192.168.255.255
- Uncomment the following lines by removing the leading "#" LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
- Add the following to the end of the file: ProxyRequests Onwhere aaa.bbb.ccc.ddd is the IP address of the remote machine which will connect to your PC. If you omit the green text, you will be running an open proxy. FoxyProxy does not endorse or condone open proxies.
ProxyVia On
<Proxy *>
Order deny,allow
Deny from all
Allow from aaa.bbb.ccc.ddd
</Proxy> - Save the file and start apache. On Windows, this is done either from the Start Menu or from the Service Control Panel (if you installed apache httpd as a service).
Caching (optional)
Apache can cache web server responses, such as commonly-used images, to speed things up. HTTPS responses are not cached due to security restrictions. To enable caching, add the following to the end of http.conf: LoadModule cache_module modules/mod_cache.so
<IfModule mod_cache.c>
# This sets up caching to disk.
# You can setup caching to memory if you prefer.
LoadModule disk_cache_module modules/mod_disk_cache.so
<IfModule mod_disk_cache.c>
CacheRoot c:/temp/cacheroot
CacheEnable disk /
CacheDirLevels 5
CacheDirLength 4
# Read this for info about the above options
# Read this for info on cleaning the cache
</IfModule>
<IfModule mod_cache.c>
# This sets up caching to disk.
# You can setup caching to memory if you prefer.
LoadModule disk_cache_module modules/mod_disk_cache.so
<IfModule mod_disk_cache.c>
CacheRoot c:/temp/cacheroot
CacheEnable disk /
CacheDirLevels 5
CacheDirLength 4
# Read this for info about the above options
# Read this for info on cleaning the cache
</IfModule>
Configuring FoxyProxy to Use Your Proxy
- Create a new proxy definition by clicking the "Add New Proxy" button on the FoxyProxy Options dialog [screenshot].
- Enter a name and optionally, notes, on the General tab [screenshot]. For example, under name you might enter "Apache HTTPD" and under notes, "Web proxy running at home"
- On the Proxy Details tab [screenshot], select "Manual Proxy Configuration". In the HTTP proxy field, enter the IP address of the machine on which you installed Apache httpd. If your ISP periodically changes your IP address (many cable/dsl ISPs do), get a free No-IP or DynDNS account. These services grant you a free domain name; for example, myproxy.bounceme.net. You run client software on your PC which "phones home" to DynDNS/No-IP every 30 minutes, informing them of your current IP address. Note that many modern consumer-oriented routers from Linksys, Netgear, D-Link, etc. have this software built-in so you don't need to run a client on your PC. If you have a domain name instead of an IP address, enter it here.
- In the port field, enter the port under which you configured Apache httpd to run. This is specified in the c:\Program Files\Apache Group\Apache2\conf\httpd.conf file on the Listen xxxx line.
- Leave all other fields on the Proxy Details tab blank.
- On the Patterns tab [screenshot], enter patterns which match blocked URLs at your school/place-of-business.
- Start surfing the web!
Optional
If you would like to
- Configure encryption so all communications between you and your proxy are encrypted (even plain http:// addresses)
- Restrict who can use the proxy not by IP address but by password or digital certificate
Wednesday, 3 August 2011
Only for Girl's use
Only for Girl's
Get all information related to beauty and fashion click on following link
Get all information related to beauty and fashion click on following link
Monday, 18 July 2011
Friday, 27 May 2011
Facebook takes Microsoft help to fight child pornography
In a bid to drive paedophiles away from its service, Facebook has announced to introduce a new technology which will automatically trawl photos posted by users for child abuse.
The popular social networking site, which claims to have more than 500 million users, has now partnered with Microsoft and will implement its PhotoDNA technology, designed to identify and remove images that exploit or endanger children.
Run by the National Center for Missing and Exploited Children (NCMEC), the PhotoDNA technology creates a "blueprint" of an inappropriate or offencive image and can search through billions of other images to locate photos with similarly inappropriate features, the Daily Telegraph reported.
According to Bill Harmon, a lawyer in Microsoft's digital crimes unit, PhotoDNA detects child pornography with "zero false positives".
"Some images become 'popular' and are used time and time again, making good targets for the PhotoDNA program," he said in a post on the Microsoft blog.
Facebook was heavily criticised over its child protection efforts by Britain's Child Exploitation and Online Protection Centre (CEOP), the police agency responsible for tracking down paedophiles online.
It followed the murder of 17-year-old Ashleigh Hall, who was lured to her death by a 33-year-old man who posed as a teenager on the dominant social network.
PhotoDNA is just the latest of several safety initiatives launched since by Facebook.
Microsoft has already implemented the system on its Bing search engine and SkyDrive online storage service, and says it detected more than 1,500 illegal images on the former and more than 1,000 on the latter.
"Even though NCMEC is a US-based organisation, we found image matches on our services stemming from abuse that has occurred across many countries, including the US, UK and Brazil among others," said Harmon
"We hope that Facebook's adoption of PhotoDNA serves as a springboard for other online service providers to take advantage of the opportunity available through NCMEC's PhotoDNA program and, in fact, we know that others are exploring the possibility right now," he added.
The popular social networking site, which claims to have more than 500 million users, has now partnered with Microsoft and will implement its PhotoDNA technology, designed to identify and remove images that exploit or endanger children.
Run by the National Center for Missing and Exploited Children (NCMEC), the PhotoDNA technology creates a "blueprint" of an inappropriate or offencive image and can search through billions of other images to locate photos with similarly inappropriate features, the Daily Telegraph reported.
According to Bill Harmon, a lawyer in Microsoft's digital crimes unit, PhotoDNA detects child pornography with "zero false positives".
"Some images become 'popular' and are used time and time again, making good targets for the PhotoDNA program," he said in a post on the Microsoft blog.
Facebook was heavily criticised over its child protection efforts by Britain's Child Exploitation and Online Protection Centre (CEOP), the police agency responsible for tracking down paedophiles online.
It followed the murder of 17-year-old Ashleigh Hall, who was lured to her death by a 33-year-old man who posed as a teenager on the dominant social network.
PhotoDNA is just the latest of several safety initiatives launched since by Facebook.
Microsoft has already implemented the system on its Bing search engine and SkyDrive online storage service, and says it detected more than 1,500 illegal images on the former and more than 1,000 on the latter.
"Even though NCMEC is a US-based organisation, we found image matches on our services stemming from abuse that has occurred across many countries, including the US, UK and Brazil among others," said Harmon
"We hope that Facebook's adoption of PhotoDNA serves as a springboard for other online service providers to take advantage of the opportunity available through NCMEC's PhotoDNA program and, in fact, we know that others are exploring the possibility right now," he added.
LinkedIn site is vulnerable
LinkedIn's professional networking website has security flaws that makes users' accounts vulnerable to attack by hackers who could break in without ever needing passwords, according to a security researcher who identified the problem.
News of the vulnerability surfaced over the weekend, only days after LinkedIn Corp (LNKD.N) went public last week with a trading debut that saw the value of its shares more than double, evoking memories of the dot.com investment boom of the late 1990s.
Rishi Narang -- an independent Internet security researcher based near New Delhi, India, who discovered the security flaw -- told Reuters on Sunday that the problem is related to the way LinkedIn manages a commonly used type of data file known as a cookie.
After a user enters the proper username and password to access an account, LinkedIn's system creates a cookie "LEO_AUTH_TOKEN" on the user's computer that serves as a key to gain access to the account.
Lots of websites use such cookies, but what makes the LinkedIn cookie unusual is that it does not expire for a full year from the date it is created, Narang said.
He detailed the vulnerability in a posting on his blog, click www.wtfuzz.com on Saturday.
Most commercial websites would typically design their access token cookies to expire in 24 hours, or even earlier if a user were to first log off the account, Narang said.
There are some exceptions: Banking sites often log users off after 5 or 10 minutes of inactivity. Google gives its users the option of using cookies that keep them logged on for several weeks, but it lets the user decide first.
The long life of the LinkedIn cookie means that anybody who gets hold of that file can load it on to a PC and easily gain access to the original user's account for as much as a year.
The company issued a statement saying that it already takes steps to secure the accounts of its customers.
"LinkedIn takes the privacy and security of our members seriously," the statement said.
"Whether you are on LinkedIn or any other site, it's always a good idea to choose trusted and encrypted WiFi networks or VPNs (virtual private networks) whenever possible."
The company said that it currently supports SSL, or secure sockets layer, technology for encrypting certain "sensitive" data, including account logins.
But those access token cookies are not yet scrambled with SSL. That makes it possible for hackers to steal the cookies using widely available tools for sniffing Internet traffic, Narang said.
LinkedIn said in its statement that it is preparing to offer "opt-in" SSL support for other parts of the site, an option that would cover encryption of those cookies. The company said it expected that to be available "in the coming months."
But LinkedIn officials declined to respond to Narang's critique of the company's use of a cookie with a one-year expiration.
Narang said that problem is particularly acute because LinkedIn's users are not aware of the problem and have no idea that they should be protecting those cookies.
He said he found four cookies with valid LinkedIn access tokens had been uploaded to a LinkedIn developer forum by users who were posting questions about their use.
He said he downloaded those cookies and was able to access the accounts of the four LinkedIn subscribers.
News of the vulnerability surfaced over the weekend, only days after LinkedIn Corp (LNKD.N) went public last week with a trading debut that saw the value of its shares more than double, evoking memories of the dot.com investment boom of the late 1990s.
Rishi Narang -- an independent Internet security researcher based near New Delhi, India, who discovered the security flaw -- told Reuters on Sunday that the problem is related to the way LinkedIn manages a commonly used type of data file known as a cookie.
After a user enters the proper username and password to access an account, LinkedIn's system creates a cookie "LEO_AUTH_TOKEN" on the user's computer that serves as a key to gain access to the account.
Lots of websites use such cookies, but what makes the LinkedIn cookie unusual is that it does not expire for a full year from the date it is created, Narang said.
He detailed the vulnerability in a posting on his blog, click www.wtfuzz.com on Saturday.
Most commercial websites would typically design their access token cookies to expire in 24 hours, or even earlier if a user were to first log off the account, Narang said.
There are some exceptions: Banking sites often log users off after 5 or 10 minutes of inactivity. Google gives its users the option of using cookies that keep them logged on for several weeks, but it lets the user decide first.
The long life of the LinkedIn cookie means that anybody who gets hold of that file can load it on to a PC and easily gain access to the original user's account for as much as a year.
The company issued a statement saying that it already takes steps to secure the accounts of its customers.
"LinkedIn takes the privacy and security of our members seriously," the statement said.
"Whether you are on LinkedIn or any other site, it's always a good idea to choose trusted and encrypted WiFi networks or VPNs (virtual private networks) whenever possible."
The company said that it currently supports SSL, or secure sockets layer, technology for encrypting certain "sensitive" data, including account logins.
But those access token cookies are not yet scrambled with SSL. That makes it possible for hackers to steal the cookies using widely available tools for sniffing Internet traffic, Narang said.
LinkedIn said in its statement that it is preparing to offer "opt-in" SSL support for other parts of the site, an option that would cover encryption of those cookies. The company said it expected that to be available "in the coming months."
But LinkedIn officials declined to respond to Narang's critique of the company's use of a cookie with a one-year expiration.
Narang said that problem is particularly acute because LinkedIn's users are not aware of the problem and have no idea that they should be protecting those cookies.
He said he found four cookies with valid LinkedIn access tokens had been uploaded to a LinkedIn developer forum by users who were posting questions about their use.
He said he downloaded those cookies and was able to access the accounts of the four LinkedIn subscribers.
Friday, 22 April 2011
Requirements of I Phone Developers in Ahmedabad
AMS is looking for fresh I-phone developers
The candidates need to have good knowledge of C# .Net
Candidates shall be provided training too for the same.
Interested students are instructed to send their CV to sachin@sachinsehgal.com on immediate basis
The candidates need to have good knowledge of C# .Net
Candidates shall be provided training too for the same.
Interested students are instructed to send their CV to sachin@sachinsehgal.com on immediate basis
Subscribe to:
Posts (Atom)