Tillbaka till svenska Fidonet
English   Information   Debug  
OS2BBS   0/787
OS2DOSBBS   0/580
OS2HW   0/42
OS2INET   0/37
OS2LAN   0/134
OS2PROG   0/36
OS2REXX   0/113
OS2USER-L   207
OS2   0/4786
OSDEBATE   6046/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1123
R20_AMATORRADIO   0/2
R20_BEST_OF_FIDONET   13
R20_CHAT   0/893
R20_DEPP   0/3
R20_DEV   399
R20_ECHO2   1379
R20_ECHOPRES   0/35
R20_ESTAT   0/719
R20_FIDONETPROG...
...RAM.MYPOINT
  0/2
R20_FIDONETPROGRAM   0/22
R20_FIDONET   0/248
R20_FILEFIND   0/24
R20_FILEFOUND   0/22
R20_HIFI   0/3
R20_INFO2   3250
R20_INTERNET   0/12940
R20_INTRESSE   0/60
R20_INTR_KOM   0/99
R20_KANDIDAT.CHAT   42
R20_KANDIDAT   28
R20_KOM_DEV   112
R20_KONTROLL   0/13301
R20_KORSET   0/18
R20_LOKALTRAFIK   0/24
R20_MODERATOR   0/1852
R20_NC   76
R20_NET200   245
R20_NETWORK.OTH...
...ERNETS
  0/13
R20_OPERATIVSYS...
...TEM.LINUX
  0/44
R20_PROGRAMVAROR   0/1
R20_REC2NEC   534
R20_SFOSM   0/341
R20_SF   0/108
R20_SPRAK.ENGLISH   0/1
R20_SQUISH   107
R20_TEST   2
R20_WORST_OF_FIDONET   12
RAR   0/9
RA_MULTI   106
RA_UTIL   0/162
REGCON.EUR   0/2056
REGCON   0/13
SCIENCE   0/1206
SF   0/239
SHAREWARE_SUPPORT   0/5146
SHAREWRE   0/14
SIMPSONS   0/169
STATS_OLD1   0/2539.065
STATS_OLD2   0/2530
STATS_OLD3   0/2395.095
STATS_OLD4   0/1692.25
SURVIVOR   0/495
SYSOPS_CORNER   0/3
SYSOP   0/84
TAGLINES   0/112
TEAMOS2   0/4530
TECH   0/2617
TEST.444   0/105
TRAPDOOR   0/19
TREK   0/755
TUB   0/290
UFO   0/40
UNIX   0/1316
USA_EURLINK   0/102
USR_MODEMS   0/1
VATICAN   0/2740
VIETNAM_VETS   0/14
VIRUS   0/378
VIRUS_INFO   0/201
VISUAL_BASIC   0/473
WHITEHOUSE   0/5187
WIN2000   0/101
WIN32   0/30
WIN95   0/4289
WIN95_OLD1   0/70272
WINDOWS   0/1517
WWB_SYSOP   0/419
WWB_TECH   0/810
ZCC-PUBLIC   0/1
ZEC   4

 
4DOS   0/134
ABORTION   0/7
ALASKA_CHAT   0/506
ALLFIX_FILE   0/1313
ALLFIX_FILE_OLD1   0/7997
ALT_DOS   0/152
AMATEUR_RADIO   0/1039
AMIGASALE   0/14
AMIGA   0/331
AMIGA_INT   0/1
AMIGA_PROG   0/20
AMIGA_SYSOP   0/26
ANIME   0/15
ARGUS   0/924
ASCII_ART   0/340
ASIAN_LINK   0/651
ASTRONOMY   0/417
AUDIO   0/92
AUTOMOBILE_RACING   0/105
BABYLON5   0/17862
BAG   135
BATPOWER   0/361
BBBS.ENGLISH   0/382
BBSLAW   0/109
BBS_ADS   0/5290
BBS_INTERNET   0/507
BIBLE   0/3563
BINKD   0/1119
BINKLEY   0/215
BLUEWAVE   0/2173
CABLE_MODEMS   0/25
CBM   0/46
CDRECORD   0/66
CDROM   0/20
CLASSIC_COMPUTER   0/378
COMICS   0/15
CONSPRCY   0/899
COOKING   33431
COOKING_OLD1   0/24719
COOKING_OLD2   0/40862
COOKING_OLD3   0/37489
COOKING_OLD4   0/35496
COOKING_OLD5   9370
C_ECHO   0/189
C_PLUSPLUS   0/31
DIRTY_DOZEN   0/201
DOORGAMES   0/2065
DOS_INTERNET   0/196
duplikat   6002
ECHOLIST   0/18295
EC_SUPPORT   0/318
ELECTRONICS   0/359
ELEKTRONIK.GER   1534
ENET.LINGUISTIC   0/13
ENET.POLITICS   0/4
ENET.SOFT   0/11701
ENET.SYSOP   33946
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   24159
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12852
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4436
FN_SYSOP   41708
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13615
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   5966/16075
HOLYSMOKE   0/6791
HOT_SITES   0/1
HTMLEDIT   0/71
HUB203   466
HUB_100   264
HUB_400   39
HUMOR   0/29
IC   0/2851
INTERNET   0/424
INTERUSER   0/3
IP_CONNECT   719
JAMNNTPD   0/233
JAMTLAND   0/47
KATTY_KORNER   0/41
LAN   0/16
LINUX-USER   0/19
LINUXHELP   0/1155
LINUX   0/22112
LINUX_BBS   0/957
mail   18.68
mail_fore_ok   249
MENSA   0/341
MODERATOR   0/102
MONTE   0/992
MOSCOW_OKLAHOMA   0/1245
MUFFIN   0/783
MUSIC   0/321
N203_STAT   930
N203_SYSCHAT   313
NET203   321
NET204   69
NET_DEV   0/10
NORD.ADMIN   0/101
NORD.CHAT   0/2572
NORD.FIDONET   189
NORD.HARDWARE   0/28
NORD.KULTUR   0/114
NORD.PROG   0/32
NORD.SOFTWARE   0/88
NORD.TEKNIK   0/58
NORD   0/453
OCCULT_CHAT   0/93
Möte OSDEBATE, 18996 texter
 lista första sista föregående nästa
