Start, Programs, Visual Studio.NET 2003, Visual Studio Tools, Visual
Studio.NET 2003 Command Prompt
Its a "Dos Box" with the environment variables/paths setup to run the VS
tools.
Mark wrote:
> I am using MS Visual Studio 2003, and am trying to compile OpenSSL
> 0.9.7g. I am following the instru
>From the looks of it you are missing some include files. Search the
source for where those symbols are defined. Get those include files
into your project.
BTW, why not just link to the libs? You could even link statically.
Sean
Francois PIETTE wrote:
> Am i the only one still using MSVC work
I have an app that communicates over the Internet. I'm using the
libeay32.dll for encryption. As we all know from WEP, using encryption
doesn't mean its secure. Can you take a min. at look at how I've
implemented this and tell me if its secure? Thanks!
The user has a fixed 8 character password
Steve,
>
> Salt shouldn't be predictable so using a fixed string isn't an option but it
> isn't secret.
>
I'm using rand_bytes() to create the salt.
>
>>IV. I should really use an IV with some modes. Again, its random
>>bytes, but it doesn't have to be secret. I will also have to transmit
Steve,
>
>>Additionally you seem to be using an unsalted key derivation algorithm with a
>>stream cipher (RC4). If passwords are reused then I hope you aren't sending
>>anything sensitive that way because that is an insecure combination.
>>
>
Additional Questions:
SALT isn't secret, correct?
ty. Especially if you have
control over the environments.
I'm sure some long-time users can discuss the compatibility details, but
that's my own personal feeling about using different versions together...
Sean
>
> Regards,
> Ahmad.
>
>> From: Sean Covel <[EM
Can't you just include libeay32.lib and ssleay32.lib in your project as
additional libraries? The you just need to add the path to those libs
and you're done.
I looked at the project on that site and its old, and all it does is
compile the libraries in the VC++ GUI, instead of using the nice scri
Steve,
Dr. Stephen Henson wrote:
[snip]
>>Here are the relevant chunks for code. I'm trying to give enough code
>>without over-burdening you. If you need more, let me know.
>>
>
> [snip]
>
> Here's one problem:
>
>
>>EVP_CIPHER_CTX_set_key_length(&Dctx, 128);
>
>
> the length para
Windows 2003 Server, SP1. List of Crypto Providers:
Listing Provider 'Default' 1
Algorithm Name Default Key len Min lenMax len
RC2 128 40 128
RC4 128 40 128
DES 56 56 56
3
48, BAD!!! If I use 48 or below, it doesn't work.
Encrypting with EVP_CipherUpdate APPEARS to be working.
Decryption with EVP_CipherUpdate returns 1, meaning success, but the
output is not decrypted, its just further garbled.
My plugin application has LOTS of small chunks, and a few larg
Now that I've updated to the latest OpenSSL (7g) I've got a question:
I implemented some RC4 functionality using the low-level rc4 functions.(
RC4_Set_Key, RC4), and its working fine.
The OpenSSL documentation recommends using the EVP_* functions instead
of the lower level functions. It seems li
Steve,
Dr. Stephen Henson wrote:
>>I was able to build 0.9.7f for Win32 successfully.
>>
>>Downloaded and tried to build 0.9.7g, and its a no-go.
>>
>>Is there a working mak file for Win32 for 0.9.7g?
>>
>
> Compiles with no problems here. I'm assuming you are using VC++ since you
> mention ntdll
Hi! New to the list.
I was able to build 0.9.7f for Win32 successfully.
Downloaded and tried to build 0.9.7g, and its a no-go.
First problem, there are a bunch of \\ in the ntdll.mak file, like
$(INCL_D)\apps\\.h
I tried to edit all those out, but even after that it wouldn't build.
(error is:
13 matches
Mail list logo
