Re: Routing Morpheus through AOL

From: Patrick Farrell (grimlock@xnet.com)
Date: 01/21/02


From: Patrick Farrell <grimlock@xnet.com>
Date: Sun, 20 Jan 2002 23:35:05 -0600

My faith in peoples ability to screw up is never dissapointed :) One of the
reasons I read this group is to see what new fun little things users come up
with. Build an idiot proof box, and the world will build a better idiot.

I just love users that think corporate networks are their own personal property
and they can do whatever the hell they want.

amputee wrote:
>
> "Patrick Farrell" <grimlock@xnet.com> wrote in message news:3C4A08D8.D5F47C64@xnet.com...
> > Hmmm.. Considering this group is supposed to be for network administrators who
> > are trying to keep you from running Morpheus, I'd be dissapointed if someone
> > actually gave you advice how to thwart them.
>
> Prepare to be disapointed..
>
> <rant>
> Last I checked, the group was called comp.security.firewalls, not comp.security.elitist.nazi.admin.clubhouse.
> As far as I'm concerned, this is NOT a group for network administrators who wish to keep people
> from running Morpheus, but a group for people to openly discuss firewalls and security issues. People
> will figure it out [how to bypass security measures] sooner or later, and guess what, you have no
> solution because you spent all that time thinking that you were fine because you thought no one could
> figure out how to bypass security policies. Since when has the concept of network security, or computer
> security through obscurity ever been accepted, hasn't anyone learned anything from Microsoft's blunders?
> </rant>
>
> Having said that.. if I were in the shoes of the original poster, I would look into some of the various
> tunneling methods available (httptunnel, zebedee, or some type of GRE or VPN implementation).
> Of course you would also need access to an offsite machine to set up said tunneling mechanisms,
> but if you really want to get past these types of restrictions, you'll find a way. I'm not familiar with
> ComSocks, but if it's a data proxy that you can setup on a remote machine, you can probably
> find a way to use it. The underlying concept here is that you need to have access to a remote machine
> (read: machine which is not restricted) from your on-campus connection, on which you can setup
> some sort of relay/proxy/tunneling daemon that will allow you to connect on a port which is not
> restricted by your university firewall, which then will serve as your unrestricted virtual connection to
> the outside world.



Relevant Pages

  • Re: Routing Morpheus through AOL
    ... this is NOT a group for network administrators who wish to keep people ... from running Morpheus, but a group for people to openly discuss firewalls and security issues. ... ComSocks, but if it's a data proxy that you can setup on a remote machine, you can probably ...
    (comp.security.firewalls)
  • Secruity on remote folders
    ... This said, we need to access the security ... Create a new Win32_Trustee ManagementObject from ManagementClass. ... Make sure you're using the scope which points to the remote machine. ... Convert the current Dacl to an array list and add your ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: False-negatives in several Vulnerability Assessment tools
    ... Numerous Vulnerability Assessment tools are available for security ... engineers, pen-testers and network administrators. ...
    (Pen-Test)
  • Re: Remote X over rsh
    ... Currently while in a usual session, ... I'm aware of the security issues of rsh however, ... The usual setup is to have just one "Standard" server. ... You also have to configure the remote machine to accept remote logins. ...
    (comp.os.linux.x)
  • RE: SQLServer cant backup remotely (on Workgroups) unless Administrator?
    ... As you know, when the machines are members of a workgroup, the security ... password) to authenticate to the remote machine. ... supplied by the SQL Server and it must possess the ... this would imply a much stronger security. ...
    (microsoft.public.sqlserver.security)