Text 6033, 298 rader
Skriven 2005-07-14 15:43:54 av Geo (1:379/45)
   Kommentar till text 6028 av Rich (1:379/45)
Ärende: Re: eeye's irresponsible self-serving behavior
======================================================
From: "Geo" <georger@nls.net>

This is a multi-part message in MIME format.

------=_NextPart_000_02E3_01C5888A.D7324EF0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

What I said was "to show eeye's initial stance" and I then go on to = quote
eeye. How can that not make sense to you?

Geo.
  "Rich" <@> wrote in message news:42d69eb8@w3.nls.net...
     Do you not see how silly this is?  To support a claim that eeye is =
not irresponsible you use a statement from eeye that they are not =
irresponsible.  Do you really expect them to say they are culpable?

  Rich

    "Geo" <georger@nls.net> wrote in message news:42d695b7@w3.nls.net...
    No, I'm claiming that they could have taken control of almost every =
windows
    computer that connects to the internet at any time since the =
"information
    anarchy" program started allowing Microsoft to take 188 days to =
patch the
    most critical of exploits. Prior to that their window from
    discovery/publishing to patch was at most 2 weeks. But now with =
standard
    patch times taking roughly half a year there is always a root =
exploit or two
    that they know about that is unpatched. At the momemt there are 4 =
for
    windows and several more for other very common windows programs and =
those
    are just the ones eeye discovered, not the full batch of all known =
root
    level exploits for windows.

    As for Rich's attitude about eeye being irresponsible, this article =
about
    the "information anarchy" program shows eeye's initial stance on =
things
    pretty clearly.

    http://www.securityfocus.com/news/281

    "What's being created here is an information cartel," says Elias =
Levy,
    former moderator of the Bugtraq security mailing list, a standard =
outlet for
    'full disclosure' security information. "It actually benefits =
security
    vendors to have limited vulnerability information, because it makes =
them
    look better in the eyes of their customers," says Levy. (Levy is CTO =
of
    SecurityFocus).

    Under the plan, member companies would share detailed information =
