IMHO, this is a statement of how an implementation must solve your
problem, not a statement of the problem you are trying to solve.
I suggest that you forget for the moment everything you think you
know about public and private keys, state your problem, and then listen
to
far with this. I've used tools built around gcc's
--instrument-functions capability to help me understand what parts of
libcrypto I actually use, for instance.
Paul Allen
__
OpenSSL Project
On Mon, 2009-06-15 at 21:32 -0700, patfla wrote:
> Hi Paul,
>
> I'm using (and have used from some time) a windows build of OpenSSL from
> here:
>
> http://www.slproweb.com/products/Win32OpenSSL.html
Yup. I don't know why anybody would take that risk when building from
trusted source is so easy
forget my puzzlement. Grab a copy of the source from the OpenSSL
web site and have a look in the apps and demos subdirectories. You
might find some of what you need there.
Paul Allen
__
OpenSSL Project
e that's older than the latest from openssl.org.
It is fairly simple to operate with multiple OpenSSL versions
installed, but you must keep them separate and pay attention to
$PATH and to -I and -L compiler switches.
Paul Allen
__
On Tue, 2009-03-31 at 08:50 -0700, Beneš Vladimír wrote:
> Hi,
>
> there is mentioned command option "-md" on official documentation -
> http://www.openssl.org/docs/apps/smime.html#
> """
> SYNOPSIS
> openssl smime ... [-md digest] ...
> ...
> COMMAND OPTIONS
> ...
> -md digest
> digest a
successful\n");
else
{
BIO_printf(bio_err, "Verification failure\n");
goto end;
}
Is there a better way to do this that would feel less like crawling
through a side window? I'd like to use the front d
our CD for a while and tell you what you
need to know in order to proceed. You could catch the return
code from the grep and only print the package name containing
the match, but I'm not good enough to throw that code off out
of my head and have it guaranteed to work. The above will ge
n between OpenSSL and console logins, but you know
your system better than I. Ask yourelf, "How is OpenSSL related to
the process of logging in on the console?" Examine the logs for clues.
Perhaps you will follow the chain to a resolution. If you uncover more
clues but still don't h
ndom, prngd seems to be the current
recommended solution.
Paul Allen
--
Boeing Phantom Works \ Paul L. Allen, (425) 865-3297
Math & Computing Technology \ [EMAIL PROTECTED]
POB 3707 M/S 7L-40, Seattle, WA 98124-2207 \ Prototype Systems Group
S/MIME Cryptographic Signature
egular SSL functionality.
Paul Allen
--
Boeing Phantom Works \ Paul L. Allen, (425) 865-3297
Math & Computing Technology \ [EMAIL PROTECTED]
POB 3707 M/S 7L-40, Seattle, WA 98124-2207 \ Prototype Systems Group
S/MIME Cryptographic Signature
made sure he had a recent copy of binutils installed and then moved
/usr/ccs/bin/as aside. Problem solved. The correct solution is
probably to rebuild gcc with only the GNU "as" available, so it won't
even try to use the one in /usr/ccs/bin. That was deemed to be too
much effort ju
ack
here and tell us exactly what you tried and exactly what happened.
Paul Allen
--
Boeing Phantom Works \ Paul L. Allen, (425) 865-3297
Math & Computing Technology \ [EMAIL PROTECTED]
POB 3707 M/S 7L-40, Seattle, WA 98124-2207 \
Arno Puder wrote:
>
> Hello,
>
> has anyone succeeded in compiling OpenSSL under PocketPC using
> Microsoft's Embedded VC++?
It works under Linux on an iPAQ. What's Microsoft's problem?
:-)
Paul Allen
--
Boeing Phantom Works \ Paul
when it tries to exec
the linker. Either your compiler, your linker, or both are incorrectly
installed.
Good luck!
Paul Allen
--
Boeing Phantom Works \ Paul L. Allen, (425) 865-3297
Math & Computing Technology \ [EMAIL PRO
Type: application/ms-tnef
> Encoding: base64
Excuse me? No Subject: line, no text content, and a Windows binary
attachment of some sort? What's your point?
:-)
Paul Allen
--
Boeing Phantom Works \ Paul L. Allen, (425) 865-3297
Math & Computing Technology
tober. The
RSA implementation built into OpenSSL is superior and is now legal to
use.
Paul Allen
"Debra Mendelson, CCE" wrote:
>
> I built my openssl, modssl, apache system following the general instructions
> for building a dso server and got the following error message when I r
e of the system include files are kernel version dependent and
come as a separate package. You need to install the kernel-headers
package for your kernel version. It'll be on your RedHat install CD.
Paul Allen
--
Boeing Phantom Works \ Paul L. Allen, (425) 865-3297
Math &
Michael Sierchio wrote:
>
> Paul Allen wrote:
> > The SUNWski package works fine on Solaris 8. Really. It doesn't
> > complain at install time, and it works fine.
>
> Just for grins, could you post a definitive URL for the patch? The
> only pages I found
mpting to make certificate for
> apache-ssl
>
> any help would be appreciated.
The SUNWski package works fine on Solaris 8. Really. It doesn't
complain at install time, and it works fine.
Paul Allen
--
Boeing Phantom Works \ Paul L. Allen, (425) 865-3
legions continue to toil
away in their dungeons. You may rest assured that they do not worry
about obscure license clauses that get trampled underfoot.
What's the goal here? Is it to produce software that doesn't suck?
Or is it to prove that somebody's wrong? I think it's t
that's the really short version of what's written in the
> docs...
Or to put it another way, "Leave off the configure option that tells
it to use RSAREF. It will use the built-in RSA algoritm instead."
Good luck!
Paul Allen
--
Paul L. Allen | voice: (425) 865-3297
#x27;m curious.
Our corporate gateway apparently filtered this virus, since there's
no trace of it in my inbox other than converstion about it. What
vulnerability did it exploit? If you care to reply, perhaps edit
the To: line to point to me instead of the list.
Thanks!
Paul Allen
--
Paul L. A
ot;. When it finishes, you will have /dev/random support. You
might have to stop and start the daemon with the
/etc/init.d/cryptorand script in order for things to work. Exit
the root account and go back to building OpenSSL.
Paul Allen
--
Paul L. Allen | voice: (425) 865-3297
e? Or do I get to debug code on
unfamiliar hardware all by myself? :-)
Paul Allen
--
Paul L. Allen | voice: (425) 865-3297 fax: (425) 865-2964
Unix Technical Support | [EMAIL PROTECTED]
Boeing Phantom Works Math & Computing Technolog
25 matches
Mail list logo