[or-cvs] r18548: {torvm} Update TODO a bit in anticipation of public bundle package. (torvm/trunk)
coderman at seul.org
coderman at seul.org
Sun Feb 15 18:37:01 UTC 2009
Author: coderman
Date: 2009-02-15 13:37:01 -0500 (Sun, 15 Feb 2009)
New Revision: 18548
Modified:
torvm/trunk/TODO
Log:
Update TODO a bit in anticipation of public bundle package.
Modified: torvm/trunk/TODO
===================================================================
--- torvm/trunk/TODO 2009-02-15 17:56:37 UTC (rev 18547)
+++ torvm/trunk/TODO 2009-02-15 18:37:01 UTC (rev 18548)
@@ -1,40 +1,97 @@
-Critical tasks:
- . documentation: convert to more useful TODO format.
- . documentation: integrate Kyle's build documentation.
+ TO-DO list for Tor VM software and packages
- . resolve all placeholder 'TODO' comments in code.
+Legend:
+ - Not done
+ . Partially done
+ o Done
+ ? Deferrable
+ X Deferred
+ * Top priority
+ !! Release critical prerequisite / showstopper
+ (this indication will probably be removed from TODO once a 0.0.x
+ release is finally tagged and packaged on the web site.)
+_______________________________________________________________________
- . integrate iptables / firewall rules with torwall
+!! Integrate Vidalia into Tor VM bundle
+ . Launch Vidalia with new control port password via stdin option and
+ correct configuration to communicate with control port over VM TAP
+ interface.
+ . Complete changes for new MSI based packaging and new Vidalia parts
+ - Add license and other legal information to package contents.
- . clean up dynamic memory handling in win32 controller
- (handle alloc failures and proper free'ing)
+!! Update end user documentation
+ . Screenshots of the installation process using both bundle and
+ network based installers and the portable self extracting
+ executable.
+ . Provide trouble shooting and bug reporting instructions.
+ - Commit documentation to torwww svn.
+ - Add license and other legal information to web pages as needed.
- . complete registry helpers for searching / cleaning registry entries created
- by tap and pcap devices. (this will resolve the issues with adding/removing
- the tap driver multiple times without a reboot)
+ * Update documentation
+ . Update Kyle's build documents at janusvm with new bundle details
+ and commit to Tor VM svn.
+ . Finish rest of this TODO file :)
+ . Add in pending changes, chapters to design document.
- . fix detection of default route when multiple gateways present and route
- metric must be used to distinguish properly.
+ Update upstream package support in build infrastructure
+ - Bypass OpenWRT MD5 package verification entirely with our own
+ download process like the win32 build stage.
+ ? OR(and?) Use Emdebian Crush and signature based verification
+ initial testing indicates this should work without much hassle.
+ ? OR(and?) Track upstream commits in a git repo and move to signed
+ changesets of current and tested versions.
+ . Integrate autotools / autoconf support so build scripts are less
+ completely kludged together.
- . autotools / configure 'ify the kamikaze and win32 builds
+ Update build automation docs and hooks
+ ? Add buildbot support into win32 ISO image so non-full builds are
+ possible easily and requisite perl parts are present.
- . provide some priviledge separation for processes (by user in 2k/xp, fine
- grained on vista/svr2008)
+ Update Tor VM release packages
+ ? Add support for run-as service configuration during install.
+ ? Add support for SteadyState friendly configuration.
+ ? Improve package removal to support real clean uninstall.
+ (removing all installed directories and data, including cached
+ package files and program data)
- . identify saved state per machine so that a portable instance on a pen drive
- does not try to restore settings from a different host to the current system
+ Tor VM kernel networking improvements
+ . Implement optional traffic shaping capabilities for client and
+ server traffic.
+ . Implement tarpit target default until Tor is successfully up and
+ running to avoid cached failures and other annoying side effects
+ of immediate RST.
+ - Collaborate with ioerror on making the iptables rules in torwall
+ compatible with Tor VM (and other implementations) to avoid
+ duplication and oversights where possible.
+ ? Implement ability to configure routes across multiple interfaces
+ for power user or dynamic installations.
- . finish the rest of this list
+ Tor VM controller implementation clean up
+ . Complete registry helpers for searching / cleaning registry
+ entries created by tap and pcap devices.
+ - Fix detection of default route when multiple gateways are present
+ and route metric must be used to distinguish properly.
+ ? Keep a host or guid identifier with the saved network state files
+ to ensure that an unclean exit on one host does not accidentally
+ hose the settings of another installation.
+ Tor VM controller hardening
+ - Provide at least minimal privilege separation for processes by
+ user account.
+ ? Integrate with SteadyState via registry backed configuration and
+ provide deployment configuration scripts.
+ ? Take advantage of fine grained authorization and permissions in
+ Vista, Server 2008, and Windows 7.
+ . Use CryptoAPI to gather entropy in host and pass to VM on command
+ line for use in stronger seeding of first-run kernel random pool.
-Additional tasks:
- . improve display output
- . run as service
- . vidalia integration
- . handle abnormal tap connection changes / failure gracefully
+ General topics requiring further investigation and documentation
+ ? Native 64bit apps and TAP device.
+ ? Custom filtering and/or shaping by port and protocol.
+ ? Multiple process model hardening.
+ ? TorButton sans toggle in bundle.
+ ? PortableFirefox in bundle.
+ ? Multiple VM networking.
+ ? Authenticated VM images.
-
-Nice to have tasks:
- . show icon for tap adapter in dock when connected
-
More information about the tor-commits
mailing list