Re: access to a socket (raw) is forbidden

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Sam Santiago (ssantiago_at_n0spam-SoftiTechture.com)
Date: 10/18/04

  • Next message: Brad Simon: "Re: access to a socket (raw) is forbidden" 
    Date: Mon, 18 Oct 2004 12:30:37 -0700

    Not sure if you can do it without knowing the password. You could set up a
    "service" account - an account explicitly for your application that has
    limited admin privileges to allow the socket communication but restrict
    other areas.

    Thanks,

    Sam 

    -- 
_______________________________
Sam Santiago
ssantiago@n0spam-SoftiTechture.com
http://www.SoftiTechture.com
_______________________________
"Brad Simon" <bsimon@simondeveloping.com> wrote in message
news:94E6B9DE-9609-4F2D-BCDB-A3CECC65A942@microsoft.com...
> That is a good idea.  The DLL is in C#, it is called from a VB .NET
> application.  How do I set it up to use an administration account, if I
don't
> know the PWD?
>
> "Sam Santiago" wrote:
>
> > What environment/language are you developing in?  With .NET you can
> > potentially set the thread identity:
> >
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemThreadingThreadClassCurrentPrincipalTopic.asp
> >
> > Thanks,
> >
> > Sam
> > _______________________________
> > Sam Santiago
> > ssantiago@n0spam-SoftiTechture.com
> > http://www.SoftiTechture.com
> > _______________________________
> > "Brad Simon" <bsimon@simondeveloping.com> wrote in message
> > news:29BA8697-BC25-4AA0-8725-F4174FBE10E8@microsoft.com...
> > > I have a DLL that pings a host via ICMP and raw sockets.  It works
fine
> > when
> > > I am logged in as an admin, but it does not work for a normal user.  I
get
> > > this error:
> > >
> > > An attempt was made to access a socket in a way forbidden by its
access
> > > permissions
> > >
> > > I have found out that this is by design, and can be fixed by editing
the
> > > registry to stop the security checks on the RAW sockets.  I don't like
> > that,
> > > as it opens up other security risks on that PC.
> > >
> > > I have tried to set the DLL to have FullTrust permissions, but that
does
> > not
> > > seem to be working, either.  If I set up FullTrust properly, should
that
> > > override that particular Permission problem?  I may not have it set up
> > right,
> > > since I have not done anything with setting up security in that manner
> > > before.
> > >
> > > If there is another option, I am all ears, but I need that ping
utility to
> > > work, as it does a speed test to see how fast the connection to a
> > particular
> > > host is.  If there is another way to do a speed test, I am also all
ears.
> > As
> > > long as the same problem does not come up for it as well.
> > >
> > > I look forward to your replies!
> > >
> > > -- 
> > > Thanks,
> > > Brad Simon
> >
> >
> >
  • Next message: Brad Simon: "Re: access to a socket (raw) is forbidden"

    Relevant Pages

    • Re: Raw Sockets in WinXP
      ... Subject: Raw Sockets in WinXP ... How many newbies get a linux distro and start doing everything as root, ... never using a normal account? ...
      (Security-Basics)
    • Re: XP Security
      ... Not to mention XP SP1 also made some changes regarding raw sockets. ... >> Tightening Raw Sockets permissions ... This is more geared towards those who don't use the guest account. ...
      (comp.security.firewalls)