BeBits - cryptlib

<a href="http://a.tribalfusion.com/i.click?site=BeBits&adSpace=ROS&requestID=1227386007" target=_blank > <img src="http://a.tribalfusion.com/i.ad?site=BeBits&adSpace=ROS&requestID=1227386007" width=468 height=60 border=0 alt="Click Here"></a>
Please support our sponsors!

cryptlib

Talkback

Go back to the cryptlib page

Post a new Talkback comment!

Building problems

By Jess - Posted on November 29, 2004 - 18:44:08 (#14893)
Current version when comment was posted: 3.1

I've seen a few others post with the same problems I've had, I've asked countless dev's & searched the net for this "header problem" MYOB told me about but in any case head to this thread http://www.bebits.com/talkback/3443#14892 to read how to build this sucker if you have had problems before.

Mail me the Bme errors

By MYOB - Posted on November 27, 2004 - 06:56:49 (#14868)
Current version when comment was posted: 3.1

Jess - mail me the errors that BeIDE is giving you for Bme.

BME - both netstacks fail

By Jess - Posted on November 26, 2004 - 19:51:50 (#14863)
Current version when comment was posted: 3.1

I've tried building BME on both BONE & net_server, the issue from what I can see isn't cryptlib but a broken project.

Yes I'm aware...

By Jess - Posted on November 16, 2004 - 14:44:50 (#14765)
Current version when comment was posted: 3.1

BeIDE was being a ^&@# & wouldnt let me remove the libzeta, I eventually was able to remove it. However the post as I said was from the ONE time I got it to stop complaining about the cryptlib, any other time my errors are about the cryptlib. However being able to get it to shut up is still done in a whack way & the build still fails. I have heard about the "needed fix" to the BONE headers but found no info on what it is exactly that needs fixing.

I'd really like to be using/trying this but it baffels me why some one can't just zip their compile & post for the rest of us, hell I will host the damn thing, I'm just sick of software builds failing, failing in Linux failing in BSD failing in Be! Can't anything just work any more? JUST WORK!!!!! /me shakes fist at the sky!

No cryptlib error

By Sir Mik - Posted on November 16, 2004 - 11:49:09 (#14764)
Current version when comment was posted: 3.1

the errors you posted here have nothing to do with cryptlib! It's a BONE specific problem (see the in_addr part in the error)...There's something wrong in the compatibility layer I think, not sure. I made it work on my system(r5+BONE) by changing the system headers. Otherwise you won't be able to build Bme. Btw, Error : File not found: “x86/libzeta.so”, this error is, as far as I know, not caused by our project file, because we don't include it in our project.

regards,

Tim

BME - same problem

By Jess - Posted on November 16, 2004 - 11:41:05 (#14763)
Current version when comment was posted: 3.1

Re: building

By tb100 - Posted on November 16, 2004 - 03:44:15 (#14762)
Current version when comment was posted: 3.1

Delete the entry for cryptlib.so in the project file. Then drag-and-drop cryptlib.so from wherever you put it into the BeIDE project window. That should get the paths sorted.

If you go into project settings on BeIDE (Edit menu I think) you can check that the path it complains about is no longer in the "Access Paths" section.

Re: Building...

By gmiranda - Posted on November 15, 2004 - 14:36:36 (#14754)
Current version when comment was posted: 3.1

Still doesn't work. I've tried to put both cryptlib.h where you said and I still get the message: "Couldn't find access path. {project}/../../cryptlib

So I placed cryptlib folder into that path, /boot/Desktop : now I don't have that message, but cannot make :(
Warnings and errors. Have you managed to make it? By the way, I'm on Zeta RC3

Building...

By tb100 - Posted on November 15, 2004 - 08:37:58 (#14750)
Current version when comment was posted: 3.1

If all you want to do is get Bme to build, you can place cryptlib.so for the BeMSN release somewhere accessible (one option is to make a lib folder in your Bme directory and put it in there), then place the cryptlib.h header somewhere else (/boot/develop/headers/ should do it).

To build from source, "make shared" is the commend you need. Some of the latest snapshots haven't worked all that well for me though, so maybe the thing I described first is the best way.

Don't know how to build it!

By gmiranda - Posted on November 13, 2004 - 13:09:12 (#14725)
Current version when comment was posted: 3.1

Hi, I unzipped it as mmlr said (otherways it won't compile) to /boot/home/cryptlib. Then I 'made' it and I couldn't find any cryptlib.so or something similar, just libcl.a... I'm trying to build BeMSN (CVS version) so I need cryptolib. Currently it does not work, BeIDE shows a list of errors (cryptlib's headers not found, blah blah blah) so tried to copy everything to /boot/home/config/include/cryptlib, with no success. I've also tried to copy the .h located on the main cryptlib dir to [...]/include, but it doesn't not work :(

Anyone can explain how they built the library and used it?

Thanks, Guillermo

Re: Wrong place to ask

By Peter Gutmann - Posted on March 17, 2004 - 06:47:35 (#11497)
Current version when comment was posted: 3.1

>Unless NT-5.1 is a new name for BeOS, this is entirely the wrong place to ask
>about compiling on Windows XP. This is a site for BeOS applications/drivers
>only.

Well, technically you could post the question to rec.pets.cats and I'd
eventually reply, but I agree that there are better places to ask non-BeOS
questions, like the general cryptlib mailing list.

Peter.

Wrong place to ask

By MYOB - Posted on March 10, 2004 - 15:19:57 (#11407)
Current version when comment was posted: 3.1

Unless NT-5.1 is a new name for BeOS, this is entirely the wrong place to ask about compiling on Windows XP. This is a site for BeOS applications/drivers only.

any idea on this error ? misc/net_tcp.c

By eranki - Posted on March 10, 2004 - 14:40:17 (#11405)
Current version when comment was posted: 3.1

misc/net_tcp.c:232: arpa/nameser.h: No such file or directory
misc/net_tcp.c:245: resolv.h: No such file or directory
make[2]: *** [static-obj/net_tcp.o] Error 1

problem to compile in CYGWIN_NT-5.1

By eranki - Posted on March 10, 2004 - 14:16:10 (#11404)
Current version when comment was posted: 3.1

If anyone knows how to solve this compilation problem

cert/certstr.c: In function `isNativeWidecharString':
cert/certstr.c:117: `WCSIZE' undeclared (first use in this function)

Re: My results

By Peter Gutmann - Posted on December 27, 2003 - 20:07:08 (#10195)
Current version when comment was posted: 3.1

The source code's been updated so the code changes shouldn't be necessary any more. I'm looking into the makefile/linking issue, there are some historical issues with that which means the linking has to be done a certain way or users on some other systems will complain.

My results

By mmlr - Posted on December 27, 2003 - 10:14:47 (#10187)
Current version when comment was posted: 3.1

I have tested the new sources and allready sent my results back to Peter.

If you need to compile the new sources on BeOS, be sure to do the following:

1. Unzip from the terminal with the command "unzip -a -d <destdir> cl31.zip". The "-a" is very important. If you unzip without it, make will not be able to figure out on what platform you operate (ppc vs. x86).

2. Edit envelop/envelop.h line 177 and comment out the "union {" and the "}" on line 179. The GCC-Versions available on BeOS cannot handle unnamed unions.

If you compile for BONE you need to change two more things:

3. Edit misc/net_tcp.c line 322. The "(errno == 0x80007)" should be "(errno == 0x80007024)".

4. Edit the makefile on line 1203 and add "-lbind -lsocket" right after "-nostart"

Hope this helps...

Updated source code

By Peter Gutmann - Posted on December 27, 2003 - 06:58:46 (#10185)
Current version when comment was posted: 3.1

I've just updated the source based on mmlr's diffs, hopefully this should now build with BONE. However, I have this horrible feeling that one of the changes (attempting to include <sys/socket.h> to get the BONE_VERSION define) may cause problems with non-BONE systems, could someone with a non-BONE / Dano / etc system give it a go and see whether it still works OK? If not, I'll need to update the makefile to check for signs of BONE when it builds the code.

Source Diff

By mmlr - Posted on December 23, 2003 - 06:59:16 (#10128)
Current version when comment was posted: 3.1

I haven't changed that much afterall. The only changes needed are in misc/net_tcp.c and you have to include -lbind and -lsocket (makefile, line 1203). You can find the source diff there:
http://kandent.com/mlotz/net_tcp.diff

I allready sent Peter a mail about it, but didn't get a answer as of yet.

This cryptlib works on BONE, Dano and Zeta. But I'm not sure if it can be built on Dano / Zeta out of the box, because there seem to be some different headers... You'll have to try it and see for yourself.

@mmlr: BONE Build

By tb100 - Posted on December 23, 2003 - 05:26:38 (#10125)
Current version when comment was posted: 3.1

mmlr,

Did have have to change much to get it to build and work properly on BONE? I'm sure Peter would be more than happy to merge your changes with the rest of the code, so anyone can build cryptlib out of the box, no matter what network stack.

Incidentally, is this on Zeta or R5/BONE?

Simon

Thank you very much

By Jess - Posted on December 22, 2003 - 12:55:19 (#10100)
Current version when comment was posted: 3.1

DL'ing & will try asap. Thanks!

Cryptlib for BONE

By mmlr - Posted on December 22, 2003 - 10:31:09 (#10097)
Current version when comment was posted: 3.1

There you have it:

http://mypage.bluewin.ch/mmlr/beos/libcl.so.3.1.0-BONE.zip
or
http://kandent.com/mlotz/libcl.so.3.1.0-BONE.zip

To install simply unpack the lib and move it to /boot/home/config/lib.

(BeMSN works on BONE with this)

RE what I'm using

By the_leander - Posted on December 17, 2003 - 20:01:55 (#10016)
Current version when comment was posted: 3.1

I'm using Zeta RC1.1 (RC1 with service pack 2)

My rig is as follows:

AthlonXP2000
ecs k7s5a motherboard with ac97 sound
512Mb sd-ram
Radeon 9200
2 40Gb hard disks, 1dvdrom and 1 cdrw
oh and a realtech eithernet card

I'll give it a go with the cc -v option and let you know how it goes :-)

@ Tb100 I would offer to do that but for the fact I wouldn't know what I was doing - I don't know C...

give us a shout on the old email addy and perhaps we could go through the ways of doing it, who knows, perhaps we might even find a fix for it :-)

Re: no go

By Peter Gutmann - Posted on December 17, 2003 - 18:09:41 (#10015)
Current version when comment was posted: 3.1

Can you send me the output of a cc -v? cryptlib autodetects the OS type and platform type based on what the compiler tells it, I check for all the standard gcc defines but it must be using something else. Or are you building this on a PPC system?

Re: no go

By tb100 - Posted on December 17, 2003 - 03:38:15 (#10005)
Current version when comment was posted: 3.1

Go into crypt/osconfig.h

Try just copying the defines for the x86 architectures over the top of the #error about needing to define stuff.

Then do a "make clean", followed by a "make".

What version of gcc are you using? Try it with the 2.9 series if the 3.x one still doesn't work.

If that works, we need to find something defined by Zeta (maybe __i586__ ) that could go in the correct place in osconfig.

As for the IM client, it's still a way off yet - still getting the basic structure in place. Thanks for the offer though, it would be good to get a Zeta version compiled when it's finished (although by that time I might be running Zeta myself!)

Simon

Hmmm, nope, no go

By the_leander - Posted on December 16, 2003 - 21:24:34 (#10001)
Current version when comment was posted: 3.1

Downloading now

By the_leander - Posted on December 16, 2003 - 21:12:36 (#10000)
Current version when comment was posted: 3.1

I'm running Zeta RC1.1, I'll probably try compiling this sometime tomorrow as its 3:15am here.

Also, if you're still after someone to try out your forthcomming IM app, I'm willing to give it a go.

Regards,
The Leander

For those who don't want to read the installation instructions...

By tb100 - Posted on December 15, 2003 - 09:23:05 (#9969)
Current version when comment was posted: 3.1

This is a cross-platform library, so the zip is not quite the same as most BeOS zip files. Firstly, the text files use windows-style new lines, and secondly the zip doesn't have one "root" folder.

Thus to unzip, do something like:
$ mkdir clib31
$ unzip -a cl31.zip -d ./clib31/
(the -a flag converts the windows new lines to unix ones)

To build the static version of the library, simply run "make". Then do "make testlib", and look at the output of "testlib" to check it's all working.

You can do a similar thing with a shared library: "make clean", "make shared", "make stestlib", "stestlib".

Make sure you download the documentation, and there's a helpful mailing list on the cryptlib site if you get stuck.

Thanks very much for providing this Peter - it's a very powerful library and actually means SSL works on R5 net_server! If somebody could build and test on BONE/Zeta, I'd like to know how it goes (Peter ported this to net_server by telnetting into my box).

Thanks again.

Simon













			Recent Downloads - # 350 Total Downloads - # 1,653 Total Views - # 2,063 User Ratings - N/A




			Tool Kits




			1. QEMU - 9.62 2. ScummVM - 9.50 3. cpu_fix - 9.42 4. Jukebox - 9.36 5. Haiku AGP busm... - 9.35 6. vim6 - 9.31 7. Beezer - 9.25 8. BeeF - 9.25 9. HandBrake - 9.24 10. DOSBox - 9.22




			1. Ati Radeon Grap... - 253 2. Realtek RTL8139... - 205 3. BeOS 5 Personal... - 199 4. ATI Rage 128 Pr... - 169 5. USB Serial driver - 107 6. Ensoniq AudioPC... - 106 7. Broadcom 440x 1... - 100 8. DjVu Viewer - 100 9. VLC Media Player - 73 10. S3 Trio 64 v2 DX... - 64




			You are not logged in. Login or create an account...


	Unless otherwise noted, everything is copyright © 1999-2002 Fifth Ace Productions, LLC. All Rights Reserved. For more legal trivia, take a gander at our Legal Stuff page and our Privacy Statement.