It took six months... but there it is.
|Posted by White Hat (whitehat) on Jul 01 2011|
|News >> JottiQ|
Six long months... I bet some people expected a new version to never appear again, to see JottiQ discarded amongst the piles of software that is released, supported for a few days, and then forgotten about. (I don't blame you.) But alas, I disappoint myself and managed to barely hold myself to the self-imposed July 1st release date for JottiQ v1.1.0.
My special thanks go out to the testers of the 1.0.9 beta releases; I have put you folks through a bit of pain and suffering.
The changelog is as follows:
v1.1.0 (2011-07-01) Six months after the official release, it is time for a well-deserved update. Sadly, there isn't much one can improve in a tool with a simple purpose. However, I hope this new version will entertain. Added: Forks support. Also known as 'Alternative Data Streams', these are a well-hidden feature of the NTFS filesystem which provide for equally well-hidden pseudo-files attached to existing files. Most programs are unable to read them, no less act on them - which makes this a feature that truly improves Jotti's malware scan. Added: Proxy server support. Added: Connectivity test for troubleshooting issues. Some beta-testers for this version had problems with proxy server support, but it will hopefully prove useful for all parties. Added: A builtin 'whitelist' for forks. The feature is sometimes used for legitimate reasons, and one of those affects nearly every file downloaded. The whitelist exists for speeding up processing only; security-minded (distrusting?) individuals are free to enable the option that forces these whitelisted forks to appear in the queue. Added: A 'whitelist fork by name' option. If the precise comparisons on a possibly whitelisted fork prove troublesome, this enables one to consider the fork safe by proxy of its name. This feature as a work- around for 'Zone.Identifier' forks encoded in different formats than I have been able to test with - so if one finds a 'Zone.Identifier' fork that is not whitelisted, I request that this forks is saved to a file and sent to me at: jottiq-whitelist (at) whitehat.dcmembers.com so I may inspect it and if is found safe, add it to the whitelist in the next version. TL;DR? Don't enable unless you know you need it. Added: The queue context menu now offers an Actions sub-menu. These contain actions that affect the selected objects (files and/or forks) in the queue physically. There are currently two items in this menu: - Delete Object(s): This either deletes the selected file(s) permanently, or it removes the selected fork(s) from the file. Do note that deleting a file also deletes its forks, but that deleting a fork on a file leaves the latter intact. I remain of the opinion that JottiQ is an investigative tool rather than a cleaner, but... the peoples wishes are clear and forks are hard to delete, so deleting files is a logical consequence. - Save Fork As: This saves the contents of a fork to a file. This does not work for ordinary files as it would be a mere 'Copy' operation that may or may not bring expectations along with it; instead it is to be used as an inspection utility for a resource otherwise difficult to examine. Added: An 'Add file(s)' feature is now available in the toolbar. It completely slipped my attention in the 1.0.x versions, for which my apologies. Rather late than never. :) Removed: The 'Add Running Processes' functionality is no longer present. It was determined to be an inappropriate feature that only delivered half work, and to boot the reason why Jotti's malware scan suffers such ungodly waiting times during the waking hours of the western world ever since JottiQ's release. Fixed: No more crash when down-sizing the amount of worker-threads. Fixed: Legibility of items on right pane could suffer in certain colour configurations; now it uses proper system colours where applicable. Fixed: Zero-byte items were not being removed by the manual nor automatic 'Remove safe items' features. Fixed: Deleting items from the queue while it was being processed no longer makes the worker-thread go M.I.A. until it finishes its work off the screen; it now terminates and moves on to the next item in the list as soon as possible. Changed: Uploading should be a little bit more efficient now. Changed: Fancy progress bars that show upload progress are now in place as opposed a boring textual description. Changed: Redesigned the Settings window with clearly named sections and recognizable icons in order to make JottiQ configuration more accessible. Changed: The instruction text in the main screen no longer suggests one to 'start processing' when processing is already enabled.Back