Open main menu

Linux and Unix Users Group at Virginia Teck Wiki β

Changes

DyKnow

2,110 bytes added, 16:59, 25 November 2009
Created page with ''''DyKnow Vision''' is proprietary classroom software used by the College of Engineering at Virginia Tech. It is mostly written in C# but has many native components and canno…'
'''DyKnow Vision''' is proprietary classroom software used by the [[College of Engineering]] at Virginia Tech. It is mostly written in C# but has many native components and cannot be run with [[w:Mono (software)|Mono]]. Attempts to run it under [[w:Wine (software)|Wine]] have been unsuccessful. DyKnow Monitor, which comes bundled with DyKnow Vision, includes malware-style features such as application and URL blocking, remote opening and closing of programs and displays of student screens.

=Malware Features=
Occasionally, professors have enabled the malware features of DyKnow products in class, forcing full-screen mode and spying on students. More specific information regarding this would be informative. In earlier versions of DyKnow, certain key combinations could easily break the forced full-screen mode. Unless students give consent to have their privacy invaded by merely showing up to class and running required software, the malware functionality breaks the [http://www.vt.edu/about/acceptable-use.html Virginia Tech Acceptable Use Policy].

=Running the Proprietary Software=
==Virtual Machines==
DyKnow runs fine in virtualized environments such as [[w:VirtualBox|VirtualBox]]. Using a virtual machine is a nice way to soften the effects of its malware capabilities.

==Making the Installer Skip Dependencies==
The web installer is broken, but if you trick it into skipping dependencies, you can at least get DyKnow installed under Wine. To do so you'll need to run the DyKnow installer with Wine then delete the dependency entries from a temporary folder in <code>c:\windows</code>.

=Security=
In the spring of 2009, the [http://www.security.vt.edu/ IT Security Office] and DyKnow were alerted that the login process was unsafe. Passwords were being sent over the wire as an [[w:MD5|MD5 hash]] with a static [[w:Salt (cryptography)|salt]], allowing [[w:Replay attack|replay attacks]] and [[w:Password cracking|password cracking]] (but not [[w:Rainbow table|precomputation attacks]]). Within a month, users were instructed to enable SSL for transactions and unencrypted access was shut off.
Anonymous user