• Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Sfor

  • Birthday

Profile Information

  • OS
    XP Pro x86
  • Country

Recent Profile Visitors

471 profile views
  1. Well, the IE proxy setting just for https was enough to solve the problem. It was not necesary to add the passtrough entry.
  2. But the IE does not connect to http://www.google.pl/ in such a case. With Proximitron in the middle, the http connection is redirected to https without problems, so there is no "Bad Request" message, then.
  3. It seems the ProxHTTPSProxyMII teamed with The Proximitron can add the TLS 1.2. I was able to confirm it with IE 8. While trying to get the thing working I noticed an interesting option in the The Proximitron version Naoko 4.5. In "config" - "HTTP" section there is "Use SSLeay/OpenSSL to filter secure pages (requires ssleay and libeay23 DLL files)". It seems there is option to filter the HTTPS without ProxHTTPSProxyMII. But, I was unable to provide The Proximitron with the DLL libraries it would be satisfied with. So, perhaps just The Proximitron could do the TLS 1.2 conversion.
  4. Well, I'm unable to install the Chrome 36, as it is always updating itself to 49. So, I can not test how it behaves with TLS. I think the first thing to test is if Chrome is able to work without schannel.dll. There is a chance, the Chrome prior to 37 does have it's own TLS support (without TLS 1.2, however). Without knowing that there is a chance of wrong understanding of what is going on with the Chrome and schannel.dll.
  5. Well, using the site https://www.ssllabs.com/ssltest/viewMyClient.html I found the both Firefox and Chrome are supporting TLS 1.2 with the schannel.dll provided with the XP. So, I strongly doubt the Chrome is using schannel.dll. So, replacing the file to the React OS version should not affect both Chrome and Firefox. On the other hand the ChromeSetup.exe does not work with the React OS schannel.dll. So, the Chrome setup does use the schannel.dll, after all.
  6. Unfortunately the applications I wish to test against TLS 1.2 support are not browsers. They are mostly goverment tax declaration form senders and managers. The goverment tax service will not work with just a browser, as the protocol is not user friendly. I did play a bit with schannel.dll. After replacing it with a file taken from Windows 7, the IE 8 stopped working with https, completely. There were no visible error messages, the IE just did not make any connection. ------------------------------------------------------- I did the same experiment with schannel.dll and mbedtls.dll from ReactOS. The result was almost the same as with Windows 7 schannel.dll file. The difference is, with some sites IE 8 crashes, with most of thei it does not connect. It seems the ReactOS is using mbed TLS 2.3.0 and schannel.dll is just a wrapper for mbedtls.dll. mbed TLS 2.3.0 should support the TLS 1.2. Another question is, if Microsoft added TLS 1.2 support with updates for Windows XP Embedded. If so, it would be logical to use them instead. Another task is testing if a particular application is gaining TLS 1.2 support. To do so it would be necesary to redirect connections to some other server. Well, redirecting to a different IP through DNS is a simple task, but I have no experience with HTTPS servers. I would be good to have a server with an ability to switch between TLS 1.0 and 1.2. On the other hand, perhaps it would be a better choice to use a proxy, instead. While using the original server, to switch on and off TLS 1.0 with the proxy. Yet another idea is to leave Windows TLS support as is, and to use a TLS 1.2 capable proxy to make the connection, instead.
  7. Well, since some sites (like Google Maps for an instance) are not giving all options to Windows XP users, I'm using masking agent with Windows XP and Firefox. So, my Internet activity adds to Windows 7 share. Im a bit curious, how many Windows XP users are masking their user agent strings. The Windows XP share could be bigger than expected, because of that. Recently, I encountered a problem which can significantly decease the Windows XP usefulness. The world wide TLS 1.0 to TLS 1.2 migration can affect many Windows XP based activities. The simple web browsing will be ok thanks to Firefox, because it has own system independent TLS implementation. But most of the Internet based utilities use the system support for TLS.
  8. More and more web sites are turning the TLS 1.0 off. There is no big deal with the web browsing, because the Firefox handles the TLS 1.2 just fine. But, some other applications will be affected. A nice example are the utilities made to send XML based electronic goverment declarations. The Polish goverment servers will turn off TLS 1.0 in the middle of 2017. I strongly doubt the utilities used to send the declarations do have own TLS 1.2 support as the Firefox does. The declarations can not be sent through the browser, so Firefox will not do. Is there a way to check if an application has it's own TLS support? Is there a way to add TLS 1.2 support to Windows XP?
  9. On the affected computer the Security center seems to be working correctly. But the "Change the way Security Center alerts me" link is disabled. How to get this link working? --------------------------- Oh, well. ComboFix did the job.
  10. The network connection status icon (the one with two computers and their screens flashing when the connection is active) is a valuable help, when there are problems with network connection. So, I'm always living it as always visible on my clients computers. In case of a problem, when I'm unable to access a particular computer remotely, I can always ask the user if everything is right with the icon. But, there is a downside. Sometimes users are mistaking the network connection icon with some other, shuting down the network connection by mistake. I'm trying to find out a way to keep the icon displayed, while disabling the possibility of shuting down the network connection with it. Perhaps it could be possible to replace the system icon with some other? Or, perhaps, it is possible to restrict the user rights, so it will be not possible for him to shut down the network connection?
  11. Thank you, very much. I was able to turn the "files with unknown extension" search option on. It was a bit difficult to find it, because the Microsoft article is in English, while my Windows is in Polish. After quite a while I was able to overcome the translation related difficulties. They hid this option well, indeed.
  12. Well. I tried to find log files with a certain keyword in them, but the Windows XP just ignored the files with .B and .BLG extensions. When I did the same in Windows 2000 the files were located, correctly. So, there is quite a difference between the Windows 2000 and XP Find Files function. Is it possible to affect the way Windows XP searches the files? Or, should I rather use a different file search tool?
  13. Well, it works correctly, now. The reason is simple. The files on the server had read only attribute set, while the local copies did not. That's why the symbolic links were working differently, depending on where they were pointing to.
  14. You are right. I did use the Link Shell Extension and the driver mentioned there. There are many pages related to this topic and many of them are not quite precise. What I found so far: - The symbolic links are working in general. The only requirement is the driver and NTFS partition. However it is possible to link to files on a server without driver and without NTFS, as well. For an example I did link to a Windows 2000 share set on FAT32 partition. - the application I'm toying with accepts the symbolic link for one of the files. The file is accessed correctly, as far as I can see. However two other data files are as good as missing. It could be related somehow to the file open procedure. The problematic files are opening correctly in Explorer, but the application does not seem to be able to open them. However, everything works fine, if the symbolic links are pointing to the files located on the same system (other partition). So, the symbolic links to networked shares do not work as intended in some cases.
  15. Well. My investigation shows the Symbolic Links with ability to link through networked systems were added in Windows Vista. Also, it looks like there is a file system filter driver able to add such a feature to Windows XP. I'm trying to speed up network application booting by moving executables to local HDD. To do that I need to copy a directory of the application from the server to local HDD with an exception of a few data files. Some data files are accessed within the same folder the EXE file was run from. So, in order to make this idea a reality it is necesary to make symbolic links on workstations, so the application will seek the databases on local HDD, but the data will be kept on the server. - the hard links within a single NTFS partition will not solve the problem - the directory junction feature will not do the trick - the symbolic links from Windows Vista (and newer) should be able to solve the problem - perhaps there is some other solution I'm not aware of. For an example there was an APPEND command in the DOS. In any case the Path enviroment string does not do the trick.