| View previous topic :: View next topic |
| Author |
Message |
buhofromepn
n00b
Joined: 22 Nov 2007
Posts: 2
|
 Posted: Thu Nov 22, 2007 5:18 pm Post subject: des 3des md5 support gentoo kernel 2.6.22 |
 |
|
Hello -
The kernel options for md5 des and 3des are disable in my kernel config
I have some 2.4.22 machines with vpn support using these options. How do
the new openswan handles md5, 3des ?
| Code: | --- Cryptographic API │ │
│ │ --- Cryptographic algorithm manager │ │
│ │ --- HMAC support │ │
│ │ < > XCBC support │ │
│ │ < > Null algorithms │ │
│ │ < > MD4 digest algorithm │ │
│ │ --- MD5 digest algorithm │ │
│ │ --- SHA1 digest algorithm │ │
│ │ <*> SHA256 digest algorithm │ │
│ │ < > SHA384 and SHA512 digest algorithms │ │
│ │ < > Whirlpool digest algorithms │ │
│ │ < > Tiger digest algorithms │ │
│ │ < > GF(2^128) multiplication functions (EXPERIMENTAL) │ │
│ │ <M> ECB support │ │
│ │ --- CBC support │ │
│ │ <M> PCBC support │ │
│ │ < > LRW support (EXPERIMENTAL) │ │
│ │ < > Software async crypto daemon │ │
│ │ --- DES and Triple DES EDE cipher algorithms
thanks for the information
|
|
|
| Back to top |
|
 |
nixnut
Bodhisattva
Joined: 09 Apr 2004
Posts: 10974
Location: the dutch mountains
|
| Posted: Thu Nov 22, 2007 5:32 pm Post subject: |
|
|
They are already enabled because other things depend on them. Look at the help screen to see which drivers depend on them
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered
talk is cheap. supply exceeds demand |
|
| Back to top |
|
|
buhofromepn
n00b
Joined: 22 Nov 2007
Posts: 2
|
| Posted: Mon Nov 26, 2007 4:27 am Post subject: ipsec0 and 2.6.22 without klips openswan |
|
|
thanks for the reply.
I have succesful ipsec sa vpns, but the tunnel does not function properly and /or the
route without ipsec0 does not function at all.
I tried 2 configurations end to end type=transport
and end to subnet type= tunnel
In either case the ping are not replied.
here is the evidence:
| Code: |
000 "mario-buho": 74.139.220.13---74.139.220.1...74.118.239.113---74.118.239.114===172.16.1.0/24; erouted; eroute owner: #2
000 "mario-buho": srcip=unset; dstip=unset; srcup=ipsec _updown; dstup=ipsec _updown;
000 "mario-buho": ike_life: 3600s; ipsec_life: 28800s; rekey_margin: 540s; rekey_fuzz: 100%; keyingtries: 0
000 "mario-buho": policy: PSK+ENCRYPT+TUNNEL+UP; prio: 32,24; interface: eth0; encap: esp;
000 "mario-buho": newest ISAKMP SA: #1; newest IPsec SA: #2;
000 "mario-buho": IKE algorithm newest: 3DES_CBC_192-MD5-MODP1536
000
000 #2: "mario-buho":500 STATE_QUICK_I2 (sent QI2, IPsec SA established); EVENT_SA_REPLACE in 27732s; newest IPSEC; eroute owner
000 #2: "mario-buho" esp.e819c8d@74.118.239.114 esp.96293ca0@74.139.220.13 tun.0@74.118.239.114 tun.0@64.139.220.13
000 #1: "mario-buho":500 STATE_MAIN_I4 (ISAKMP SA established); EVENT_SA_REPLACE in 2630s; newest ISAKMP; lastdpd=-1s(seq in:0 out:0)
|
the kernel version
Linux unconf-buho 2.6.22-gentoo-r9 and openswan-2.4.9-r1
how do we handle the routing issue without ipsec0 ?? |
|
| Back to top |
|
|
|
Networking & Security