during the
    30-day grace period with law enforcement agencies, infrastructure =
protection
    organizations, and "other communities in which enforceable =
frameworks exist
    to deter onward uncontrolled distribution." The last category would =
allow
    member companies to share details with clients under a =
non-disclosure
    agreement, and to share details with one another. "They're not going =
to ban
    it among themselves," says Levy. "They might be willing to limit the =
public
    access to this information, but I highly doubt that they'll limit it =
among
    each other."

    Marc Maiffret, co-founder of eEye Digital Security, agrees, and =
charges that
    the coalition was formed for the commercial advantage of its =
members, rather
    than the well-being of the Internet.

    "If it becomes hard to release vulnerabilities, that's a good way =
for
    Microsoft to get rid of some embarrassment," says Maiffret.

    Maiffret's company is responsible for discovering some of the most =
serious
    Microsoft security holes in recent years -- vulnerabilities in the =
company's
    IIS web server product that allow attackers to gain remote control =
of the
    system. He says eEye cooperates with vendors, and doesn't release =
advisories
    until a company has had a chance to produce patches for the security =
hole.
    But Maiffret rejects the idea of holding back on technical details, =
and
    warns that the new coalition may alienate independent security =
researchers.

    "People have to do it Microsoft's way or they'll have this group =
telling
    them that they're acting irresponsibly," says Maiffret. "It's going =
to drive
    people into the underground, and could lead to more people breaking =
into
    computers."


    Geo.

    "John Beckett" <FirstnameSurname@compuserve.com.omit> wrote in =
message
    news:nf1cd1pblvdmv4gpcp55g3671etghdujsm@4ax.com...
    > "Rich" <@> wrote in message news:<42d5ef53@w3.nls.net>:
    > > You made a claim that 95% of computers are vulnerable to the =
point that
    eeye could own them.
    >
    > I thought Geo's claim was that if eeye had not been publishing the =
bugs
    > they had found (and just kept them to themselves) over the last =
couple of
    > years, then eeye could have owned 95% of the Windows computers =
connected
    > to the Internet now.
    >
    > Assuming that no one filled this hypothetical vacuum left by eeye =
saying
    > nothing, Geo's claim looks very credible to me (with pointless =
argument
    > about whether it's really 95% or 85% etc).
    >
    > John
    >


------=_NextPart_000_02E3_01C5888A.D7324EF0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1505" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>What I said was "to show eeye's initial =
stance" and=20
I then go on to quote eeye. How can that not make sense to = you?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Geo.</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV>"Rich" &lt;@&gt; wrote in message <A=20
  =
href=3D"news:42d69eb8@w3.nls.net">news:42d69eb8@w3.nls.net</A>...</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Do you not see how silly =
this=20
  is?&nbsp; To support a claim that eeye is not irresponsible you use a=20
  statement from eeye that they are not irresponsible.&nbsp; Do you =
really=20
  expect them to say they are culpable?</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <BLOCKQUOTE=20
  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV>"Geo" &lt;<A =
href=3D"mailto:georger@nls.net">georger@nls.net</A>&gt;=20
    wrote in message <A=20
    =
href=3D"news:42d695b7@w3.nls.net">news:42d695b7@w3.nls.net</A>...</DIV>No=
, I'm=20
    claiming that they could have taken control of almost every=20
    windows<BR>computer that connects to the internet at any time since =
the=20
    "information<BR>anarchy" program started allowing Microsoft to take =
188 days=20
    to patch the<BR>most critical of exploits. Prior to that their =
window=20
    from<BR>discovery/publishing to patch was at most 2 weeks. But now =
with=20
    standard<BR>patch times taking roughly half a year there is always a =
root=20
    exploit or two<BR>that they know about that is unpatched. At the =
momemt=20
    there are 4 for<BR>windows and several more for other very common =
windows=20
    programs and those<BR>are just the ones eeye discovered, not the =
full batch=20
    of all known root<BR>level exploits for windows.<BR><BR>As for =
Rich's=20
    attitude about eeye being irresponsible, this article about<BR>the=20
    "information anarchy" program shows eeye's initial stance on=20
    things<BR>pretty clearly.<BR><BR><A=20
    =
