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/4785
OSDEBATE   0/18996
PASCAL   0/490
PERL   0/457
PHP   0/45
POINTS   0/405
POLITICS   0/29554
POL_INC   0/14731
PSION   103
R20_ADMIN   1117
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   2794
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/13064
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/340
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/2055
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/4277
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   28516
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/2018
DOS_INTERNET   0/196
duplikat   6000
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   33806
ENET.TALKS   0/32
ENGLISH_TUTOR   0/2000
EVOLUTION   0/1335
FDECHO   0/217
FDN_ANNOUNCE   0/7068
FIDONEWS   23541
FIDONEWS_OLD1   0/49742
FIDONEWS_OLD2   0/35949
FIDONEWS_OLD3   0/30874
FIDONEWS_OLD4   0/37224
FIDO_SYSOP   12847
FIDO_UTIL   0/180
FILEFIND   0/209
FILEGATE   0/212
FILM   0/18
FNEWS_PUBLISH   4193
FN_SYSOP   41525
FN_SYSOP_OLD1   71952
FTP_FIDO   0/2
FTSC_PUBLIC   0/13586
FUNNY   0/4886
GENEALOGY.EUR   0/71
GET_INFO   105
GOLDED   0/408
HAM   0/16053
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/22012
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   900
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 17347, 140 rader
Skriven 2007-04-10 15:05:06 av Rich (1:379/45)
  Kommentar till text 17345 av mike (1:379/45)
Ärende: Re: /GS
===============
From: "Rich" <@>

This is a multi-part message in MIME format.

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

   Have these folks never spoken with an engineer?  Of course this was =
tested and yes if emitted everywhere it is unacceptable.  In performance = for
sure and I think size too but I don't remember.

   As for a paranoid option as suggested, this is available via =
different means using #pragma strict_gs_check which Michael Howard = describes
at =
http://blogs.msdn.com/michael_howard/archive/2007/04/03/hardening-stack-b=
ased-buffer-overrun-detection-in-vc-2005-sp1.aspx.  It's not as = described as
emitting one with no need.  It uses a different and lower = bar for when one
should be emitted.

   Both with and without the pragma checks are emitted when one is not =
needed and both could miss unusual cases where one could be needed = though
that is less likely with the pragma because it is a more = inclusive test. 
Then again, I think these folks don't understand the = purpose of the checks. 
They are not intended to fix or avoid bugs.  = They are a mitigation for when
bugs do exist to limit the risk due to = the bug.

Rich

  "mike" <mike@barkto.com> wrote in message =
news:e61o13pfa398b42o3shukiet2je1cjoe3b@4ax.com...


  http://www.eweek.com/article2/0,1895,2110151,00.asp



  =3D=3D=3D
  Once again, obviously an engineering trade-off decision was made.
  Perhaps Microsoft was concerned that putting in stack checking =
literally
  everywhere would fatten the program up beyond what was acceptable. Its
  compiler, its source code, it could do the testing to see.

   It seems to me that
  maybe there's a need for a /GSP (for "Paranoid") switch that puts in =
the
  stack check even if there doesn't seem to be a need, unless there's a
  good reason not to (there are cases, described by Microsoft, where the
  stack check code wouldn't be reliable).

  =3D=3D=3D


   /m
------=_NextPart_000_0014_01C77B81.A0376110
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.6000.16397" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Have these folks never =
spoken with an=20
engineer?&nbsp; Of course this was tested and yes if emitted everywhere = it
is=20
unacceptable.&nbsp; In performance for sure and I think size too but I =
don't=20
remember.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; As for a paranoid option =
as suggested,=20
this is available via different means using #pragma strict_gs_check = which=20
Michael Howard describes at <A=20
href=3D"http://blogs.msdn.com/michael_howard/archive/2007/04/03/hardening=
-stack-based-buffer-overrun-detection-in-vc-2005-sp1.aspx">http://blogs.m=
sdn.com/michael_howard/archive/2007/04/03/hardening-stack-based-buffer-ov=
errun-detection-in-vc-2005-sp1.aspx</A>.&nbsp;=20
It's not as described as emitting one with no need.&nbsp; It uses a =
different=20
and lower&nbsp;bar for when one should be emitted.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Both with and without the =
pragma=20
checks are emitted when one is not needed and both could miss unusual =
cases=20
where one could be needed though that is less likely with the pragma = because
it=20
is a more inclusive test.&nbsp; Then again, I think these folks don't =
understand=20
the purpose of the checks.&nbsp; They are not intended to fix or avoid=20
bugs.&nbsp; They are a mitigation for when bugs do exist to limit the = risk
due=20
to the bug.</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>"mike" &lt;<A =
href=3D"mailto:mike@barkto.com">mike@barkto.com</A>&gt; wrote=20
  in message <A=20
  =
href=3D"news:e61o13pfa398b42o3shukiet2je1cjoe3b@4ax.com">news:e61o13pfa39=
8b42o3shukiet2je1cjoe3b@4ax.com</A>...</DIV>
  <DIV><FONT face=3DArial size=3D2></FONT><BR><BR><A=20
  =
href=3D"http://www.eweek.com/article2/0,1895,2110151,00.asp">http://www.e=
week.com/article2/0,1895,2110151,00.asp</A><BR><BR><BR><BR>=3D=3D=3D<BR>O=
nce=20
  again, obviously an engineering trade-off decision was =
made.<BR>Perhaps=20
  Microsoft was concerned that putting in stack checking =
literally<BR>everywhere=20
  would fatten the program up beyond what was acceptable. =
Its<BR>compiler, its=20
  source code, it could do the testing to see.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;It seems to me that<BR>maybe there's a need for a /GSP (for =

  "Paranoid") switch that puts in the<BR>stack check even if there =
doesn't seem=20
  to be a need, unless there's a<BR>good reason not to (there are cases, =

  described by Microsoft, where the<BR>stack check code wouldn't be=20
  reliable).<BR></DIV>
  <DIV>=3D=3D=3D<BR><BR><BR>&nbsp;/m</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0014_01C77B81.A0376110--

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