DyKnow: Difference between revisions
imported>Cov 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…' |
imported>Cov No edit summary |
||
| Line 1: | Line 1: | ||
'''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. | '''DyKnow Vision''' is proprietary classroom software made by Dynamic Knowledge Transfer, LLC and 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= | =Malware Features= | ||
| Line 13: | Line 13: | ||
=Security= | =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. | 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. | ||
If it is preferable for the traffic to remain unencrypted for some time, using [[socat]] as a [[Socat#Cleartext_to_SSL_Tunnel_for_DyKnow|plaintext-to-SSL proxy]] allows the final end of the connection to be encrypted but the middle | |||
=Patents= | |||
DyKnow has been granted three [[w:Software patent|software patents]]. | |||
* [http://www.google.com/patents/about?id=yY94AAAAEBAJ US 7003728] | |||
* [http://www.google.com/patents/about?id=idh_AAAAEBAJ US 7213211] | |||
*[http://www.google.com/patents/about?id=0AC6AAAAEBAJ US 7508354] | |||