School without thought - your thoughts

Posted by   Virus Bulletin on   Jun 30, 2003

Your thoughts on the University of Calgary's proposals to teach virus writing in its course on computer viruses and malware.

Recently VB reported on the University of Calgary's plans for a new undergraduate course that will 'focus on developing malicious software such as computer viruses, worms and Trojan horses that are known to wreak havoc to the tune of billions of dollars worldwide on an annual basis'. The following are some of your responses to the report.

 Regarding the article (http://www.virusbtn.com/news/latest_news/calgaryuni.xml), I disagree with your point of view on this. Dr Aycock will probably be forced to stop his course because of sentiment like the content of your article. Nevertheless, it's nice to see that there are still free thinkers. "The AV industry had better brace itself if we are to expect a future in which virus writers are the leaders of tomorrow." Statements like that are very funny, it's basically UTism. Funny because virus writers tend to become the "leaders of tomorrow." And the software engineers, piano tuners, AV analysts, stock brokers etc. I agree with the idea that it's not necessary to write viruses to learn how to protect against them (http://www.avien.org/publicletter.htm). But it's probably the easiest way to learn how to protect against them. It's also a good way to learn about the internals of a given operating system and the hardware of a particular architecture. It's also definitely a good way to inspire creativity and get students involved. The strongest reason for a class like this is mentioned in http://www.cpsc.ucalgary.ca/News/virus_course.html [LINK SINCE REMOVED]. For the most part, antivirus software is reactive (with exceptions like heuristics and integrity checkers). The traditional model of coding a sig scanner for each specific virus fails to anticipate new viruses. Heuristics and integrity checking fail if the virus coder works around them. I don't expect anyone in the antivirus industry to look for novel long term solutions because of the income from the subscription/update model. Scott Cruzen

 If the information is being sent to Microsoft for evaluation purposes, to plug up holes in the system; this class would make some sense. Otherwise, it is only assisting the 'anti-virus sellers' in their money making sales needed to protect the Internet and our systems. JEMeives

What do you think? Send your comments to comments@virusbtn.com

Posted on 30 June 2003 by Virus Bulletin

 Tags

twitter.png
fb.png
linkedin.png
googleplus.png
reddit.png

 

Latest posts:

VB2018 paper: The dark side of WebAssembly

Today, we publish the VB2018 paper by Symantec researchers Aishwarya Lonkar and Siddhesh Chandrayan on the security risks that come with WebAssembly.

The Virus Bulletin conference returns home: VB2019 to take place in London

In 2019, the Virus Bulletin conference is set to return home, with VB2019 taking place in London, UK.

Guest blog: The case for increasing transparency in cybersecurity

In a guest blog post, Kaspersky Lab's Anton Shingarev considers the case for increasing transparency in cybersecurity.

VB2018 preview: Workshops

Workshops make their VB Conference debut during VB2018, giving delegates the opportunity to learn the basics of kernel-level malware analysis, Android reverse-engineering and artificial intelligence.

New article: Through the looking glass: webcam interception and protection in kernel mode

Today we publish a short article by Ronen Slavin and Michael Maltsev, researchers at Reason Software Company, who dive into the video capturing internals on Windows, and explain how this can be used by a malicious actor to steal images recorded by a…

We have placed cookies on your device in order to improve the functionality of this site, as outlined in our cookies policy. However, you may delete and block all cookies from this site and your use of the site will be unaffected. By continuing to browse this site, you are agreeing to Virus Bulletin's use of data as outlined in our privacy policy.