I did an "emerge --update --ask world" and now at boot time I get this:

mod_tls/2.2.1: compiled using OpenSSL version 'OpenSSL 0.9.8k 25 Mar 2009' headers, but linked to OpenSSL version

everything seems to work fine on the system and google searches doesnt seem to have a solution to this linking warning message, then I did

"emerge --update --deep --world --assk" as I thought maybe one of the nested dependencies had to be updated but this did not solve it either, anyone know how to correct this?

That looks like an incomplete message. Have a look through your log (or run:
and then view the file) and see if you can see what comes after "but linked to OpenSSL version...". It might help us.

my boot messages don't appear in dmesg, do I need to enable that feature somewhere?

Maybe, but I don't know how. Alternatively there should be something in /var/log (probably called /var/log/boot or /var/log/messages - I'm not on my linux box to check as I'm at work).

I'll wait till I'm in front of the console and capture the entire message in console mode.

this is the output at boottime

* Checking proftpd configuration ...
Checking syntax of configuration file
- mod_tls/2.2.1: compiled using OpenSSL version 'OpenSSL 0.9.8k 25 Mar 2009' headers, but linked to OpenSSL version 'OpenSSL 0.9.8l 5 Nov 2009' library
Syntax check complete. [ ok ] * Starting proftpd ...
- mod_tls/2.2.1: compiled using OpenSSL version 'OpenSSL 0.9.8k 25 Mar 2009' headers, but linked to OpenSSL version 'OpenSSL 0.9.8l 5 Nov 2009' library [ ok ] * samba -> start: smbd ...

Right, well the difference between the header version and the library version is so small (1 build) and everything seems to be working, so I wouldn't worry. What's likely happened is that originally you had OpenSSL version 0.9.8k on your system, you then compiled tls against this version, and then when you did the update it's updated your version of OpenSSL to 0.9.8l because it was available. I'd doubt very very much that any function definitions have changed from one minor build to the next.

If it's bothering you, try emerging ProFTPd again. If it recompiles it should link to the correct version again.