full-disclosure - (no subject)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <OF6C80C500.B565A91D-ON80256EEC.002F56B9-80256EEC.003184EB@Inveresk.com>
From: Michael.Simpson at inveresk.com (Michael Simpson)
Subject: (no subject)

i've worked within medicine in my previous life as an ER doc and guess 
what
there is no formal naming standardisation within it, at least not one that 
there is any sort of agreement over, though people have been trying for 
centuries to sort something out.
some use latin, some use greek, some use anglified terms, others will use 
their own language's interpretations of disease
google helps but the variation between differing nations medical 
terminology can lead to a total breakdown in communication when one relies 
on a written record.
Also, some of the less obvious jargon is derived from the name of the 
company (that owns the patent) that makes the device that's used in the 
treament of the disease.
"we threw a quick austin-moore into Mrs McGinty this morning"
using inpenetrable, rapidly-geographically-changing terminology is part of 
the mechanism used to obfuscate the publically available knowledge that is 
part of the (evil) process of preserving professional autonomy. not a good 
thing for medics to do but tends to be repeated in other industries as 
well
-three letter acronym anyone?




Frank Knobbe <frank@...bbe.us> 
Sent by: full-disclosure-admin@...ts.netsys.com
10/08/2004 01:06

To
Bernardo Quintero <bernardo@...pasec.com>
cc
full-disclosure@...sys.com
Subject
Re: [Full-Disclosure] (no subject)






On Mon, 2004-08-09 at 14:43, Bernardo Quintero wrote:
> BitDefender 7.0/20040809 found [JS.Dword.dropper]
> ClamWin devel-20040727/20040809 found [Trojan.JS.RunMe]
> eTrustAV-Inoc 4641/20040728 found [JScript/IE.VM.Exploit]
> F-Prot 3.15/20040809 found [HTML/ObjData@exp]
> Kaspersky 4.0.2.23/20040809 found nothing
> McAfee 4383/20040804 found [JS/IllWill]
> NOD32v2 1.836/20040809 found [Win32/Bagle.AI]
> Norman 5.70.10/20040806 found [W32/Malware]
> Panda 7.02.00/20040809 found [Fichero Sospechoso]
> Sybari 7.5.1314/20040809 found [JS/IllWill]
> Symantec 8.0/20040809 found nothing
> TrendMicro 7.000/20040809 found [HTML_BAGLE.AC]


Isn't the complete lack of naming standardization in the AV industry
simply amazing? Imagine that were the case in science, particular
medicine...

Makes for a nice game of AV bingo though...

-Frank


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/octet-stream
Size: 193 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040810/150f7290/signature.obj