You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by TechDud
Thank you for bringing practical perspective.
In light of the following, perhaps only Win2k need critical warning. :lol
http://www.ryanvm.net/forum/viewtopic.p … 8a0#137215
Also wondering if a "real iron" nt5 system could be "cloaked" as a "virty" install to fool some malware. 
Changing hardware detection in the DP_Sound.ini to specify HWID, instead of selecting by HWID's contained within *.inf files. That method didn't always properly distinguish between SUBSYS ID's.
Notepad++ has made these multi-line edits possible for me. Before i only did it manually, like the .Ini for DP_Graphics_B. That took a while, although it was a valuable learning experience.
Looking forward to using devcon to replace dpinst, although that won't be in the next (& probably last nt5) nightly.
It should especially work wonders for the AMD/ATi drivers.
Well, help me to be a "fact-monger" then. Pro-activity is far preferred to reactivity. Murphy's Law is a good source of inspiration towards foresight, it would seem evident. Is there a better stance?
This issue is also relevant to those that use XPMode as well, BTW.
Perhaps we could refer to a statement (by perhaps number one fear-monger :lol):
"Important
As of April 8, 2014, technical support for Windows XP and Windows XP Mode is no longer available, including updates that help protect your PC. This means that if you continue to use Windows XP or use Windows XP Mode on a Windows 7 PC after support ends, your PC might become more vulnerable to security risks and viruses. Therefore, to keep your Windows 7 PC secure after support ends, we recommend that you only use Windows XP Mode if your PC is disconnected from the Internet."
quoted from: http://windows.microsoft.com/en-us/wind … -windows-7
Here are some more aspects:
"I have XP-specific applications that won't run under wine or any later windows, as well as some windows-only applications, so for me an XP VM is an absolute requirement, which I've given some thought to.
You are at risk, but you can bring the risk down to an acceptable level by:
1. Not browsing in the VM - do that in the host, copy files across as required.
2. If there's some bizarre reason why you really must browse in the guest, throw all the browser-based security you can at it (strict noscript etc.) and only for the sites you really have to (and see item 4.).
3. Cutting out all non-essential services from XP (especially network-related ones, but note that networking is used to share folders to the host.
4. Running your VM from a file system that appears to be called immutable in the docs - it's reset to the starting conditions on shutdown. I asked about this here.
5. or running still-supported security software on the guest (it's no use if you can't keep it up-to-date, which you can't if loads from immutable storage).
6. Firewalling the VM on the host (which I haven't done properly yet, so can't go into more detail, but basically close all the ports to start with)."quoted from Apr 30 at 15:43: http://askubuntu.com/questions/458306/v … e-browsing
Here is one possible reason for recommending a linux VM. That is, the very nature of not only the OS, yet some of the malware itself.
"It’s not uncommon for the malware of today to include some type of built-in virtual machine detection."
quoted from: http://blog.malwarebytes.org/intelligen … detection/
"It’s not so much what it can do, rather, it doesn’t want to do anything. Since average PC users don’t run their OS within a VM, it’s suspicious to be running in a virtual environment from the malware’s standpoint, as it drastically increases the likelihood that’s being analyzed and/or reverse engineered. This is something the malware’s creator wants to prevent."
quoted from: http://blog.malwarebytes.org/intelligen … mment-5861
Of course, that doesn't preclude infection, just further aberrant behavior for the most part.
Virtual machine hosts can be vulnerable, even linux hosts.
"A successful attack from Windows users will be as follows ;
* You installed wine application in ubuntu
* you forget to configure UFW (the firewall)
* you unintentionally clicked on a malware link from your win xp virtual box
* you opened ports and didn't secure them
. In your case, you are going to install WINDOWS XP in Virtual box, and VBox will create a disk image which will be impossible for users to get outside the disk image and mess with your Ubuntu, however, if you have wine in your ubuntu, and wrongly clicked a malware link from your Win XP virtual box, that will lead the attacker to your ubuntu and execute commands and harm your computer."quoted from Jan 9 at 20:21: http://askubuntu.com/questions/403079/i … for-ubuntu
Apologies for not expanding upon security in VMWare. Am hoping more people will offer insight.
Then again, there's the whole current flawed trust model.
"Essentially, at some point a decision was made to anchor trust in an organization like Comodo, and now we’re locked into trusting them — forever."
quoted from: http://www.thoughtcrime.org/blog/ssl-an … henticity/
"Of 3.45 million real-world connections made to Facebook servers using the transport layer security (TLS) or secure sockets layer protocols, 6,845, or about 0.2 percent of them, were established using forged certificates. The vast majority of unauthorized credentials were presented to computers running antivirus programs from companies including Bitdefender, Eset, and others. Commercial firewall and network security appliances were the second most common source of forged certificates."
quoted from: http://arstechnica.com/security/2014/05 … tificates/
Few do think of updating those RootCerts & getting the current revocation update. The RootCerts package is only an optional update for the masses, and curiously hasn't seen an update since before the HeartBleed revelation.
How long ago did schannel.dll (TLS/SSL) see an update?
The latest i see for w2k is v5.1.2195.6960 from Apr 8, 2005. That must be vulnerable in so many ways.
The latest for xp is v5.1.2600.6370 from Mar 28, 2013, so that should be OK for at least a little while. That seems to indicate pro-activity on MS's part.
2k3's latest is v5.2.3790.5014 from June 4, 2012. Curious that the supported OS has the older implementation, unless i have miscalculated the latest update for 2k3. (25000 Servers a day need 2k3 updated before July of next year???)
Is that the revision of schannel.dll in XPMode?
"Secure channel (aka SChannel) - Introduced in Windows 2000 and updated in Windows Vista to support stronger AES encryption and ECC [6] This provider uses SSL/TLS records to encrypt data payloads. (schannel.dll)"
quoted from: url=https://en.wikipedia.org/wiki/Secur … _Interface
XP lacks support for stronger AES encryption and ECC? I think the availability of something like P-521 or greater is something that should be available in today's day & age (especially in light of recent WPA2 vulnerabilities - recommendations of usage of greater complexity encryption at minimum.
There is an update for 2k3 to support AES256-SHA at least. https://support.microsoft.com/kb/948963
Perhaps one approach would be to disable support for the lowest and least secure ciphers. See http://support.microsoft.com/kb/245030. Those could go into the changelog.
Anyway, how should an advisory read (perhaps in addition to "* use at your own risk *" in networking packs) ?
"Avoid networking entirely on Win2000 unless it is a private wired and isolated network. XP/2k3 will eventually and not necessarily in succession receive the same recommendation."???
Check the changelogs and see if you disagree moderately to vehemently against any statement within, please.
Integrating official updates into one's source does seem like another proactive approach. Of course, that is a whole other kettle of fish.
There are some recent KB updates for xp that so-far seemingly have improved usb stability/performance from textmode on.
Wouldn't integrating KB network files & related inbuilt protocols/drivers, etc. offer one less flaws and greater stability than what is stock for XPMode? (What is stock in a XPMode distro? I don't know.)
Ooo, XP sees another update, one for SilverLight --> http://www.microsoft.com/en-us/download … x?id=42250
Just as well --> http://arstechnica.com/security/2014/05 … -the-rise/
OK; thanks for reminding me about the first post. Will decorate the changelogs and get that up. No wonder that one seems so popular. d'oh. :u
The 3rd-party MassStorage packs are now depricated as they have been unified in this pack.
2k bug AKA "7 sisters" - satisfied.
DP_MassStorage_wnt5_x86-32_1405176.7z - 10.9 MB 6E6227920907D3DF53579FFC791DE79546BA790D 
updated.
DP_LAN_wnt5_x86-32_1405191.7z - 11.1 MB 2AF77C3435780C5904A086924DC7229363C39F23
edit: link removed; updated below
updated with an import from chipset for NEC GPRS.
DP_Phone-Mobile_wnt5_x86-32_1405111.7z - 15.4 MB 2AF766C3A2399DC2B25342B9CFCF30268BA43698
Updated DisplayLink & FrescoLogic drivers. DL now includes the apps within the driver package, like it does for the legacy 2k version.
for post-Windows Setup utilizing SAD3:
DP_Graphics_USB_wnt5_x86-32_1405191.7z - 30.11 MB D0EFE43A724837F08F52EF48F8BA2F7461666D82
edit: link removed - updated or reposted below.
Updated Fresco Logic USB3:
DP_Chipset_wnt5_x86-32_1405191.7z - 33.28 MB 00C8660DC38DC00EFDEDD9EC8A69815FBE332BD7
edit: link removed - updated near topic end
Jetway or Foxconn released that some months back. It's in DP_Sound_A_wnt5_x86-32_1403071.
Thank you for the "heads up" just the same; i appreciate it as such.
Wednesday is the latest ETA for a tested pack including a fix for the "7 sisters" win2k setuperr.log fix. (I call it that despite the fact that only six errors persist on install because in addition to the six errors, mraid35x.sys is similarly affected though "disabled".)
An update to Acheron's "3 amigos" fix is that now three errors are located in the System section in Event Viewer. Those complain of the sudden removal of the mvmmxx libraries, so an entry in the "Known Issues" will need be added to the changelog.
At least all entries are completely gone now (except in BartPE/UBCD4Win by design).
Noting that 2003 Storport v5.2.3790.4485 is available for Server 2003 SP2 here --> http://support.microsoft.com/?kbid=957910
For SP1, there is http://support.microsoft.com/?kbid=943545
Curious that update_SP2QFE.inf includes the line "SP_TITLE_XP = "Hotfix for Windows XP (KB957910)""
" Version: 12.9.0.1001" ... "BartPE complains iaStorA.sys as corrupt. It's not compatible to 2003 storport.sys or another reason."
"I don't like to go this way. As long as there are XP compatible drivers, use XP drivers."
Indeed. That was a cool exploration of limits though!
Oops, i neglected to remember this yesterday.
Here it is! --> DP_TVcard_x64_908
Updated with Acheron's modified Marvell_Cleanup.cmd from this post, and changes from this post above (, et cetera?).
It hasn't been tested. This is just an interim Nightly.
A tested newer pack should be available before the end of next week.
DP_MassStorage_wnt5_x86-32_1404011.7z - 10.73 MB 778756E74BCB91192D20B6CD7A42878710BB97C4
* - edit: link removed - updated near last post in this topic
Note that the DP_MassStorage_IntelIDE or pciIDE pack is still used for this Nightly, as described in this post. They will be deprecated in the next Nightly, as the MassStorage pack is once-again unified.
for DriverPacks folder:
DP_Graphics_A_wnt5_x86-32_1401181.7z - 117.45 MB BB24C55735A704701862DE1B00A9E9AD6C006D69
DP_Graphics_B_wnt5_x86-32_1404281.7z - 224.38 MB CF3BF5CA5B42272E8C68C5F8366CC5FB6470CA2E
DP_Graphics_C_wnt5_x86-32_1403071.7z - 172.07 MB 2c0b735b80db3c105c39618efbd5add660076043
for 3rd party DriverPacks folder:
DP_Graphics_ATi_Runtimes_wnt5_x86-32_1310151.7z - 21.0 MB 81b4fcc8e3d2f112b780fc82b38377bc0a1314ba*
DP_Graphics_ATi-Hydravision_wnt5_x86-32_1401181.7z - 12.71 MB 11506C801884F6F8BF4DC9EC4AEDF456A04497F2
DP_Graphics_ATi-Legacy_wnt5_x86-32_1312081.7z - 118.71 MB a8d189246d1b0d48dd3c0ce7e1785629b54089d2
DP_Graphics_ATi_OpenCL-vc2k10_wnt5_x86-32_1312081.7z - 10.39 MB 4cd10c4ac8ff83995b759584afb9afb8e1d97d6b
DP_Graphics_ATi-TV_wnt5_x86-32_1310291.7z - 8.45 MB e40bba47ecd213387f8fe6e71825ae78b8ebccd7
DP_Graphics_Intel_Runtimes_wnt5_x86-32_1312071.7z - 34.32 MB 860b02399667d7eb81a18d2197e064723118c275
DP_Graphics_Languages_wnt5_x86-32_1403011.7z - 78.58 MB 2d1c7df2b00e84df7608ebcb3689a2fee7acae1f
DP_Graphics_nVidia_GFxp-upd-NET4_wnt5_x86-32_1402251.7z - 101.08 MB 894f16206c6e5677bd410d4e05dd5b43537edf13
DP_Graphics_PhysX_wnt5_x86-32_1403281.7z - 38.23 MB 26A81D581BD7DA6322864E16C836C2DD6657B9BF
DP_Graphics_PhysX-Legacy_wnt5_x86-32_1310271.7z - 18.5 MB 7e5df14e2c44335ed3a60e5591ea68f07175b730
for post-Windows Setup utilizing SAD3:
DP_Graphics_USB_wnt5_x86-32_1401181.7z - 23.93 MB CDC65794CB122CE00026F8E4959F59B39B8FC5E1
* (some packs are updated in replies below)
edit: links removed - updated or reposted below.
* Note: DP_Graphics_External_wnt5_x86-32 has been renamed to DP_Graphics_USB_wnt5_x86-32
Test Archive (not a DriverPack, yet unofficially useful for non-ATi-AMD OpenCL-CPU - SSE2.x{min}):
Ati-AMD_OpenCL_Test.7z - 85.24MB 9b7c6808816f9a4329becfe57d323a5741680376
updated (2013-11-16)
Haswell Graphics/Sound Test pack:
4thGenHaswell_Graphics-HDAudio_NT5_TestPack.7z - 14.65 MB 6F3E80C2C015ECB6E2AE70A57B028168F0441879
Noting that the latest SAD3 has the old DevPath.exe, yet doesn't seem to work with Win2k nor ever has (unless failure was my fault somehow - a possibility for sure). Would updating DevPath.exe and removing Win2k from the OS Support List be advantageous?
The missing link may be the HDCP key.
Perhaps Intel has not licensed it for that particular hardware?
If so, that would negate any possibility of any included modded driver.
Updated.
DP_SmartCard_wnt5_x86-32_1403281.7z - 51.61 MB 7F2CD580ADB9EF15907FECA363E8DFE718B95B61
Recommended for post-Windows Setup utilizing SAD3.
Probably no need to integrate via DPs_BASE.
Updated.
DP_Biometric_wnt5_x86-32_1403281.7z - 15.33 MB 42CE98DB8534B86A539CCEE10F17514F68728D09
Recommended for post-Windows Setup utilizing SAD3.
Probably no need to integrate via DPs_BASE.
Updated.
DP_WebCam_wnt5_x86-32_1403281.7z - 82.19 MB BCD187782FB85BC3D11796E2A56DEABA00155CCB
*edit: link removed - updated below
Recommended for post-Windows Setup utilizing SAD3.
Do not integrate via DPs_BASE.
Name changed to DP_Phone-Mobile_wnt5_x86-32. Folder path is now ..\D\3\PhM to segregate it from the DP_Printers_wnt5 packs from so, so long ago.
Inter-brand conflicts are documented.
DP_Phone-Mobile_wnt5_x86-32_1405041.7z - 15.39 MB 40B524C2B5E5FCF3CF14E74483D3E229B568F0DD
* edit: link removed - updated below
Recommended for post-Windows Setup utilizing SAD3.
Do not integrate via DPs_BASE.
From changelog:
"Windows XP SP3 (incl. TabletPC & MCE - except Embedded) Extended Support by MS ended April 2014 (network connection ill-advised)"
...
"*** USE ANY OF THESE DRIVERS ONLY AT YOUR OWN RISK ***"
...
"Potential Inter-Brand Conflicts:
Manual-Device installation recommended for following HWIDs:
USB\VID_0BB4&PID_0C01 (HTC Dream), USB\VID_0E8D&PID_0003 (MediaTek Generic device),
USB\VID_18D1&PID_DDDD (Google Android Sooner)
Warning:
-Consult your Wireless Cellular Service Provider for Tethering data rates,
roaming & other charges before use (if applicable)"
Updated.
DP_Modem_wnt5_x86-32_1403111.7z - 32.11 MB BC0ABDDA1E50A2DF25044A72E2EFE1037FF662F1
Should network connections only be advised via Virtual environments for 2000 & XP?
Updated, including contents/changelogs/previous.
Utilities are now installed by HWID, not via .inf as that method was buggy.
DP_WLAN_wnt5_x86-32_1405041.7z - 30.03 MB 266FB948F921167772256F8FAB18E669EC9BD948
edit: link removed - updated below
DP_WLANutils_wnt5_x86-32_1404141.7z - 214.71 MB BCA18ACAFE26B02368D7BF6EF740C3225EB2771A
Do read the changelog, it has important information not quoted in this reply below.
From the changelog:
"Windows XP SP3 (incl. TabletPC & MCE - except Embedded) Extended Support by MS ended April 2014 (network connection ill-advised)"
...
"-WEP, WPA, WPS & WPA2 have been cracked
see: http://phys.org/news170679777.html, http://phys.org/news/2011-12-us-cert-wi … brute.html
& http://phys.org/news/2014-03-wpa2-wireless.html*** USE ANY OF THESE DRIVERS ONLY AT YOUR OWN RISK ***
-Reconsider a wired connection if possible (proper cabling can be used instead of replaceable antennae)"
D'oh. Think the following need be added (thoughts, anybody?):
"-Use a LAN connection instead wherever possible via Virtual environments.
Also note that both Broadcom & Intel driver sets list OpenSSL in their list of copyrights dated 2006 & 2008.
Are any of the HeartBleed affected versions of OpenSSL included in those or any other driver sets including DP_LAN?
I don't know. That is on reason why i have placed so many disclaimers in the changelog.
Check back in an hour, Outbreaker.
Yes. Also, [Nightlies] updated.
DriverPacks.net Forum » Posts by TechDud
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.072 seconds, 5 queries executed ]