Hello again XP (or why I still have a need for it)
-
My code signing certificate expires is less than a month, so it's time once again to jump through the hoops needed to convert the certificate into a .pfx to enable signing from multiple computers. One of the caveats I have learned through the years is that this operation must be done on a < Vista system since MS changed the way they store the keys internally. I'm now installing XP for the first time in 10 years as a VM to accommodate the task. It will be interesting to see how it handles the updates since it's now officially not supported. :)
"Go forth into the source" - Neal Morse
-
My code signing certificate expires is less than a month, so it's time once again to jump through the hoops needed to convert the certificate into a .pfx to enable signing from multiple computers. One of the caveats I have learned through the years is that this operation must be done on a < Vista system since MS changed the way they store the keys internally. I'm now installing XP for the first time in 10 years as a VM to accommodate the task. It will be interesting to see how it handles the updates since it's now officially not supported. :)
"Go forth into the source" - Neal Morse
kmoorevs wrote:
It will be interesting to see how it handles the updates since it's now officially not supported.
They stopped releasing new updates, but I believe you will still get all the updates released through the years. Maybe.
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
-
My code signing certificate expires is less than a month, so it's time once again to jump through the hoops needed to convert the certificate into a .pfx to enable signing from multiple computers. One of the caveats I have learned through the years is that this operation must be done on a < Vista system since MS changed the way they store the keys internally. I'm now installing XP for the first time in 10 years as a VM to accommodate the task. It will be interesting to see how it handles the updates since it's now officially not supported. :)
"Go forth into the source" - Neal Morse
If it's just for a single task or two why bother with the updates unless directly affected for the work required? If worried about attacks do you really need network? Just a common/shared folder will do to get info in/out. Either way once done just save the VM image so next time can jump straight back into it. It's not as the ms fanlemmings believe going to not work (or halt and catch fire) just because ms aren't supporting it - there's xp boxes out there in the real word that run literally for years without ever updating it's not that important. (Most system rescue disks use a xp base, they still work fine don't they.)
-
My code signing certificate expires is less than a month, so it's time once again to jump through the hoops needed to convert the certificate into a .pfx to enable signing from multiple computers. One of the caveats I have learned through the years is that this operation must be done on a < Vista system since MS changed the way they store the keys internally. I'm now installing XP for the first time in 10 years as a VM to accommodate the task. It will be interesting to see how it handles the updates since it's now officially not supported. :)
"Go forth into the source" - Neal Morse
If you use certmgr you can export the private keys with the pfx on windows 7, 10 etc. Unless I misunderstand what you are doing, this is what I have often had to do to move a certificate from one machine to another. These days you need an EV certificate. Have fun! :)
-
My code signing certificate expires is less than a month, so it's time once again to jump through the hoops needed to convert the certificate into a .pfx to enable signing from multiple computers. One of the caveats I have learned through the years is that this operation must be done on a < Vista system since MS changed the way they store the keys internally. I'm now installing XP for the first time in 10 years as a VM to accommodate the task. It will be interesting to see how it handles the updates since it's now officially not supported. :)
"Go forth into the source" - Neal Morse
Does MS still offer an IE6 tester VM for the cursed souls who still have to support it? if so, that'd give you a presumably fully patched XP to fool with.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
If it's just for a single task or two why bother with the updates unless directly affected for the work required? If worried about attacks do you really need network? Just a common/shared folder will do to get info in/out. Either way once done just save the VM image so next time can jump straight back into it. It's not as the ms fanlemmings believe going to not work (or halt and catch fire) just because ms aren't supporting it - there's xp boxes out there in the real word that run literally for years without ever updating it's not that important. (Most system rescue disks use a xp base, they still work fine don't they.)
lopati: loaming wrote:
why bother with the updates unless directly affected for the work required?
Agreed...not really worried about it, just curious. The issue now is that Activation over the internet no longer works and I'm not about to call them. I have a snapshot with 30 days remaining for Activation. I'll do what I need to do before then, and promptly revert it for the next time I might need it...hopefully, this is the last time. :)
"Go forth into the source" - Neal Morse