D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: mzkhadir on January 21, 2010, 06:43:03 PM
-
Does 1.33 have all the fixes of 132NA ?
-
If I understand you correctly: Yes, all fixes already included in 1.32 are also in 1.33. Or do you mean something different?
-
If I understand you correctly: Yes, all fixes already included in 1.32 are also in 1.33. Or do you mean something different?
How would you know this information? I don't remember seeing any readme with 1.33. These are all beta's. These forums are beta's. Do you work for, or have inside info from the people who write the firmware?
The proper response is 1.33 was released on the tail of 1.32. It addressed a security hole recently found in many of dlinks firmware. There were no changes other than the above mentoned fix.
:) :o
-
How would you know this information? I don't remember seeing any readme with 1.33. These are all beta's. These forums are beta's. Do you work for, or have inside info from the people who write the firmware?
The proper response is 1.33 was released on the tail of 1.32. It addressed a security hole recently found in many of dlinks firmware. There were no changes other than the above mentoned fix.
:) :o
You are speculating just as you accussed EddieZ of doing.
-
The proper response is 1.33 was released on the tail of 1.32. It addressed a security hole recently found in many of dlinks firmware. There were no changes other than the above mentoned fix.
:) :o
This is not correct. The 1.33 version is dated : Firmware Version : 1.33NA, 2009/12/22
This is before the HNAP isue was made public.
The EU Firmware Version : 1.31EU, 2010/01/14 was build afterwards to fix HNAP
-
Nope, I am not on the Dlink payroll or in any way linked to Dlink. Makes you wonder, right?
And thank you for telling me what the proper response should be. Any more suggestions how I can express myself in any way? ::)
1.33 does not specifically address the security bug. That's the new 1.31EU beta.
Edit: ...as lizzi555 simultanuously added ;D
-
Nope, I am not on the Dlink payroll or in any way linked to Dlink. Makes you wonder, right?
And thank you for telling me what the proper response should be. Any more suggestions how I can express myself in any way? ::)
1.33 does not specifically address the security bug. That's the new 1.31EU beta.
Edit: ...as lizzi555 simultanuously added ;D
Eddie and Dave, was there a readme or not?
Not... so how would you know? Where are you boys getting your info from?
The same place as me I guess :)
-
There was no changelog with this release.
Sources:
1. Simple logic -> firmware date (see lizzi555's remark)
2. Sources that won't be revealed :-X
-
There was no changelog with this release.
Sources:
1. Simple logic -> firmware date (see lizzi555's remark)
2. Sources that won't be revealed :-X
Sources that won't be revealed.
Eddie you or lizz?
Explain please.
-
Sources that won't be revealed.
Eddie you or lizz?
Explain please.
I cannot speak for Lizz, only for myself.
-
How would you know this information? I don't remember seeing any readme with 1.33. These are all beta's. These forums are beta's. Do you work for, or have inside info from the people who write the firmware?
The proper response is 1.33 was released on the tail of 1.32. It addressed a security hole recently found in many of dlinks firmware. There were no changes other than the above mentoned fix.
:) :o
Actually it specifically addresses performance/stability issues with the unit as EddieZ mentioned. The HNAP security flaw was not mentioned in this firmware.
-
Nope, I am not on the Dlink payroll or in any way linked to Dlink. Makes you wonder, right?
And thank you for telling me what the proper response should be. Any more suggestions how I can express myself in any way? ::)
1.33 does not specifically address the security bug. That's the new 1.31EU beta.
Edit: ...as lizzi555 simultanuously added ;D
It doesn't make me wonder at all.
I've read all of the posts I can handle. It seems everything here is a beta, including these forum posts.
Will there ever be a real release? or will we beta it forever?
I'd love to post the logs from my white 3 legged bug, but until it allows me to connect to the web interface i will have to wait and see. pileing up the 655's...
-
Actually it specifically addresses performance/stability issues with the unit as EddieZ mentioned. The HNAP security flaw was not mentioned in this firmware.
Now, how would Eddie be made aware of this information? And why is dlink posting so many beta's and testing them on people's router's here in the beta forum?
-
Because I told him.
In fact I PM'd the firmware to him before releasing it so I could get feedback on it before I posted it.
Him and several others.
Not that it matters. There will be an official release soon. The reason for the lack of the changelog is there actually isn't one.
The truth is I wasn't supposed to release those codes yet, but I knew how good they were ( thanks to some of the forum users) and pushed it out anyway.
-
Because I told him.
In fact I PM'd the firmware to him before releasing it so I could get feedback on it before I posted it.
He must be special, or have a special relationship with Dlink.
You would think a big company would not send out it's untested firmware to the public first.
That's unheard of in the real world.
Is that why eddie's got attitude?
-
Nope just a normal forums user with the ability to provide useful feedback on the code.
-
Because I told him.
In fact I PM'd the firmware to him before releasing it so I could get feedback on it before I posted it.
Him and several others.
Not that it matters. There will be an official release soon. The reason for the lack of the changelog is there actually isn't one.
The truth is I wasn't supposed to release those codes yet, but I knew how good they were ( thanks to some of the forum users) and pushed it out anyway.
So does Dlink send out it's beta code out to specific non-dlink employees on a regular basis?
Where I work that would be considered a breach of security. I guess not at dlink. Right?
-
Breach of security? LOL
It's a firmware. The firmware file is just as intact as it would be when we post it to dlink.com.
We started a program to try to minimize negative firmware launches through customer feedback. However there has to be some level of competency of the tester for D-Link to glean any useful information. So to do this I selected a few of our more vocal and helpful users to provide feedback. Once I feel that the beta will only help and not hurt the community then I release it as beta.
Now that we've played 20 questions, I'm going to lock this thread as it has reached a nontechnical nature and is becoming of no use to anyone.
-Lycan.