Microsoft Windows 10 and Microsoft Windows Server 2016 no longer include the Hyper-V Integration Services ISO, vmguest.iso.  The rationale behind this change is that the latest supported Windows and Linux operating systems provide their own Hyper-V integration.

 

This means that there is no built-in way to install Hyper-V Integration Services into legacy operating systems such as Windows XP (Windows Embedded POSReady 2009).

 

Fortunately, there is a direct download link mirror to the Hyper-V Integration Services 6.3.9300.16384 ISO, which came from Windows 8.1 / Windows Server 2012 R2.  You can download this file and mount it as a CD in your legacy Hyper-V guest to install Hyper-V Integration Services.

 

 

• Direct from Internet Archive: vmguest.iso
• Direct from Internet Archive Wayback Machine: vmguest.iso

• vmguest.iso, size: 27590656 bytes (27 MiB)
• vmguest.iso, MD5: e36d4976a4fa8b38726670eb332c4fea
• vmguest.iso, SHA1: 415d62038cf28c39af2ca63076a7df91a4524314
• vmguest.iso, SHA256: d1037fd8e788ce8ed0df16ec21f057e74512d5b3d551cc9396c7ae95dccba10f
  

In the past, Deltik's products site, products.deltik.org, provided demos of the products published by Deltik from 2008 to 2011.  Some of these products have serious security or performance flaws that made them unsuitable for demoing on Deltik.

 

As a result, the old products, now collectively called the "Legacy Deltik Products", have been taken off of the demo site and published as an unsupported archive.

 

The Legacy Deltik Products can be copied to any web server running PHP 5, and they should run roughly as they did on Deltik.  Note that some paths were hard-coded and may break on your web server if you aren’t pretending to use the virtual host products.deltik.org.

 

You can find the products on the Legacy Deltik Products GitHub repo and clone them with this command: 

git clone https://github.com/Deltik/products-legacy.git

A .tar.xz archive containing only the products folder can be downloaded directly from GitHub or from Deltik.

 

Either of these commands performs the download and extraction into the current directory:

curl -L 'https://github.com/Deltik/products-legacy/raw/master/products.tar.xz' | tar -xJvf -

curl -L 'https://content.deltik.net/products/legacy/products.tar.xz' | tar -xJvf -

 

The GitHub repo contains a README.md file that explains what's included.

 

Currently, https://products.deltik.org/ just contains a static page explaining what happened to the Legacy Deltik Products.  If I choose to make something of the subdomain, I'll replace it with whatever succeeds the Legacy Deltik Products.

 

The demos ran on the same unprivileged user as the main Deltik website, which means that compromising one of the demos would allow an attacker to take control of Deltik.  I provide an example of a partial exploit in the extended version of this news post.  (I figured that it would be pointless to demonstrate a full exploit, since the demos are no longer running here.)

 

It was also possible to do some denial of service attacks and proxy some attacks through this server.  I present a high-level overview of some attack examples in the extended version of this news post.

The Deltik news feed just got a lot more content.  Having found some old backups of this website, I performed a manual merge of the salvageable news articles and comments from all of Deltik's history dating back to 2008.

 

For historical preservation, I republished these old articles and comments.  Most of the posts don't have a user assigned to them anymore, so they show up as user ID 2, "Legacy User".

 

You're welcome to browse them by going back to the earliest pages,  They're probably not all that relevant anymore, but it could be interesting to see how different things were back then.

Hey, look!

 

Deltik.org is running on HTTPS now, finally.

 

When people ask me about this website and why it looks so lame, I tell them that it's trapped in the past.  Deltik.org looks almost the same as it did in 2008.

 

Well, I'm not changing how this site looks, except for the new lock icon in the address bar.  I've gone through the internal workings of this site and changed many of the deltik.org hyperlinks to use HTTPS.  Not everything on deltik.org is configured properly for HTTPS, though.

 

The only notable thing is that the domain is configured with wildcard subdomains (*.deltik.org), but I didn't buy a wildcard site certificate, which means that wildcard subdomains such as http://csrf.deltik.org/ will only be valid over HTTP, though they do have an invalid HTTPS certificate installed.

 

• deltik.org – Redirects to www.deltik.org
• www.deltik.org – This website
• content.deltik.org – My kind-of content distribution network (CDN) that I would actually turn into a CDN if I hosted sufficiently popular files
• products.deltik.org – I never finished this dumb-looking page showcasing Deltik products.
• my.deltik.org – A stalled/failed project for community-driven material on Deltik
• man.deltik.org – MediaWiki used to be running on here, but I never took care of it, and it got overrun by spam robots.  I haven't bothered to delete this site yet.

Log2Log v1.0.4 has been released, and here is a screenshot showcasing the new format converter:

 

 

