public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Laurie Gellatly" <laurie.gellatly@netic.com>
To: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS]  Re: Using openssl for HTTPS
Date: Fri, 30 Oct 2009 21:39:00 -0000	[thread overview]
Message-ID: <001801ca59a9$795466c0$6bfd3440$@gellatly@netic.com> (raw)
In-Reply-To: <hcesn2$478$1@ger.gmane.org>

Hi Kevin,
Thanks for the speedy reply.
Unfortunately I'd already seen (and have tried to follow) that page.
Now that I've slept on it I realized that I had unchecked some of the 
algorithms in the openSSL package. I've just put them all back in
(suffering quite an increase in code size) but at least the SSL_CTX_new
now passes and the complaint is now about my private key.

Does anyone know which algorithms are needed (or conversely which 
ones can be unchecked) for SSL to still work?

			...Laurie:{)

> -----Original Message-----
> From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
> owner@ecos.sourceware.org] On Behalf Of Kelvin Lawson
> Sent: Saturday, 31 October 2009 1:20 AM
> To: ecos-discuss@sources.redhat.com
> Subject: [ECOS] Re: Using openssl for HTTPS
> 
> Hi Laurie,
> 
> > Does anyone have a working example they can share?
> > If the example happens to go into the certificates and keys (their
> setup,
> > format and functions that use them) that would be really excellent.
> 
> A good example is the "wserver" code available from:
> http://www.rtfm.com/openssl-examples/
> 
> Regards,
> Kelvin.
> 
> 
> --
> Before posting, please read the FAQ:
> http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2009-10-30 21:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19  9:32 [ECOS] RedBoot image for Olimex LPC-E2294 peter_lanius
2009-10-19 10:42 ` Sergei Gavrikov
2009-10-19 11:42   ` peter_lanius
2009-10-19 13:47     ` Sergei Gavrikov
2009-10-24  9:37       ` [ECOS] RedBoot loading eCOS examples causes PC reboot peter_lanius
2009-10-24 12:38         ` Sergei Gavrikov
     [not found]           ` <738229.12555.qm@web51906.mail.re2.yahoo.com>
2009-10-25 13:20             ` Sergei Gavrikov
2009-10-25 16:04               ` Sergei Gavrikov
2009-10-26  9:58               ` [ECOS] LPC2XXX watchdog feeds and interrupts Laurie Gellatly
2009-10-30 13:51                 ` [ECOS] Using openssl for HTTPS Laurie Gellatly
     [not found]                 ` <46171.9697145329$1256910809@news.gmane.org>
2009-10-30 14:20                   ` [ECOS] " Kelvin Lawson
2009-10-30 21:39                     ` Laurie Gellatly [this message]
     [not found]                     ` <26103.8444740281$1256938790@news.gmane.org>
2009-11-02  8:58                       ` Kelvin Lawson
2009-11-02 10:22                         ` Laurie Gellatly
2010-02-04 17:45                     ` [ECOS] pthread_kill return value Jay Foster
2010-02-08 12:36                       ` Bart Veer
2009-10-27  6:11               ` [ECOS] RedBoot loading eCOS examples causes PC reboot peter_lanius
2009-10-24 13:21         ` [ECOS] " Grant Edwards

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001801ca59a9$795466c0$6bfd3440$@gellatly@netic.com' \
    --to=laurie.gellatly@netic.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).