href=3D"http://www.securityfocus.com/news/281">http://www.securityfocus.c=
om/news/281</A><BR><BR>"What's=20
    being created here is an information cartel," says Elias =
Levy,<BR>former=20
    moderator of the Bugtraq security mailing list, a standard outlet=20
    for<BR>'full disclosure' security information. "It actually benefits =

    security<BR>vendors to have limited vulnerability information, =
because it=20
    makes them<BR>look better in the eyes of their customers," says =
Levy. (Levy=20
    is CTO of<BR>SecurityFocus).<BR><BR>Under the plan, member companies =
would=20
    share detailed information during the<BR>30-day grace period with =
law=20
    enforcement agencies, infrastructure protection<BR>organizations, =
and "other=20
    communities in which enforceable frameworks exist<BR>to deter onward =

    uncontrolled distribution." The last category would allow<BR>member=20
    companies to share details with clients under a =
non-disclosure<BR>agreement,=20
    and to share details with one another. "They're not going to =
ban<BR>it among=20
    themselves," says Levy. "They might be willing to limit the =
public<BR>access=20
    to this information, but I highly doubt that they'll limit it =
among<BR>each=20
    other."<BR><BR>Marc Maiffret, co-founder of eEye Digital Security, =
agrees,=20
    and charges that<BR>the coalition was formed for the commercial =
advantage of=20
    its members, rather<BR>than the well-being of the =
Internet.<BR><BR>"If it=20
    becomes hard to release vulnerabilities, that's a good way =
for<BR>Microsoft=20
    to get rid of some embarrassment," says Maiffret.<BR><BR>Maiffret's =
company=20
    is responsible for discovering some of the most serious<BR>Microsoft =

    security holes in recent years -- vulnerabilities in the =
company's<BR>IIS=20
    web server product that allow attackers to gain remote control of=20
    the<BR>system. He says eEye cooperates with vendors, and doesn't =
release=20
    advisories<BR>until a company has had a chance to produce patches =
for the=20
    security hole.<BR>But Maiffret rejects the idea of holding back on =
technical=20
    details, and<BR>warns that the new coalition may alienate =
independent=20
    security researchers.<BR><BR>"People have to do it Microsoft's way =
or=20
    they'll have this group telling<BR>them that they're acting =
irresponsibly,"=20
    says Maiffret. "It's going to drive<BR>people into the underground, =
and=20
    could lead to more people breaking=20
    into<BR>computers."<BR><BR><BR>Geo.<BR><BR>"John Beckett" &lt;<A=20
    =
href=3D"mailto:FirstnameSurname@compuserve.com.omit">FirstnameSurname@com=
puserve.com.omit</A>&gt;=20
    wrote in message<BR><A=20
    =
href=3D"news:nf1cd1pblvdmv4gpcp55g3671etghdujsm@4ax.com">news:nf1cd1pblvd=
mv4gpcp55g3671etghdujsm@4ax.com</A>...<BR>&gt;=20
    "Rich" &lt;@&gt; wrote in message <A=20
    =
href=3D"news:<42d5ef53@w3.nls.net">news:&lt;42d5ef53@w3.nls.net</A>&gt;:<=
BR>&gt;=20
    &gt; You made a claim that 95% of computers are vulnerable to the =
point=20
    that<BR>eeye could own them.<BR>&gt;<BR>&gt; I thought Geo's claim =
was that=20
    if eeye had not been publishing the bugs<BR>&gt; they had found (and =
just=20
    kept them to themselves) over the last couple of<BR>&gt; years, then =
eeye=20
    could have owned 95% of the Windows computers connected<BR>&gt; to =
the=20
    Internet now.<BR>&gt;<BR>&gt; Assuming that no one filled this =
hypothetical=20
    vacuum left by eeye saying<BR>&gt; nothing, Geo's claim looks very =
credible=20
    to me (with pointless argument<BR>&gt; about whether it's really 95% =
or 85%=20
    etc).<BR>&gt;<BR>&gt;=20
John<BR>&gt;<BR><BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_02E3_01C5888A.D7324EF0--

--- BBBS/NT v4.01 Flag-5
 * Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)