Re: how these 2 functions may differ?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

thanks for the info... I was thinking of turning the windows forms app I used as a test harness into a little general purpose encryption/decryption utility for the supported .net algorithms... I'm interested in learning about encryption/decryption but I am definitely not experienced at coding for it at this point.

thanks again. I appreciate it.

"Ben Voigt [C++ MVP]" <rbv@xxxxxxxxxxxxx> wrote in message news:eDESlQacJHA.1760@xxxxxxxxxxxxxxxxxxxxxxx
James wrote:
You were already told (correctly) that this code is trash. Why are
you not using the encryption functions built in to Windows?



as for using rc4, its a requirement since what I'm putting together
reads data from an existing system that is already storing the data
in this way, as far as I know there isn't any .net builtin RC4
encryption... as for writting my own translation using more

Windows has RC4 builtin. http://msdn.microsoft.com/en-us/library/aa375549(VS.85).aspx
CALG_RC40x00006801RC4 stream encryption algorithm. This algorithm is supported by the Microsoft Base Cryptographic Provider.

As for .NET, it should have been as simple as calling new CryptoAPITransform and passing the right algid. But that constructor is marked internal. So you'd have to p/invoke the Windows Cryptography functions directly.



appropriate methods, well, what I got from the 4guysfromrolla.com
site works and I don't program enough to do it myself in a timely
manner, and this is the last piece I need to finish this, which is
long overdue. I'm confident its ok for my scenario.

You're right that crypto is not something you want to do yourself. In a similar vein, it's not something you want to trust to whatever poorly written code you found with google.



.

Relevant Pages

  • EFS and System Cryptography Group Policy - Windows XP SP2
    ... Windows XP uses the Data Encryption Standard algorithm with a 56-bit ...
    (microsoft.public.windowsxp.security_admin)
  • You are COMPLETELY correct!
    ... algorithm was DES and assumed 56 bit like I did. ... Windows 200 WS and Server that explain exactly what you say. ... unless the 128-bit encryption pack is applied. ...
    (alt.computer.security)
  • Re: how these 2 functions may differ?
    ... you not using the encryption functions built in to Windows? ... as far as I know there isn't any .net builtin RC4 ... Windows has RC4 builtin. ... it should have been as simple as calling new CryptoAPITransform ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: user does not have acces privileges
    ... to reinstall the windows to do that. ... ownership is the reason of the inaccessibility. ... I'm not an expert but I find out, it is not the encryption but ... "Zorro" wrote: ...
    (microsoft.public.windowsxp.accessibility)
  • Re: user does not have acces privileges
    ... But now at the new files I should have the right EFS key in my computer. ... That means there is something wrong with the ownership settings and that was ... Or it is only matter if the encryption is combined with the ownership change? ... to reinstall the windows to do that. ...
    (microsoft.public.windowsxp.accessibility)