New Intel Wifi 13.2.0.30 driver

These are from Stationdrivers, not yet released on Intel Website

Download

Works fine on my 1000BGN

 

I have the 1000BGN , the driver works fine , but the pro set utility says it cannot find a compatible adaptor , though the pro set`s diagnostic tests say that wifi adaptor is fine , all tests pass green.

 

I don't use the pro set utility, sorry can't help. Why don't you just use the built in tool in Windows 7?

Proset is the wifi connection utility right?

 

I normally use the windows 7 wifi util , but i thought i would give the pro set utility a go , As i have used it in the past , I have un-installed it now anyway.

 

Intel occasionally posts, then quickly withdraws, drivers from their web site all the time. Whether this is due to a publishing error, discovery of a software problem, or ??? we don't know. Intel also makes test versions of drivers available to users who are working their way through a support case. None of these "now you see them, now you don't" driver sets are suitable for general use and you certainly shouldn't call them 'releases'.

I wouldn't trust any driver downloadable from a third party site that is not also available directly from the manufacturers web site. You have no way of knowing where it originally came from.

 

You can trust StationDrivers. Just because it's not on the Intel website it doesn't mean that the drivers are not from Intel? They are, they're just not officially released yet

 

Prove it. Show me where SD or ltv2go and the others absolutely guarantee the source and validity of their downloads. They don't. In fact, those web sites have good disclaimers absolving them of any responsibility for what YOU choose to download from them.

All you have to go on is hearsay most especially in the case of 'unreleased' drivers.

Some of you happily drive into that pool. Some of us don't.

 

Any driver that is officially signed is trusted because only they possess the encryption key for signing it.
It uses public key encryption only they have the master key and you have the public key.
They don't actually encrypt the driver but just to verify integrity.
And WHQL is definitely trusted.
Personally I only use WHQL Drivers.

 

It's WHQL, what more do you want?

 

whql can be forged. easily. so says msft themselves. driver signing is not the sole way to identify the publisher. download source counts for a lot too.

 

Can you quote the source?
Btw if you try to mod a driver, it immediately becomes Non-WHQL and will display warning during installation.
Public Key haven't been broken AFAIK.

 

It is amazing to me that the same people who pretend to be smart enough to NOT download operating system patches from third-party sources think nothing of blindly downloading device drivers from third-party sources.

As for whql-inspired driver signing, the cert only 'breaks' if someone uses the original cert. Replace the original cert with a forged or custom-issued bogus cert and the package passes 'validation'. it's not that hard to do.

Most people have no idea how to validate the origin of a cert. I have a cert server here that I can use to issue private and public certs as often as I want. It is trivial for anyone to do so.

Blind acceptance of certs, be they for web pages, bogus https ssl connections, or driver/software signing is a prime vector for malware tranmission. It's a dirty little secret in the world of those who issue certs used to validate security and source. msft and rsa both admit this.

you don't have to break public key crypto, just use it to your advantage.

google is your friend, try searching for 'certificate forgery' or 'certificate phishing' and related.

you won't believe it unless you do the research yourself.

 

We're talking about a driver here, why are you so paranoid?

I don't think the driver is going to steal my bank account pass, just because it has not been released on the manufacturer's website

 

Device drivers are just as important to the correct functioning of your system as any other operating system component.

"I don't think....." is often the beginning of Not Good Stuff.

But have it your way. I was pointing out the possible problems and if anyone heeded my advice to avoid third-party driver sites, no harm would come to them.

Your advice, to merrily d/l OS components from third-party enthusiast sites, is the one that is less than optimal.

I'm sure you're right.

 

If I am not wrong the certificate has to match the Windows Root Certificate in the Windows OS just like the signed packages on Linux Package Server so you can't simply create a cert because it will not match the OS root certificate.

Those you meant are probably SSL Webserver certificate.
The problem with Web Certs are there is no ground rule on who to trust but OS Certificates are owned only by the OS distributors.

 

I'm talking about WHQL and you're talking about SSL certs?

 

WHQL depends on certs for validation.

 

Newsposter, these drivers are from HP, but also posted on StationDrivers! Do you think HP is trying to install mallware on your notebook?

 

If the drivers are now available on HP (as of what, two days ago?) why would anyone take the chance of downloading them from a third-party web site?

At the time this thread started, the downloads from hp.com were NOT available. It's kind of skanky for you to come in 9 days later and say that because they are NOW available that it makes a difference.

Your jumping the gun and grabbing drivers from a third-party web site did nothing but add risk to the way you 'manage' your machine. Waiting for the drivers to be available from the manufacturers source is the safe play.

Get your drivers from the direct source and forget their third-party download sites.

 

Just to let you guys know, I tried this driver on my Win7 64bit machine having intel centrino advanced-N 6200 inside.

This driver corrupted something with the windows.
Win7 could not find WLAN card anymore.
I uninstalled it with option "Delete the driver software for this device", and then installed v13.1.1.1 but WLAN card never worked again.

It was very strange as windows did install the driver successfully and there was no problem indicated in the Device Manager, but still in the Network Connection Manager it always said WLAN drivers or hardware problem.

I even tried by deleting all the older versions of WLAN driver and then allow windows to download driver from micrsoft. It did that and installed the driver again successfully, but the card never worked.

So after trying a lot of different things for a few hours I finally put an older image of operating system on my N71JQ and the WLAN works again.
Luckly, I always produce new images of my operating system every 2 months or so.

 

I don't have problems with this driver, sorry to hear you had some problems. Numerous posts on other forums also indicate that the driver is working fine

 

Yes, I also saw that it is working fine for a lot of people.
I don't know why it cuased problems on my Intel 6200.