I had used WineTools to install IE6 under WINE 0.9.something (0.9.4, I think). It worked fine to connect to my employer's Citrix server and run Citrix apps that required 128-bit encryption to run SSL connections. Since updating WINE to 0.9.6 (via Apt-get, I run Debian), whenever I try to connect to the Citrix server, I get a message informing me that 128-bit encryption is required and I can't connect. Yet when I check IE6's About IE option, it tells me that 128-bit encryption is installed. Fortunately, the IE5.5 w/ 128-bit encryption I have installed under Win4Lin works just fine. -- David gnome@hawaii.rr.com authenticity, honesty, community
Joachim von Thadden
2006-Jan-26 15:56 UTC
[Wine] 128-bit encryption message since update to 0.9.6
Am Wed, Jan 25, 2006 at 11:06:40PM -1000 schrieb david:> I had used WineTools to install IE6 under WINE 0.9.something (0.9.4, I > think). It worked fine to connect to my employer's Citrix server and run > Citrix apps that required 128-bit encryption to run SSL connections. > Since updating WINE to 0.9.6 (via Apt-get, I run Debian), whenever I try > to connect to the Citrix server, I get a message informing me that > 128-bit encryption is required and I can't connect. Yet when I check > IE6's About IE option, it tells me that 128-bit encryption is installed.At the moment it seems that there are certain drawbacks with WineTools and Wine-0.9.6. As the situation with WineTools is undebuggable for developers I would suggest you either downgrade Wine to the version you had runnig before or move your WineTools .wine away and use plain Wine. In that case you can test whether the error still remains and then make a bug report for Wine. Here are two hints for installing IE6 with plain Wine: http://gentoo-wiki.com/HOWTO_Install_Internet_Explorer_6_SP1 http://appdb.winehq.org/appview.php?versionId=469 Regards Joachim von Thadden -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"
James E. LaBarre
2006-Jan-27 09:40 UTC
[Wine] 128-bit encryption message since update to 0.9.6
>Back to Win4Lin. If dealing with Wine upgrades means trashing your Wine >settings and starting all over from scratch each time, it's just as time >consuming as upgrading a Windows installation ... :-(My solution for testing new builds is to rename .wine to something like hold.wine, (or core_app.wine, yymmdd.wine, etc), then let Wine create a new clean configuration. That way I can move back to my old one. Sometimes I'll tar up a working configuration to save for later testing. Or perhaps I'll tar up the current version and try the new build against what I currently have, then I can restore the prior configuration afterwards.