As we now encourage users to use wolfSSL over yaSSL, we are deprecating the yaSSL forums and making them read only.

Best Regards,
Chris

I'm porting the yassl library to FreeBSD. The configure / make process runs more or less smoothly (I might submit FreeBSD-specific patches later on). I'm now trying to compile and run a simple client application, but run into linking errors because the definition of the Client interface is not included in the library:

client.cpp:(.text+0x21): undefined reference to `yaSSL::Client::Client()'
client.cpp:(.text+0x34): undefined reference to `yaSSL::Client::SetCA(char const*)'
client.cpp:(.text+0x111): undefined reference to `yaSSL::Client::~Client()'
client.cpp:(.text+0x1b7): undefined reference to `yaSSL::Client::Connect(int)'
client.cpp:(.text+0x27a): undefined reference to `yaSSL::Client::Write(void const*, int)'
client.cpp:(.text+0x29a): undefined reference to `yaSSL::Client::Read(void*, int)'
client.cpp:(.text+0x318): undefined reference to `yaSSL::Client::~Client()

I see that the implementation is in yassl.cpp, which is not built and thus not included in the library. yassl.cpp is only listed in EXTRA_DIST.

Any idea how one is supposed to use the Client (or Server) API?

I have just begin studying yaSSL these days.

Can someone tell me that  yaSSL whether support IPv6 without CyaSSL?

Thank you.

-DC

I am testing the yaSSL GPL code.

I started testing all the crypto algorithms supported by yaSSL.

Most of the algorithms got passed. But RSA test failed. When I debugged I found that this test failed because certificate got expired.

I hope yaSSL tries to extract the public key from the certificate and while validating this certificate it failed.

Can someone help me from where I could get the new client certificate.

Regards,
Satish

I have downloaded yaSSL GPL code and tried to build on Ubuntu platform.
While runing ./configure, i am facing some error as follows.

checking for g++ ... no
checking for c++... no
checking for gpp .. no
checking for aCC ... no
checking for CC ... no
checking for cxx ... no
checking for cc++ ... no
......
.....
checking whether c++ compiler works ... no
configure : error : C++ compiler cannot create executable.
see config.log for more details.

Can someone help me out how to fix thiis error?

1) V612 An unconditional 'return' within a loop. internal.c 7190

static int DoClientHello(....)
{
  ....
  while (ssl->options.resuming) {
    ....
    if (!session) {
      ....
      break;
    }
    if (MatchSuite(ssl, &clSuites) < 0) {
      ....
      return UNSUPPORTED_SUITE;
    }
    ....
    return ret;
  }
  return MatchSuite(ssl, &clSuites);
}  

Also:
V612 An unconditional 'return' within a loop. internal.c 7026

2) V614 Potentially uninitialized variable 'rhSize' used. sniffer.c 2255

static int ProcessMessage(....)
{
  int rhSize;
  ....
  notEnough = 0;
  ....
  if (sslBytes >= RECORD_HEADER_SZ) {
    if (GetRecordHeader(sslFrame, &rh, &rhSize) != 0) {
      ....
      return -1;
    }
  }
  else
    notEnough = 1;
  ....
  if (notEnough || rhSize > (sslBytes - RECORD_HEADER_SZ)) {
    ....
  }

  tmp = sslFrame + rhSize;   <<<---
  ....
}

FYI, there's a diff for yassl in this one.

I'm getting :
Microsoft (R) Program Maintenance Utility Version 11.00.50214.1
Copyright (C) Microsoft Corporation.  All rights reserved.

[  0%] Built target INFO_BIN
[  0%] Built target INFO_SRC
[  2%] Built target zlib
[  2%] Building CXX object extra/yassl/CMakeFiles/yassl.dir/src/cert_wrapper.cpp
.obj
cert_wrapper.cpp
e:\test-trunk\extra\yassl\include\socket_wrapper.hpp(31) : fatal error C1083: Ca
nnot open include file: 'winsock2.h': No such file or directory

openssl genrsa -out my_priv_key.pem 4096
openssl rsa -in my_priv_key.pem -out my_pub_key.pem -pubout

Then converted the PEM files to DER files like this:

openssl rsa -in  my_priv_key.pem  -inform PEM -out  my_priv_key.der -outform DER
openssl rsa -in  my_priv_key.pem -pubout -out my_pub_key.der -outform DER

Parsing the private key works fine and I can successfully extract the public key components from this key to encrypt and decrypt a message (using   rsaPub.SetModulus(n); rsaPub.SetPublicExponent(e)), but when I try to do:

TaoCrypt::RSA_PublicKey rsaPub(public_key_src);
TaoCrypt::PK_Lengths lengths(rsaPub.GetModulus());
printf("Pub key: FixedCiphertextLength= %u\n",lengths.FixedCiphertextLength());

I get the result:
Pub key: FixedCiphertextLength= 0

The failure seems to happen in RSA_Public_Decode::Decode() :

// Decode a BER encoded RSA Public Key
void RSA_Public_Decoder::Decode(RSA_PublicKey& key)
{
    ReadHeader();
    if (source_.GetError().What()) return;

    // public key
    key.SetModulus(GetInteger(Integer().Ref()));  <---- Fails
    key.SetPublicExponent(GetInteger(Integer().Ref()));
}

and more specifically here:

void Integer::Decode(Source& source)
{
    byte b = source.next();
    if (b != INTEGER) {
        source.SetError(INTEGER_E);  <-- exit path
        return;
    }
[..]

What is the proper way to store the public key so that it can be parsed correctly?

Regards,
Kristofer Pettersson

sajithts
(2008-10-01 06:36:17 UTC)

How to build yassl and taocrypt shared libraries?  I can seem to build only the static libs.  On Ubuntu 7.04 feisty; autoconf 2.5.0; automake 1.9.6; libtool 1.5.22.

touska
(2008-10-01 21:42:37 UTC)

I've added support to configure for shared libs.  Though sourceforge is having problems with developer access to CVS after their migration yesterday so I can't check in the changes yet.  I'll post back after it's checked in.

Shared lib support in configure is checked in for yaSSL.  See: http://sourceforge.net/cvs/?group_id=129181 for details.

sajithts
(2008-10-02 10:03:43 UTC)

That worked.  Thank you!  openssl-links target is perhaps an affected party.  You might want to check that.  I however was trying to build curl against yassl for a mips-linux-uclibc based embedded system.  Looks like yassl is a little too big for this particular box.  (libyassl 508K, libyacrypt 528K, plus C++ runtime perhaps? 

This was built with "./configure

--disable-zlib --enable-plain-c", have I done it right?)

Got a few questions here:

1. Perhaps I should try cyassl?  This certainly depends on the state of cyassl's openssl compatibility layer..

2. Is cyassl's openssl compat layer "good enough" for curl at this point?  Reason for asking is, in curl users' mailing list, I was told that although curl buids against yassl, it doesn't pass all test cases.  Further, no one has tried buidling curl against cyassl, so it probably stands much less chance.  (I was also told that it should not be too hard to make curl work with yassl's native API, but I'm on a schedule here...)

3. I did try building curl against cyassl, but curl's configure complained about missing libcrypto symbols (CRYPTO_lock etc.)  How can I build libctaocrypt properly?

Sorry about pestering.  But I'm sort of lost with both openssl and gnutls.  I was really excited to find yassl project...

sajithts
(2008-10-02 11:08:24 UTC)

Q&A in curl users's list, if anyone wants to take a look...

http://curl.haxx.se/mail/archive-2008-10/0001.html
http://curl.haxx.se/mail/archive-2008-10/0002.html
http://curl.haxx.se/mail/archive-2008-10/0003.html

touska
(2008-10-02 19:19:21 UTC)
You might want to try --disable-debug and stripping the shared objects as well.  Though not sure if that will be enough for you.

I'll try to get CyaSSL to build with curl, it should be pretty close.  I'll post back on the results.

openssl/dsa.h
openssl/dh.h files are missing.

Is it possible to build licurl using yassl as underlying SSL stack.

-Ambuj