James Knott schreef:
Amedee Van Gasse wrote:
James Knott schreef:
Amedee Van Gasse wrote:
James Knott schreef:
Patrick Shanahan wrote:
AND, it's trivial to ssh into your home box and access an email client there.
Assuming the corporate network & security will permit.
I assume that there is some kind of firewall? And that it blocks port 22? Are they using a mandatory proxy? I may be able to help you, if you give me more details. Are they using ISA or Squid?
I was speaking in a general sense. I have no problem using SSH or VPN to connect from work to my home network. However, there are many places where such "unauthorized" use is prohibited or blocked. As an example, the public library in my city has free WiFi access for library card holders. It works fine for accessing the web or library catalog, but they block both SSH and OpenVPN, so I cannot connect to my home network from the library.
If you can connect to the web, you can tunnel over http or https. If you can ping to any random host on the web, then you can use icmptx. If you can make dns queries, then you can use nstx.
Regardless of what can technically be done, there's still corporate security policy to worry about. If you have an employer that bans such activity, will you do it? Also, many companies have "locked down" computers, where users cannot add any unauthorized software. They are all too often stuck with Outlook.
If my customer doesn't allow me to use the tools I need for the contract they are paying me to do, bad luck for them. They will still be invoiced. Anyway I will follow every rule that the customer *gives* me in writing, but I'm not going to look up their corporate security that is hidden somewhere deep on their intranet. You know, those documents that everybody *should* have read but nobody knows that they exist. -- Amedee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org