OpenCores
URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [rtos/] [ecos-3.0/] [packages/] [net/] [common/] [current/] [doc/] [ipsec.sgml] - Blame information for rev 786

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 786 skrzyp
2
 
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
 
26
27
 
28
29
  IPSEC for eCos
30
  
31
    
32
    The FreeBSD network stack which is part of
33
    eCos can be configured to use IPSEC to
34
    provide more secure communications between Internet hosts. IPSEC
35
    can be used with both IPv4 and IPv6.
36
    
37
  
38
  
39
    Installation and Configuration
40
    
41
    Due to the restrictions imposed by various countries on the
42
    exportation and importation of cryptographic software, it has been
43
    decided to distribute the crypto parts of FreeBSD IPSEC separately
44
    from the rest of eCos. Before IPSEC can be enabled the eCos
45
    package bsd_crypto must be installed. This package can be found on
46
    the eCosCentric server at
47
    
48
    ftp.ecoscentric.com:/pub/contrib. Once the package has been
49
    downloaded it must be installed using the
50
    ecosadmin.tcl script.
51
    
52
 
53
    
54
    When the bsd_crypto package has been installed, the building of
55
    IPSEC will automatically be enabled when the FreeBSD stack is
56
    used. It can be disabled using the configuration option
57
    CYGPKG_NET_IPSEC. There are no other
58
    configuration options for IPSEC as a whole.
59
    
60
 
61
    
62
    In order to use IPSEC, connections must be configured. This can be
63
    performed using setsockopt() calls. A more
64
    convenient way is the use the libipsec library
65
    from the KAME distribution. eCos
66
    contains a snapshot of this library, which is documented else
67
    where. The aim is to also port the
68
    racoon daemon to eCos in the near
69
    future.
70
    
71
 
72
    
73
    It should be noted that the FreeBSD stack in eCos is quite
74
    old. IPSEC and IPv6 have continued to develop. It is quite
75
    possible there could be interoperabilty problems when using the
76
    IPSEC implementation in eCos with more modern implementations.
77
    
78
 
79
    
80
    It should also be noted that IPSEC, libipsec etc are currently
81
    work in progress items.
82
    
83
  
84
  &net-ipsec-libipsec-libipsec-manpages-sgml;
85

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.