(I know my French isn't perfect…)

 

• Ability to convert to Windows Live Messenger chat logs
• A slightly more readable incompatibility description box

• The Pidgin source converter malfunctioned and gave zeroed timestamps due to poor programming practices combined with Qt framework updates.
• The Windows Live Messenger default log path has been corrected.

• Download: https://sourceforge.net/projects/log2log/files/
• Project Site: http://log2log.sourceforge.net/

 

Thank you Jennifer!  Jennifer contacted me requesting a converter from her Pidgin so that she could use them with Windows Live Messenger.

 

To make this possible, I needed to know the formula to generate Microsoft Passport numbers.  Thanks to Harry Parsonage's .NET application (Deltik mirror), this was possible.

 

Windows Live Messenger was discontinued a few years ago, and its usage is disabled by default, but there exists a significant community that wants to keep Windows Live Messenger alive.  At the time of writing, people can use Messenger Reviver to continue using Windows Live Messenger.

 

Though a new version of Log2Log v1.x has been released, it is running on limited support.  New format converters are being created only on demand.

If you browse this site… well, I'm surprised, since the activity on this site is as dead as some of the links on it.

 

In all seriousness, if you browse this site, you might notice some dead links.  Some of them are images.

 

New Links 

One of the things I like the least about the Internet is dead links, and I will begin my part to prevent them.  Starting today, all new content will be hosted in-house at Deltik, especially now that we have much larger server resources than when we first started out on 31 March 2008.  Content may be served by a third-party content distribution network, but it will all originate from right here, at content.deltik.net.

 

The main reason that I'm not replacing links that are currently on the site, especially the dead ones, is that I don't have their original sources.  Many of them might be on some scattered backups that I can't find, or they might have been lost forever (which is difficult to believe on the Internet, isn't it?).  Over time, I intend to replace all current media that I've uploaded with sources hosted here at Deltik.

Announcing…

 

 

 

• Ability to convert from Digsby chat logs
• Ability to convert to Pidgin chat logs

• Update checker is now compatible with the SourceForge web server by sending a user agent.

• Download: https://sourceforge.net/projects/log2log/files/
• Project Site: http://log2log.sourceforge.net/

 

Thank you Steve!  Steve contacted me requesting a converter from his 2200 Digsby logs with AIM, Google Talk, MSN, and Yahoo!, and I delivered.  Though a new version of Log2Log v1.x has been released, it is running on limited support.  New format converters are being created only on demand.

Meebo Messenger is going away, and so is the
Log2Log

We're Still Here
Deltik's top priority project, Log2Log, is still very active. We're working on it as hard as we can and will continue to do so until it's production-ready.


What's Taking So Long?
Don't believe that we're working hard on it? See for yourself!

Creating a chat log converter is by no means easy. Me? I want Log2Log to be released as soon as possible without sacrificing the originally intended enterprise-grade quality. In order to do that, I have to learn C++ and the Qt framework on-the-fly while programming Log2Log.

Log2Log was intended to be released at the end of August 2011.  The development team has underestimated how much work it would take to create it, but don't let that get you down.  I really, really, really want Log2Log ready for people by the end of this month, September 2011.


What Works
Surely we have made some progress in the several weeks of persistent development.  This is the rundown of what works in Log2Log as of 10 September 2011:

• Fully capable of reading files from a directory, feeding them through the format converters, and saving the converted files
• Interface shows what data may be lost in the conversion process (formats don't store the same data)
• Feature to "Check for Updates"

But there are a plethora of things that don't work:

• Most of the planned format converters have not been created yet.

Detailed Priorities
As of 08 September 2011, here are the priorities for development of Log2Log format converters:

1. Pidgin HTML -- Log2Log was originally created on 01 January 2011 with this format in mind.  Pidgin HTML is complicated, and if I can create a good format converter for it, the others can easily fall in place.
2. Meebo (download) -- This was the reason why I wanted to create Log2Log.  The format would be very easy to convert to and from, but there is a major problem to solve: The chat logs must be downloaded from a remote server.  The code for doing this already exists, but originally, I had made it in a different programming language, PHP.  It's now a matter of porting it to the language that Log2Log is now programmed in, C++.
3. Log2Log JSON (standardized export) -- For advanced purposes, I intend to create this format converter.  Theoretically, this should take only minutes to create because it directly exports what Log2Log already does in the background.
4. Trillian -- Trillian stores its chat logs in XML format.  Pidgin HTML is also like XML, so with that established foundation, I should have no problem creating a format converter to and from Trillian.
5. Windows Live Messenger -- By input from an eagerly waiting person, I'll create the Windows Live Messenger format converter.  I looked at the chat log format, which was XML as well.  Since Pidgin HTML will have been completed by the time I start working on this format converter, it should be very easy to read this format.
6. AIM -- Also by request, I intend AIM to be the sixth format converter I make.  AIM chat logs are in HTML, and they resemble Meebo chat logs, but they're somewhat more detailed.  It seems rather easy to create this format converter as well.
7. Skype -- Personally, I also want a Skype format converter.  There is a major frustration, though.  Skype thought that it would be funny to create their own eccentric chat log format.  The format makes absolutely no logical sense at all, but all the data exists.  In order to read it, I have to drop down to a very primitive level and scan the binary data.  I started work on it in PHP, but once again, I have to port it to C++ because Log2Log is now written in C++.

Loguntu
Loguntu has been envisioned, and some planning has been done.  As for a server to host Loguntu on, we are trying to secure one by 04 October 2011.


Thank You

• Igor Cardoso — still sticking with the Log2Log project
• John — for helping us know what to work on next in the development of Log2Log