| /freebsd/crypto/openssl/test/ssl-tests/ |
| H A D | protocol_version.pm | 46 my @protocols = @{$protref};
50 foreach my $i (0..$#protocols) {
62 my @protocols = @{$protref};
66 foreach my $i (0..$#protocols) {
68 && ($protocols[$i] ne "TLSv1.3"
121 my @protocols;
127 @protocols = $dtls ? @dtls_protocols_fips : @tls_protocols_fips;
133 @protocols = $dtls ? @dtls_protocols : @tls_protocols;
156 \@protocols);
229 my @protocols;
[all …]
|
| H A D | 04-client_auth.cnf.in | 16 my @protocols;
21 @protocols = (undef, "TLSv1.2", "DTLSv1.2");
24 @protocols = (undef, "SSLv3", "TLSv1", "TLSv1.1", "TLSv1.2", "DTLSv1", "DTLSv1.2");
31 foreach (0..$#protocols) {
32 my $protocol = $protocols[$_];
|
| /freebsd/sys/contrib/device-tree/Bindings/mailbox/ |
| H A D | arm,mhuv2.yaml | 28 protocols. The transport protocols determine the method of data transmission
31 Following are the possible transport protocols.
83 arm,mhuv2-protocols:
88 be used for various transport protocols.
91 used in various transport protocols. The entries in this property shall be
114 arm,mhuv2-protocols = <0 2>, <1 1>, <1 5>, <1 7>;
117 The above example defines the protocols of an ARM MHUv2 mailbox
139 From the example given above for arm,mhuv2-protocols, here is how a client
164 - arm,mhuv2-protocols
169 # Multiple transport protocols implemented by the mailbox controllers
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | netintro.4 | 47 .Em protocols ,
51 All network protocols are associated with a specific
62 A protocol family is normally comprised of a number of protocols, one per
67 protocols supporting the same socket abstraction.
74 Protocols normally accept only one type of address format,
79 All protocols are expected to support
105 .Sh PROTOCOLS
108 protocols, the Xerox Network Systems(tm) protocols,
111 protocols.
150 #define AF_NS 6 /* Xerox NS protocols */
[all …]
|
| H A D | ipsec.4 | 55 is a set of protocols,
134 Key exchange protocols are beyond what is necessary in the kernel and
220 protocols are configured for use, all protocols are included in the system.
221 To selectively enable/disable protocols, use
307 .Sh PROTOCOLS
314 protocols and therefore supports most of the protocols defined upon
315 those IP-layer protocols.
320 protocols may behave differently with
380 The protocols drew heavily on the
384 protocols.
[all …]
|
| /freebsd/lib/libsys/ |
| H A D | socket.2 | 56 PF_LOCAL Host-internal protocols (alias for PF_UNIX),
57 PF_UNIX Host-internal protocols,
58 PF_INET Internet version 4 protocols,
59 PF_INET6 Internet version 6 protocols,
64 PF_NETLINK Netlink protocols,
65 PF_BLUETOOTH Bluetooth protocols,
110 sockets provide access to internal network protocols and interfaces.
134 that many protocols may exist, in which case a particular protocol
141 .Xr protocols 5 .
183 The communications protocols used to implement a
[all …]
|
| /freebsd/lib/libc/net/ |
| H A D | getprotoent.3 | 63 .Pa /etc/protocols .
121 .Bl -tag -width /etc/protocols -compact
122 .It Pa /etc/protocols
125 .Xr protocols 5
141 protocols are currently understood.
|
| /freebsd/share/doc/smm/18.net/ |
| H A D | 9.t | 35 The lowest layer in the set of protocols which comprise a
75 Each protocol family must have one or more ``lowest level'' protocols.
76 These protocols deal with internetwork addressing and are responsible
78 modules. In the PUP model [Boggs78] these protocols are termed Level
79 1 protocols,
80 in the ISO model, network layer protocols. In this system each such
|
| H A D | 6.t | 38 abstraction, those provided by the communication protocols,
40 protocols are normally layered into two or more individual
88 the socket data structure for later use. Protocols are defined
93 Protocols control this data structure, which normally includes a
129 The state of a socket is manipulated both by the protocols
177 used by the protocols in controlling the flow of data.
263 and a set of protocols which implement various socket types within the domain
282 After that time, the domain structure is used to locate protocols
288 Protocols are described by a set of entry points and certain
323 Protocols pass data between themselves as chains of mbufs using
[all …]
|
| H A D | 7.t | 36 protocols is through the \fIpr_usrreq\fP routine defined in the
59 /* begin for protocols internal use */
115 may vary depending on the protocol. Virtual circuit protocols,
117 TCP connection. Datagram protocols, such as UDP [Postel80], simply
244 not the user. No protocols currently use this facility.
250 left to the protocol modules. No protocols currently use this facility.
|
| H A D | e.t | 29 .\".ds RH "Trailer protocols
33 \s+2Trailer protocols\s0
60 one or more headers used by the high level protocols.
108 Clearly, trailer protocols require cooperation between
|
| H A D | 3.t | 39 required interpretation only by the protocols which ``controlled''
42 protocols (a \fIprotocol family\fP), and those used for rendezvous
48 which new protocols and hardware could be easily be supported.
|
| /freebsd/usr.bin/sockstat/ |
| H A D | sockstat.1 | 39 .Op Fl P Ar protocols
93 .It Fl P Ar protocols
95 .Ar protocols .
97 .Ar protocols
100 .Xr protocols 5 .
236 .Xr protocols 5
|
| /freebsd/share/doc/psd/26.rpcrfc/ |
| H A D | rpc.rfc.ms | 48 program in order to be forward compatible with changing protocols.
94 The RPC protocol is independent of transport protocols. That is, RPC
139 connection-oriented protocols. For example, a request-reply protocol
165 Several different authentication protocols can be supported. A field
167 information on specific authentication protocols can be found in the
168 \fIAuthentication Protocols\fP\,
205 version number of 1. Because most new protocols evolve into better,
206 stable, and mature protocols, a version field of the call message
208 Version numbers make speaking old and new protocols through the same
217 Just as remote program protocols may change over several versions,
[all …]
|
| /freebsd/share/man/man5/ |
| H A D | bluetooth.protocols.5 | 25 .\" $Id: bluetooth.protocols.5,v 1.1 2003/05/20 22:52:39 max Exp $
31 .Nm bluetooth.protocols
35 .Pa /etc/bluetooth/protocols
56 .It Pa /etc/bluetooth/protocols
|
| H A D | protocols.5 | 32 .Nm protocols
57 .Bl -tag -width /etc/protocols -compact
58 .It Pa /etc/protocols
82 describing the "known protocols used in the DARPA Internet".
|
| /freebsd/share/doc/papers/beyond4.3/ |
| H A D | beyond43.ms | 67 much as multiple networking protocols are supported by 4.3BSD.
168 and an implementation of the ISO OSI network protocols
195 A kernel version of the OSI IP and ES-IS protocols must be produced.
196 We will implement the kernel version of these protocols.
206 that the interoperability of the ISODE and BSD kernel protocols
208 Testing is crucial because an openly available version of GOSIP protocols
249 Improvements to the TCP/IP Networking Protocols
262 and standard protocols.
298 As with networking protocols,
302 file system protocols, just as it is necessary to run several
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | SSL_CTX_set_alpn_select_cb.pod | 53 set the list of protocols available to be negotiated. The B<protos> must be in
56 protocols and no ALPN extension will be sent to the server.
70 SSL_select_next_proto() is a helper function used to select protocols. It
94 server's advertised protocols are provided in B<in> and B<inlen>. The
102 when a TLS server needs a list of supported protocols for Next Protocol
120 this function need not be a member of the list of supported protocols
181 ALPN protocol not selected, e.g., because no ALPN protocols are configured for
|
| H A D | SSL_CTX_new.pod | 126 The supported protocols are SSLv3, TLSv1, TLSv1.1, TLSv1.2 and TLSv1.3.
163 Currently supported protocols are DTLS 1.0 and DTLS 1.2.
186 If you want to limit the supported protocols for the version flexible
192 allow newer protocols like TLS 1.0, TLS 1.1, TLS 1.2 or TLS 1.3.
194 The list of protocols available can also be limited using the
200 protocols they support. When disabling a protocol, make sure that you also
|
| /freebsd/share/doc/psd/05.sysman/ |
| H A D | 2.3.t | 42 using the Xerox Network Systems protocols.
45 Socket types and protocols
98 no standard protocols to provide SOCK_RDM or SOCK_SEQPACKET sockets exist.
111 One of several possible protocols may be selected using identifiers
312 Sockets, and their underlying communication protocols, may
368 Socket types and protocols
405 and enables user-level implementations of special-purpose protocols
406 such as inter-gateway routing protocols.
|
| /freebsd/sys/contrib/dev/iwlwifi/mvm/ |
| H A D | time-sync.c | 128 int iwl_mvm_time_sync_config(struct iwl_mvm *mvm, const u8 *addr, u32 protocols) in iwl_mvm_time_sync_config() argument
149 if (protocols & ~(IWL_TIME_SYNC_PROTOCOL_TM | in iwl_mvm_time_sync_config()
153 cmd.protocols = cpu_to_le32(protocols); in iwl_mvm_time_sync_config()
164 mvm->time_sync.active = protocols != 0; in iwl_mvm_time_sync_config()
|
| /freebsd/usr.bin/getent/ |
| H A D | getent.1 | 66 .It Li protocols Ta name protocol [alias ...]
111 Show entry for TCP from the protocols database:
113 $ getent protocols tcp
131 .Xr protocols 5 ,
|
| /freebsd/share/doc/smm/01.setup/ |
| H A D | 5.t | 36 protocols IP, ICMP, TCP, and UDP. These protocols may be used
40 kernel (communication protocols) and user programs (user
43 \*(4B also supports the Xerox Network Systems (NS) protocols.
45 and other protocols such as Courier run at the user level.
46 \*(4B provides some support for the ISO OSI protocols CLNP
48 complete the application protocols such as X.400 and X.500.
52 protocols, define the INET option.
324 /etc/protocols \fIprotocols\fP\|(5) protocol names
|
| /freebsd/share/doc/psd/21.ipc/ |
| H A D | 3.t | 48 facilities support the Internet protocols
49 and the Xerox NS protocols,
118 Because of the differences in these databases and their access protocols,
226 For protocols, which are defined in \fI/etc/protocols\fP,
241 In the NS domain, protocols are indicated by the "client type"
306 Internet protocols and addressing scheme we would be forced to add
|
| /freebsd/usr.sbin/ppp/ |
| H A D | README.nat | 69 A second disadvantage is that "IP encoding" protocols, which send IP
73 protocols. This frees users from depending on using the ftp passive
77 The implementation supports all standard, non-encoding TCP and UDP protocols.
78 Examples of these protocols are http, gopher and telnet. The standard UDP
155 the number of NAT links open for different protocols.
164 This will allow rsh, RPC and other specialised protocols to work
251 occasional IP-encoding protocols always need workarounds (hacks).
252 Users who are interested in supporting new IP-encoding protocols
|