Safer-Networking Forums - View Single Post

**PepiMK** · 2006-12-24, 22:25

Well, I guess the TeaTimer history is really a bad one. Many parts of it can be read on our website under News, and around here. It really wasn't as simple as a patch of a few bytes; in times of codesigned files, you have to replace the whole file. Combined with the bad availability of update servers (that was before we had 7 of our own, updated hardware, reduces includes size etc.)...

And it wasn't just something small to patch - actually the error multiplied with every compile due to a huge bug in our development environment - and lots of trouble with its manufacturer - which eventually lead us to change all our code to be independent of that environment (Delphi - and everyone who has developed using Delphi will probably agree that 2005 was nearly unusable).

And last the Symantec situation, where a change to the TeaTimer was part of a possible solution, which was stalled by S. for many months. And that's just the tip of the iceberg - every month we've got to fight with some AV company over a F/P. They're exagerating their heuristics that much that every second file we do not even have released is already detected as something bad. I have two new updated files available, but can't release them currently since three AV companies do detect them as something bad

I guess in your production days, you didn't have to deal with that much "politics"

Anyway, the TeaTimer + AdvCheck update would've already turned public if it wouldn't have been for the xmas factor. I hope we'll have someone around between xmas and new year to test the final installer from inside the app then

2006-12-24, 22:25	#10
PepiMK Member of Team Spybot Join Date: Oct 2005 Location: Planet Earth Posts: 3,156 Blog Entries: 15 Rated LASSHes: 9,186	Well, I guess the TeaTimer history is really a bad one. Many parts of it can be read on our website under News, and around here. It really wasn't as simple as a patch of a few bytes; in times of codesigned files, you have to replace the whole file. Combined with the bad availability of update servers (that was before we had 7 of our own, updated hardware, reduces includes size etc.)... And it wasn't just something small to patch - actually the error multiplied with every compile due to a huge bug in our development environment - and lots of trouble with its manufacturer - which eventually lead us to change all our code to be independent of that environment (Delphi - and everyone who has developed using Delphi will probably agree that 2005 was nearly unusable). And last the Symantec situation, where a change to the TeaTimer was part of a possible solution, which was stalled by S. for many months. And that's just the tip of the iceberg - every month we've got to fight with some AV company over a F/P. They're exagerating their heuristics that much that every second file we do not even have released is already detected as something bad. I have two new updated files available, but can't release them currently since three AV companies do detect them as something bad I guess in your production days, you didn't have to deal with that much "politics" Anyway, the TeaTimer + AdvCheck update would've already turned public if it wouldn't have been for the xmas factor. I hope we'll have someone around between xmas and new year to test the final installer from inside the app then __________________ Just remember, love is life, and hate is living death. Treat your life for what it's worth, and live for every breath (Black Sabbath: A National Acrobat)