02-04-2003
You don't need to 'split the key'... the key (shared secret) is symmetric, not asymmetric. You simply use the same (shared secret) key on both ends of the IPSEC VPN tunnel.
Each end will use the (shared secret) key to generate a session key.
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I'm facing a problem interpreting the shared memory key on an AIX machine.
(1) I go to a property file and I see the following:
shm_key = "119112066"
(2) So I now go the command prompt and do this:
ipcs -m | grep 119112066
And, I do not find it. So what I do is to run the... (2 Replies)
Discussion started by: vijaygade
2 Replies
2. IP Networking
Hello,
I'm trying to setup a gateway VPN between two routers across an unsecured network between two local networks. The routers are both linux and I'm using the ipsec tools, racoon and setkey. So far hosts from either local net can successfully ping hosts on the other local net without issue.
... (0 Replies)
Discussion started by: salukibob
0 Replies
3. Solaris
Hi, I've used the following way to set ssh public key authentication and it is working fine on Solaris 10, RedHat Linux and SuSE Linux servers without any problem. But I got error 'Server refused our key' on Solaris 8 system. Solaris 8 uses SSH2 too. Why? Please help. Thanks.
... (1 Reply)
Discussion started by: aixlover
1 Replies
4. Cybersecurity
hello,
after configuration ipsec in ip4 I can not ping between client and server whereas I had success ping before configuration!
I also generate different key for AH and ESP as i have shown below.
what is my problem and what should i do to have ping and test the configuration?
code:
... (0 Replies)
Discussion started by: elinaz
0 Replies
5. Programming
Hello.
I am new to this forum and I would like to ask for advice about low level POSIX programming.
I have to implement a POSIX compliant C shared library.
A file will have some variables and the shared library will have some functions which need those variables.
There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies
6. IP Networking
Hi all,
I have installed Openswan and configured IPSec and works perfect, but for some unknown reasons it stop working. I see that the tunnels are up and established. The route to the destination are added. Everything by the book seems to be ok. But somehow when i start to ping the other side (... (4 Replies)
Discussion started by: ivancd
4 Replies
7. IP Networking
Hi @all,
I try to connect 2 LANs with IPSec/Openswan
LAN 1: 192.168.0.0/24
LAN 2: 192.168.1.0/24
This is my Config:
conn HomeVPN # # Left security gateway, subnet behind it, nexthop toward right. left=192.168.1.29 ... (1 Reply)
Discussion started by: bahnhasser83
1 Replies
8. IP Networking
We are using cyberoam device, VPN IPSEC tunnel is going of frequently even the traffic is throug.
Please suggest what may be the cause for the above mentioned issue.
Also suggest a best tool to monitor the same VPN IPSEC tunnel connectivity. (4 Replies)
Discussion started by: marunmeera
4 Replies
LEARN ABOUT OPENDARWIN
dh_compute_key
DH_generate_key(3SSL) OpenSSL DH_generate_key(3SSL)
NAME
DH_generate_key, DH_compute_key - perform Diffie-Hellman key exchange
SYNOPSIS
#include <openssl/dh.h>
int DH_generate_key(DH *dh);
int DH_compute_key(unsigned char *key, BIGNUM *pub_key, DH *dh);
DESCRIPTION
DH_generate_key() performs the first step of a Diffie-Hellman key exchange by generating private and public DH values. By calling
DH_compute_key(), these are combined with the other party's public value to compute the shared key.
DH_generate_key() expects dh to contain the shared parameters dh->p and dh->g. It generates a random private DH value unless dh->priv_key
is already set, and computes the corresponding public value dh->pub_key, which can then be published.
DH_compute_key() computes the shared secret from the private DH value in dh and the other party's public value in pub_key and stores it in
key. key must point to DH_size(dh) bytes of memory.
RETURN VALUES
DH_generate_key() returns 1 on success, 0 otherwise.
DH_compute_key() returns the size of the shared secret on success, -1 on error.
The error codes can be obtained by ERR_get_error(3).
SEE ALSO
dh(3), ERR_get_error(3), rand(3), DH_size(3)
HISTORY
DH_generate_key() and DH_compute_key() are available in all versions of SSLeay and OpenSSL.
1.0.1e 2013-02-11 DH_generate_key(3SSL)