Re: Error in send, while using IP_HDRINCL
- From: "Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx>
- Date: Wed, 17 Aug 2005 10:38:19 +0200
Hi!
"Eugene Gershnik" <gershnik@xxxxxxxxxxx> wrote in message
news:eoq1PUqoFHA.3984@xxxxxxxxxxxxxxxxxxxxxxx
> Arkady Frenkel wrote:
>> "Eugene Gershnik" <gershnik@xxxxxxxxxxx> wrote in message
>> news:%23SDWavboFHA.3300@xxxxxxxxxxxxxxxxxxxxxxx
>>> Arkady Frenkel wrote:
>>>> They do use drivers , but to install driver you have to be
>>>> administrator and answer for Find new device Device Manager dialog
>>>> in the case your driver not signed ( hard to believe that hacker
>>>> will do all the procedure of WHQL :) )
>>>
>>> And MS could do exactly the same precautions for an app that uses raw
>>> sockets. That is require a privilege normally held by admins only
>>> (or even
>>
>> The only computers which are not admins at home are computers of the
>> family members of IT administrators , they say :"In my family only I
>> can be administrator!" :)
>
> Same holds for the current situation. Most home users I know work as
> admins and happily click Ok on any warning they got.
>
And that is ther problem , because click on Device Manager warning can hurt
that person computer , but playing with raw sockets - others ...
>>> local system only) and popping up a dialog when a raw socket is
>>> requested by an application for the first time.
>>>
>>> Instead they have chosen the easy way (for them) that hurts other
>>> developers.
>>>
>> Before the year and half , when MS guys shows the upcoming changes of
>> SP2 in Redmond I warned them with sentence :"By that you'll cause
>> network students move to linux" , at the end they leave the UDP
>> option at least.
>
> OT: AFAIK all students and researchers are already on Linux. Have you seen
I mean not universities but people wanted to learn the topic
> any interesting Windows network utility or tool in the last few years that
> wasn't ported from Linux?
MS guys stand that it's forbidden for them to use open source apps as
source of inspiration and look at open source code...
Arkady
>
>> Agree with you that it's not the best way and that
>> hurt the white hackers( developers ) , so if the as many as possible
>> of us will write to sdkfdbk@xxxxxxxxxxxxx about that , IMHO, the
>> changes will be done for that.
>
>
> Hmmm. Might be worth a try.
>
> --
> Eugene
> http://www.gershnik.com
>
>
.
- Follow-Ups:
- Re: Error in send, while using IP_HDRINCL
- From: Eugene Gershnik
- Re: Error in send, while using IP_HDRINCL
- From: Alexander Nickolov
- Re: Error in send, while using IP_HDRINCL
- References:
- Re: Error in send, while using IP_HDRINCL
- From: sudesh Sawant
- Re: Error in send, while using IP_HDRINCL
- From: Arkady Frenkel
- Re: Error in send, while using IP_HDRINCL
- From: qfel
- Re: Error in send, while using IP_HDRINCL
- From: Arkady Frenkel
- Re: Error in send, while using IP_HDRINCL
- From: Eugene Gershnik
- Re: Error in send, while using IP_HDRINCL
- From: Arkady Frenkel
- Re: Error in send, while using IP_HDRINCL
- From: Eugene Gershnik
- Re: Error in send, while using IP_HDRINCL
- Prev by Date: Problem accessing CALLINFO_STRING structure in TAPI 3.x
- Next by Date: Re: Error in send, while using IP_HDRINCL
- Previous by thread: Re: Error in send, while using IP_HDRINCL
- Next by thread: Re: Error in send, while using IP_HDRINCL
- Index(es):
Relevant Pages
|