RE: Home proxy to webserver

[Ray McClure <Ray.G.McClure () hofstra edu>]

Check this out:
http://portableapps.com/

~R
-----Original Message-----
From: listbounce () securityfocus com [mailto:listbounce () securityfocus com] On Behalf Of Miguel Regala
Sent: Thursday, October 13, 2011 6:15 PM
To: krymson () gmail com
Cc: security-basics () securityfocus com
Subject: Re: Home proxy to webserver

Running a browser in a USB flash drive is something I don't hear in a
long time. That's a great idea. Thanks!

2011/10/13  <krymson () gmail com>:
> If you open a web browser at the public terminal and proxy your connection through, say, a server you have at home, 
> your browser on the public terminal is still going to often use local cookies and history and optional storage of 
> filled-in form fields. You'll not gain any protection. I'm assuming you mean a simple web proxy, and not some sort of 
> other tunneling setup like a VPN.
>
> The way around this problem is to avoid using the browser on that untrusted system.
>
> You want to do one of two things:
> 1) Use a full VPN connection home along with screen forwarding so you're actually just consuming the remote browser.
>
> 2) Use a browser you control, i.e. via a USB stick with portable apps on it.
>
> You're still open to other attacks, but that's a good start.
>
>
> <- snip ->
> Hi list,
>
> i'm worried with the amount of people that log in into their accounts
> (critical ones, like email, bank account) on public servers and
> besides that doing the usual error of not logging out. Most of the
> times, the way you know someone visited e.g gmail.com is, well,
> accessing gmail.com. What would happen if everyone could connect via a
> self-own proxy, via a redirection service?
>
> Well, that's my question. Would that mitigate the common problems?
>
> 1) Cookie storage
> 2) History storage
> 3) Maintain connection speed, reliability and security
>
> Regards,
> Miguel
>
> ------------------------------------------------------------------------
> Securing Apache Web Server with thawte Digital Certificate
> In this guide we examine the importance of Apache-SSL and who needs an SSL certificate.  We look at how SSL works, 
> how it benefits your company and how your customers can tell if a site is secure. You will find out how to test, 
> purchase, install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for 
> set-up are highlighted to help you ensure efficient ongoing management of your encryption keys and digital 
> certificates.
>
> http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be442f727d1
> ------------------------------------------------------------------------

------------------------------------------------------------------------
Securing Apache Web Server with thawte Digital Certificate
In this guide we examine the importance of Apache-SSL and who needs an SSL certificate.  We look at how SSL works, how 
it benefits your company and how your customers can tell if a site is secure. You will find out how to test, purchase, 
install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for set-up are 
highlighted to help you ensure efficient ongoing management of your encryption keys and digital certificates.

http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be442f727d1
------------------------------------------------------------------------




------------------------------------------------------------------------
Securing Apache Web Server with thawte Digital Certificate
In this guide we examine the importance of Apache-SSL and who needs an SSL certificate.  We look at how SSL works, how 
it benefits your company and how your customers can tell if a site is secure. You will find out how to test, purchase, 
install and use a thawte Digital Certificate on your Apache web server. Throughout, best practices for set-up are 
highlighted to help you ensure efficient ongoing management of your encryption keys and digital certificates.

http://www.dinclinx.com/Redirect.aspx?36;4175;25;1371;0;5;946;e13b6be442f727d1
------------------------------------------------------------------------