openssh installation problem

openssh installation problem

[Tony Gogoi]

Hello,

I am having a probelm with installing openssh from tarball. OpenSSL was
installed from tarball as well.


When I run ./configure, I get
---------------------------------

Checking openssl header version		90700f
Checking openssl library version	90701f
Checking whether OpenSSL's headers match the library NO

Any pointers how I could rectify this ?

Regards,
Tony

Re: openssh installation problem

[Adrian C.]

Hello.
I'm running into big trouble here with L2tpd compilation. Already
tried 3 or 4 versions and same error. Tried different distros also (so
it's not a gcc problem). On slack10 the same error occurs. This is
what mandrake reports:

[root@SoculuiNet l2tpd]# make
cc -g -O2 -DDEBUG_PPPD -DDEBUG_CONTROL -Wall -DSANITY -DLINUX
-I/usr/include   -c -o call.o call.c
In file included from l2tp.h:27,
                 from call.c:26:
misc.h:64: warning: conflicting types for built-in function `log'
call.c:166:23: missing terminating " character
call.c: In function `read_packet':
call.c:167: error: parse error before "enter"


Please help. Thanks.

On Tue, 14 Sep 2004 19:08:07 -0400 (EDT), Tony Gogoi
<tgogoi@cse.buffalo.edu> wrote:
> 
> Hello,
> 
> I am having a probelm with installing openssh from tarball. OpenSSL was
> installed from tarball as well.
> 
> When I run ./configure, I get
> ---------------------------------
> 
> Checking openssl header version         90700f
> Checking openssl library version        90701f
> Checking whether OpenSSL's headers match the library NO
> 
> Any pointers how I could rectify this ?
> 
> Regards,
> Tony
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: openssh installation problem

[Miguel González Castaños]

Tony Gogoi escribió:

>Hello,
>
>I am having a probelm with installing openssh from tarball. OpenSSL was
>installed from tarball as well.
>
>
>When I run ./configure, I get
>---------------------------------
>
>Checking openssl header version		90700f
>Checking openssl library version	90701f
>Checking whether OpenSSL's headers match the library NO
>
>Any pointers how I could rectify this ?
>
>Regards,
>Tony
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-admin" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>  
>
Do you have the openssl libraries package installed? Which distro do you
have? Under RedHat you have openssl and openssl-devel RPM...

HTH

Miguel


-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: openssh installation problem

[Chris DiTrani]

There are strings in call.c and network.c at the lines specified in the
error messages that illegally span lines (contain line-feeds). If you
simple concat the lines compilation will succeed.

CD

On Tue, 2004-09-14 at 19:36, Adrian C. wrote:
> Hello.
> I'm running into big trouble here with L2tpd compilation. Already
> tried 3 or 4 versions and same error. Tried different distros also (so
> it's not a gcc problem). On slack10 the same error occurs. This is
> what mandrake reports:
> 
> [root@SoculuiNet l2tpd]# make
> cc -g -O2 -DDEBUG_PPPD -DDEBUG_CONTROL -Wall -DSANITY -DLINUX
> -I/usr/include   -c -o call.o call.c
> In file included from l2tp.h:27,
>                  from call.c:26:
> misc.h:64: warning: conflicting types for built-in function `log'
> call.c:166:23: missing terminating " character
> call.c: In function `read_packet':
> call.c:167: error: parse error before "enter"
> 
> 
> Please help. Thanks.
> 
> On Tue, 14 Sep 2004 19:08:07 -0400 (EDT), Tony Gogoi
> <tgogoi@cse.buffalo.edu> wrote:
> > 
> > Hello,
> > 
> > I am having a probelm with installing openssh from tarball. OpenSSL was
> > installed from tarball as well.
> > 
> > When I run ./configure, I get
> > ---------------------------------
> > 
> > Checking openssl header version         90700f
> > Checking openssl library version        90701f
> > Checking whether OpenSSL's headers match the library NO
> > 
> > Any pointers how I could rectify this ?
> > 
> > Regards,
> > Tony
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: openssh installation problem

[Adrian C.]

Thank you very much. It worked. I think they should keep an eye on
this for the next version of L2TPD.

--Adrian.


On Wed, 15 Sep 2004 10:01:51 -0400, Chris DiTrani <cditrani@livedata.com> wrote:
> There are strings in call.c and network.c at the lines specified in the
> error messages that illegally span lines (contain line-feeds). If you
> simple concat the lines compilation will succeed.
> 
> CD
> 
> 
> 
> On Tue, 2004-09-14 at 19:36, Adrian C. wrote:
> > Hello.
> > I'm running into big trouble here with L2tpd compilation. Already
> > tried 3 or 4 versions and same error. Tried different distros also (so
> > it's not a gcc problem). On slack10 the same error occurs. This is
> > what mandrake reports:
> >
> > [root@SoculuiNet l2tpd]# make
> > cc -g -O2 -DDEBUG_PPPD -DDEBUG_CONTROL -Wall -DSANITY -DLINUX
> > -I/usr/include   -c -o call.o call.c
> > In file included from l2tp.h:27,
> >                  from call.c:26:
> > misc.h:64: warning: conflicting types for built-in function `log'
> > call.c:166:23: missing terminating " character
> > call.c: In function `read_packet':
> > call.c:167: error: parse error before "enter"
> >
> >
> > Please help. Thanks.
> >
> > On Tue, 14 Sep 2004 19:08:07 -0400 (EDT), Tony Gogoi
> > <tgogoi@cse.buffalo.edu> wrote:
> > >
> > > Hello,
> > >
> > > I am having a probelm with installing openssh from tarball. OpenSSL was
> > > installed from tarball as well.
> > >
> > > When I run ./configure, I get
> > > ---------------------------------
> > >
> > > Checking openssl header version         90700f
> > > Checking openssl library version        90701f
> > > Checking whether OpenSSL's headers match the library NO
> > >
> > > Any pointers how I could rectify this ?
> > >
> > > Regards,
> > > Tony
> > >
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > >
> > -
> 
> 
> > To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
>

Adding Apps To Panel

[Mike Tran]

[-- Attachment #1: Type: text/plain, Size: 377 bytes --]

I've just installed a digital clock in /usr/X11R6/bin/dclock. 
How do i get the clock to display on the panel?  I'm using linux 
version Redhat Enterprise W3.  

I've tried right click on an empty space in the panel then "add to panel"
but i can't find dlock listed anywhere. How do i get dclok listed in for 
example "Accessories". Thanks for any suggestion.

Mike


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: openssh installation problem

[Tony Gogoi]

> >When I run ./configure, I get
> >---------------------------------
> >
> >Checking openssl header version		90700f
> >Checking openssl library version	90701f
> >Checking whether OpenSSL's headers match the library NO
> >
> Do you have the openssl libraries package installed? Which distro do you
> have? Under RedHat you have openssl and openssl-devel RPM...
>

At first, the default red-hat version was installed from the installation
disks.
Then I installed the OpenSSL from source without uninstalling the RPM
versions of OpenSSL.

I thought if I could soft link libssl.so.0.9.4 to the one installed from
source then things could work. However, I found that the SSL installed
from source does not have shared libraries.

How can I build shared libraries from the "installed from source OpenSSL"?
THen  perhaps I could link libssl.so to the new shared libraries.

regards,
Tony

mounting secure usb flash drive

[Mike Tran]

[-- Attachment #1: Type: text/plain, Size: 476 bytes --]

Does anyone know how to access data on a usb secure mass storage drive?
I just bought a Lexar 512MB secure Jumpdrive. I used window to format it 
half public and half secure. The secure section is protected with a password for storing 
sensitive data.  When i try to mount it in Linux i can only see the unsecure partition.  
How does Linux access the secure portion of this drive. 
I looked at the mount command manual but did not see anything that can help.

Mike


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: mounting secure usb flash drive

[Matt Hemingway]

How about the -p option in mount?

mount: mount-2.12

-p "num" If  the  mount requires a passphrase to be entered, read it from file descriptor "num" instead of from the terminal.

-p num In case of a loop mount with encryption, read the passphrase from file  descriptor num instead of from the terminal.

I don't know what the Lexar 512MB secure Jumpdrive uses, but you prolly had to put in some sort of password/phrase to make it secure, right?

eh.

-Matt


On Wed, 15 Sep 2004 21:00:25 +0000
Mike Tran <mtran@opsec.usda.gov> wrote:

> Does anyone know how to access data on a usb secure mass storage drive?
> I just bought a Lexar 512MB secure Jumpdrive. I used window to format it 
> half public and half secure. The secure section is protected with a password for storing 
> sensitive data.  When i try to mount it in Linux i can only see the unsecure partition.  
> How does Linux access the secure portion of this drive. 
> I looked at the mount command manual but did not see anything that can help.
> 
> Mike
> 
>