Vocabulary question regarding Cyberwar

Slashdot: This submission is of the question variety. Is anyone interested to have a discussion about potential cyberwar tactics and strategy? I have hereafter listed all I could think of in the way of vocabulary. I got started on this list just after I read the umpteenth unsubstantive journalistic sensationalist effort on the subject. I will not regard it as an insult if expedience dictates that this discussion be relocated to another community... I'm a little neurotic anyway. Components of a cyber-war: as in any 'war,' sword and shield are determined by application - I mostly go white hat. Most important quality of this information is the VOCABULARY. By naming things, a team can determine if all available concepts are represented. I ginned up what I could without straining and put it in the hands of the author of the blowfish cipher algorithm. I anticipated he would enhance and communicate with open source community. He is unquestionably White hat. DOS attacks cyber break-ins and intrusions - generate IFF mistakes botnets - distributed Denial of service malware - spyware, adware, spam, phishing, virus, browser hijacking DNS attacks - as simple as a power outage web site defacements hijacked websites related tools captcha (recaptcha etc.) http://alipr.com/captcha (imagination) kittenauth distributed processing for RSA key factoring turn off PCs when not in use to impede-defeat botnets I have understood Adobe to be vigilant in hardening PDF against virus introduction techniques. If I am wrong, I expect to make errors from inference on a faulty premise DHCP - IP release looks a better practice than static ip because of ip cloning. I speculate that during a dDoS attack, you could pull the ethernet connection, do an iprelease, and plug it back up and go. Imagine applying this at a site like wikileaks. multiplying browser applications - safari, foxfire, firefox, ie7 as needed, opera, aol actually had a proprietary one for a while. root kit 'catcher.' knoppix-type ReactOS cd that audits processes during CD boot, then compares to HDD boot. M'soft is actually sitting on this, not selling. Alternative patent-copyright effort would be to audit cpu cycles as in unix environment (guaranteed kludge.) I'm scratching around for the book I read... can't remember the title, but a friend might. physical stuff cut non-redundant fibre optics (pulling a Milo - deified i'net historical figure that disconnected sweden back in the day, by pulling ethernet cables at a server farm or some such thing. also referenced in that book.) power outages - both widespread and targeted virus stuff buffer over run null pointer errors jpg, doc, exe, inf, dll (not 100 percent sure how to implement, but dll corruption is certainly problematic enough.) HDOS - hardware denial of service - the process by which a nintendo is rendered a brick. On a PC this can be accomplished by creative BIOS corruption - hashing or encryption are two ways. social engineering tips relevant subject lines vs starlite type randomized ones. I can envision lifting text from literaturary works in a mechanized way, based on parts of speech (for example.) basic tip - I was once alerted to a problem by an un-necessary ding when opening a jpeg. firewalls heuristics MAC address filtering or bluetooth protocol URL blacklists versus URL safelist anti-virus stuff hueristic anti-viruses known virus lists Registry hashing anti-phishing suggestion - instead of opening link from e-mail directly, force user to hover, then supply link in tool-tip type window. dummies will persist in creatively failing, but the mediocrity of ignorance can be undermined. data interdiction packet sniffers man in the middle attacks - white hat will watch the clock with a stop watch - time is the key to becoming aware. ip cloning on static ips. unix was a keylogger heaven individual usb cameras can be remotely activated without permission on occasion knoppix - usb linux. This features a way to mount a drive, extract data and transmit over a live i'net connection, without leaving a footprint. OPERATOR (Knoppix) with exploits built into compile.