[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[microblaze-uclinux] Re: Boa + SSL hanging after certificate download



Hello all (again),

Some Additional Information:

I took 'prime and prime.o' out of the openssl makefiles so I could build the openssl app (to see if this was openssl or boa related). When I first tried to run the app, it failed with a memory error.

Considering the XUP board has 256 MB installed (and wasn't really out of memory), I enabled the "allow allocating large blocks (>1MB)" in the kernel config. This allowed openSSL to run (and print out help messages), however it would lock up the system as well when running options such as 'openssl speed' (a benchmark that runs through various ciphers).

# Doing md2 for 3s on 16 size blocks: <HANG>

Right after I enabled >1MB allocation support, openssl SIGSEVed when running the 'speed' option. However, I couldn't get a core dump because I wasn't in a writable directory. When I moved to /var to run it again, it hung on run.

No change in Boa's behavior after the memory allocation change.

XMD reports that the processor has stopped whenever the hangs occur. I'm not too keen on XMD's debugging ability, is there a good way to see what the last few instructions were run before the hang?

--------------------------

Another question I have regarding the building of the image...

A few weeks ago, when I downloaded the package for my XUPV2P board, I could not build linux. It would error out with an error related to not having CONFIG_XILINX_FLASH_SIZE and CONFIG_XILINX_FLASH_START defined (during mtd* compilation). The included auto-config.in inside the microblaze_0 directory included with the XUP package didn't include this variable.

I simple entered in some values to make it happy, it didn't seem like they overran any other memory locations:

define_hex CONFIG_XILINX_FLASH_START 0xff000000
define_hex CONFIG_XILINX_FLASH_SIZE 0x00800000

This allowed the compilation to continue, and I had not noticed any problems playing around with various other facets of the distribution.

Is there a .config that was used when creating the XUPV2P package on the webpage that I can use that won't ask for these variables? They aren't specified when rebuilding the included system in the EDK, so I don't know what else to do with them other than to stub them out.

Thanks,

Jonathan


On Oct 22, 2005, at 11:17 AM, Jonathan Jung wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I'm attempting to get Boa (webserver) to work with SSL as part of my uClinux build. The instructions I used were located at:

http://www.ucdot.org/article.pl?sid=03/07/30/0114226&mode=thread

I used slightly different instructions to build openssl (http:// www.ucdot.org/article.pl?sid=03/10/23/2249235&mode=thread), but it does compile. Boa compiles too with SSL enabled, however the problem comes into play when I'm trying to use it.

Environment:

XUPV2P board
- -ssl_cert.pem and ssl_key.pem (uclinux-auto as hostname) in /etc/ config/
- -uclinux-auto in local machine's hostfile
- -syslogd working on /var/log/messages
- -test file and boa.conf in /var
- -/dev/urandom seems to provide data via dd if=/dev/urandom of=/ var/test count=1

Boa seems to work fine when using normal http, starting with 'boa - c /var'. I can request and get files via http.

Boa Startup messages in syslogd:

<5>Jan 1 00:11:09 boa[98]: Enabling SSL security system
<7>Jan 1 00:11:09 boa[98]: Loaded SSL certificate file: /etc/config/ ssl_cert.pe <7>Jan 1 00:11:09 boa[98]: Opened private key file: /etc/config/ ssl_key.pem
<5>Jan 1 00:11:09 boa[98]: SSL security system enabled
<6>Jan 1 00:11:09 boa[98]: Boa/0.93.15 started

However, when I request a file via ssl, the uclinux system hangs. The host system does start the connection, and I'll get a warning about an unsigned certificate (I created it myself). It's right at this point where the uclinux system hangs, won't respond to carriage returns or hard breaks.

Has anybody experienced similar problems (or successes) with SSL or even Boa + SSL? I know SSH is suppose to work for the platform as well, any success stories that might be related to my problem?

Thanks,

Jonathan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFDWoJU4kOt3FHegqgRAkLCAKCjQAL0siLEhagbNbZlNDv+vroPUgCeO/2Z
XdBgDJxQZo9SndZorJ7hJ3c=
=dBwt
-----END PGP SIGNATURE-----


___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/