… | |
… | |
429 | appropriate error message. |
429 | appropriate error message. |
430 | |
430 | |
431 | TLS mode requires Net::SSLeay to be installed (it will be loaded |
431 | TLS mode requires Net::SSLeay to be installed (it will be loaded |
432 | automatically when you try to create a TLS handle): this module doesn't |
432 | automatically when you try to create a TLS handle): this module doesn't |
433 | have a dependency on that module, so if your module requires it, you have |
433 | have a dependency on that module, so if your module requires it, you have |
434 | to add the dependency yourself. |
434 | to add the dependency yourself. If Net::SSLeay cannot be loaded or is too |
|
|
435 | old, you get an C<EPROTO> error. |
435 | |
436 | |
436 | Unlike TCP, TLS has a server and client side: for the TLS server side, use |
437 | Unlike TCP, TLS has a server and client side: for the TLS server side, use |
437 | C<accept>, and for the TLS client side of a connection, use C<connect> |
438 | C<accept>, and for the TLS client side of a connection, use C<connect> |
438 | mode. |
439 | mode. |
439 | |
440 | |
… | |
… | |
495 | callback. |
496 | callback. |
496 | |
497 | |
497 | This callback will only be called on TLS shutdowns, not when the |
498 | This callback will only be called on TLS shutdowns, not when the |
498 | underlying handle signals EOF. |
499 | underlying handle signals EOF. |
499 | |
500 | |
500 | =item json => JSON or JSON::XS object |
501 | =item json => L<JSON>, L<JSON::PP> or L<JSON::XS> object |
501 | |
502 | |
502 | This is the json coder object used by the C<json> read and write types. |
503 | This is the json coder object used by the C<json> read and write types. |
503 | |
504 | |
504 | If you don't supply it, then AnyEvent::Handle will create and use a |
505 | If you don't supply it, then AnyEvent::Handle will create and use a |
505 | suitable one (on demand), which will write and expect UTF-8 encoded JSON |
506 | suitable one (on demand), which will write and expect UTF-8 encoded |
|
|
507 | JSON texts (either using L<JSON::XS> or L<JSON>). The written texts are |
|
|
508 | guaranteed not to contain any newline character. |
|
|
509 | |
|
|
510 | For security reasons, this encoder will likely I<not> handle numbers and |
|
|
511 | strings, only arrays and objects/hashes. The reason is that originally |
|
|
512 | JSON was self-delimited, but Dougles Crockford thought it was a splendid |
|
|
513 | idea to redefine JSON incompatibly, so this is no longer true. |
|
|
514 | |
|
|
515 | For protocols that used back-to-back JSON texts, this might lead to |
|
|
516 | run-ins, where two or more JSON texts will be interpreted as one JSON |
506 | texts. |
517 | text. |
507 | |
518 | |
|
|
519 | For this reason, if the default encoder uses L<JSON::XS>, it will default |
|
|
520 | to not allowing anything but arrays and objects/hashes, at least for the |
|
|
521 | forseeable future (it will change at some point). This might or might not |
|
|
522 | be true for the L<JSON> module, so this might cause a security issue. |
|
|
523 | |
|
|
524 | If you depend on either behaviour, you should create your own json object |
|
|
525 | and pass it in explicitly. |
|
|
526 | |
|
|
527 | =item cbor => L<CBOR::XS> object |
|
|
528 | |
|
|
529 | This is the cbor coder object used by the C<cbor> read and write types. |
|
|
530 | |
|
|
531 | If you don't supply it, then AnyEvent::Handle will create and use a |
|
|
532 | suitable one (on demand), which will write CBOR without using extensions, |
|
|
533 | if possible. |
|
|
534 | |
508 | Note that you are responsible to depend on the JSON module if you want to |
535 | Note that you are responsible to depend on the L<CBOR::XS> module if you |
509 | use this functionality, as AnyEvent does not have a dependency itself. |
536 | want to use this functionality, as AnyEvent does not have a dependency on |
|
|
537 | it itself. |
510 | |
538 | |
511 | =back |
539 | =back |
512 | |
540 | |
513 | =cut |
541 | =cut |
514 | |
542 | |
… | |
… | |
1044 | |
1072 | |
1045 | Encodes the given hash or array reference into a JSON object. Unless you |
1073 | Encodes the given hash or array reference into a JSON object. Unless you |
1046 | provide your own JSON object, this means it will be encoded to JSON text |
1074 | provide your own JSON object, this means it will be encoded to JSON text |
1047 | in UTF-8. |
1075 | in UTF-8. |
1048 | |
1076 | |
|
|
1077 | The default encoder might or might not handle every type of JSON value - |
|
|
1078 | it might be limited to arrays and objects for security reasons. See the |
|
|
1079 | C<json> constructor attribute for more details. |
|
|
1080 | |
1049 | JSON objects (and arrays) are self-delimiting, so you can write JSON at |
1081 | JSON objects (and arrays) are self-delimiting, so if you only use arrays |
1050 | one end of a handle and read them at the other end without using any |
1082 | and hashes, you can write JSON at one end of a handle and read them at the |
1051 | additional framing. |
1083 | other end without using any additional framing. |
1052 | |
1084 | |
1053 | The generated JSON text is guaranteed not to contain any newlines: While |
1085 | The JSON text generated by the default encoder is guaranteed not to |
1054 | this module doesn't need delimiters after or between JSON texts to be |
1086 | contain any newlines: While this module doesn't need delimiters after or |
1055 | able to read them, many other languages depend on that. |
1087 | between JSON texts to be able to read them, many other languages depend on |
|
|
1088 | them. |
1056 | |
1089 | |
1057 | A simple RPC protocol that interoperates easily with others is to send |
1090 | A simple RPC protocol that interoperates easily with other languages is |
1058 | JSON arrays (or objects, although arrays are usually the better choice as |
1091 | to send JSON arrays (or objects, although arrays are usually the better |
1059 | they mimic how function argument passing works) and a newline after each |
1092 | choice as they mimic how function argument passing works) and a newline |
1060 | JSON text: |
1093 | after each JSON text: |
1061 | |
1094 | |
1062 | $handle->push_write (json => ["method", "arg1", "arg2"]); # whatever |
1095 | $handle->push_write (json => ["method", "arg1", "arg2"]); # whatever |
1063 | $handle->push_write ("\012"); |
1096 | $handle->push_write ("\012"); |
1064 | |
1097 | |
1065 | An AnyEvent::Handle receiver would simply use the C<json> read type and |
1098 | An AnyEvent::Handle receiver would simply use the C<json> read type and |
… | |
… | |
1068 | $handle->push_read (json => sub { my $array = $_[1]; ... }); |
1101 | $handle->push_read (json => sub { my $array = $_[1]; ... }); |
1069 | |
1102 | |
1070 | Other languages could read single lines terminated by a newline and pass |
1103 | Other languages could read single lines terminated by a newline and pass |
1071 | this line into their JSON decoder of choice. |
1104 | this line into their JSON decoder of choice. |
1072 | |
1105 | |
|
|
1106 | =item cbor => $perl_scalar |
|
|
1107 | |
|
|
1108 | Encodes the given scalar into a CBOR value. Unless you provide your own |
|
|
1109 | L<CBOR::XS> object, this means it will be encoded to a CBOR string not |
|
|
1110 | using any extensions, if possible. |
|
|
1111 | |
|
|
1112 | CBOR values are self-delimiting, so you can write CBOR at one end of |
|
|
1113 | a handle and read them at the other end without using any additional |
|
|
1114 | framing. |
|
|
1115 | |
|
|
1116 | A simple nd very very fast RPC protocol that interoperates with |
|
|
1117 | other languages is to send CBOR and receive CBOR values (arrays are |
|
|
1118 | recommended): |
|
|
1119 | |
|
|
1120 | $handle->push_write (cbor => ["method", "arg1", "arg2"]); # whatever |
|
|
1121 | |
|
|
1122 | An AnyEvent::Handle receiver would simply use the C<cbor> read type: |
|
|
1123 | |
|
|
1124 | $handle->push_read (cbor => sub { my $array = $_[1]; ... }); |
|
|
1125 | |
1073 | =cut |
1126 | =cut |
1074 | |
1127 | |
1075 | sub json_coder() { |
1128 | sub json_coder() { |
1076 | eval { require JSON::XS; JSON::XS->new->utf8 } |
1129 | eval { require JSON::XS; JSON::XS->new->utf8 } |
1077 | || do { require JSON; JSON->new->utf8 } |
1130 | || do { require JSON::PP; JSON::PP->new->utf8 } |
1078 | } |
1131 | } |
1079 | |
1132 | |
1080 | register_write_type json => sub { |
1133 | register_write_type json => sub { |
1081 | my ($self, $ref) = @_; |
1134 | my ($self, $ref) = @_; |
1082 | |
1135 | |
1083 | my $json = $self->{json} ||= json_coder; |
1136 | ($self->{json} ||= json_coder) |
1084 | |
|
|
1085 | $json->encode ($ref) |
1137 | ->encode ($ref) |
|
|
1138 | }; |
|
|
1139 | |
|
|
1140 | sub cbor_coder() { |
|
|
1141 | require CBOR::XS; |
|
|
1142 | CBOR::XS->new |
|
|
1143 | } |
|
|
1144 | |
|
|
1145 | register_write_type cbor => sub { |
|
|
1146 | my ($self, $scalar) = @_; |
|
|
1147 | |
|
|
1148 | ($self->{cbor} ||= cbor_coder) |
|
|
1149 | ->encode ($scalar) |
1086 | }; |
1150 | }; |
1087 | |
1151 | |
1088 | =item storable => $reference |
1152 | =item storable => $reference |
1089 | |
1153 | |
1090 | Freezes the given reference using L<Storable> and writes it to the |
1154 | Freezes the given reference using L<Storable> and writes it to the |
… | |
… | |
1484 | |
1548 | |
1485 | register_read_type line => sub { |
1549 | register_read_type line => sub { |
1486 | my ($self, $cb, $eol) = @_; |
1550 | my ($self, $cb, $eol) = @_; |
1487 | |
1551 | |
1488 | if (@_ < 3) { |
1552 | if (@_ < 3) { |
1489 | # this is more than twice as fast as the generic code below |
1553 | # this is faster then the generic code below |
1490 | sub { |
1554 | sub { |
1491 | $_[0]{rbuf} =~ s/^([^\015\012]*)(\015?\012)// or return; |
1555 | (my $pos = index $_[0]{rbuf}, "\012") >= 0 |
|
|
1556 | or return; |
1492 | |
1557 | |
|
|
1558 | (my $str = substr $_[0]{rbuf}, 0, $pos + 1, "") =~ s/(\015?\012)\Z// or die; |
1493 | $cb->($_[0], "$1", "$2"); |
1559 | $cb->($_[0], $str, "$1"); |
1494 | 1 |
1560 | 1 |
1495 | } |
1561 | } |
1496 | } else { |
1562 | } else { |
1497 | $eol = quotemeta $eol unless ref $eol; |
1563 | $eol = quotemeta $eol unless ref $eol; |
1498 | $eol = qr|^(.*?)($eol)|s; |
1564 | $eol = qr|^(.*?)($eol)|s; |
… | |
… | |
1661 | =item json => $cb->($handle, $hash_or_arrayref) |
1727 | =item json => $cb->($handle, $hash_or_arrayref) |
1662 | |
1728 | |
1663 | Reads a JSON object or array, decodes it and passes it to the |
1729 | Reads a JSON object or array, decodes it and passes it to the |
1664 | callback. When a parse error occurs, an C<EBADMSG> error will be raised. |
1730 | callback. When a parse error occurs, an C<EBADMSG> error will be raised. |
1665 | |
1731 | |
1666 | If a C<json> object was passed to the constructor, then that will be used |
1732 | If a C<json> object was passed to the constructor, then that will be |
1667 | for the final decode, otherwise it will create a JSON coder expecting UTF-8. |
1733 | used for the final decode, otherwise it will create a L<JSON::XS> or |
|
|
1734 | L<JSON::PP> coder object expecting UTF-8. |
1668 | |
1735 | |
1669 | This read type uses the incremental parser available with JSON version |
1736 | This read type uses the incremental parser available with JSON version |
1670 | 2.09 (and JSON::XS version 2.2) and above. You have to provide a |
1737 | 2.09 (and JSON::XS version 2.2) and above. |
1671 | dependency on your own: this module will load the JSON module, but |
|
|
1672 | AnyEvent does not depend on it itself. |
|
|
1673 | |
1738 | |
1674 | Since JSON texts are fully self-delimiting, the C<json> read and write |
1739 | Since JSON texts are fully self-delimiting, the C<json> read and write |
1675 | types are an ideal simple RPC protocol: just exchange JSON datagrams. See |
1740 | types are an ideal simple RPC protocol: just exchange JSON datagrams. See |
1676 | the C<json> write type description, above, for an actual example. |
1741 | the C<json> write type description, above, for an actual example. |
1677 | |
1742 | |
… | |
… | |
1681 | my ($self, $cb) = @_; |
1746 | my ($self, $cb) = @_; |
1682 | |
1747 | |
1683 | my $json = $self->{json} ||= json_coder; |
1748 | my $json = $self->{json} ||= json_coder; |
1684 | |
1749 | |
1685 | my $data; |
1750 | my $data; |
1686 | my $rbuf = \$self->{rbuf}; |
|
|
1687 | |
1751 | |
1688 | sub { |
1752 | sub { |
1689 | my $ref = eval { $json->incr_parse ($_[0]{rbuf}) }; |
1753 | my $ref = eval { $json->incr_parse ($_[0]{rbuf}) }; |
1690 | |
1754 | |
1691 | if ($ref) { |
1755 | if ($ref) { |
… | |
… | |
1705 | |
1769 | |
1706 | () |
1770 | () |
1707 | } else { |
1771 | } else { |
1708 | $_[0]{rbuf} = ""; |
1772 | $_[0]{rbuf} = ""; |
1709 | |
1773 | |
|
|
1774 | () |
|
|
1775 | } |
|
|
1776 | } |
|
|
1777 | }; |
|
|
1778 | |
|
|
1779 | =item cbor => $cb->($handle, $scalar) |
|
|
1780 | |
|
|
1781 | Reads a CBOR value, decodes it and passes it to the callback. When a parse |
|
|
1782 | error occurs, an C<EBADMSG> error will be raised. |
|
|
1783 | |
|
|
1784 | If a L<CBOR::XS> object was passed to the constructor, then that will be |
|
|
1785 | used for the final decode, otherwise it will create a CBOR coder without |
|
|
1786 | enabling any options. |
|
|
1787 | |
|
|
1788 | You have to provide a dependency to L<CBOR::XS> on your own: this module |
|
|
1789 | will load the L<CBOR::XS> module, but AnyEvent does not depend on it |
|
|
1790 | itself. |
|
|
1791 | |
|
|
1792 | Since CBOR values are fully self-delimiting, the C<cbor> read and write |
|
|
1793 | types are an ideal simple RPC protocol: just exchange CBOR datagrams. See |
|
|
1794 | the C<cbor> write type description, above, for an actual example. |
|
|
1795 | |
|
|
1796 | =cut |
|
|
1797 | |
|
|
1798 | register_read_type cbor => sub { |
|
|
1799 | my ($self, $cb) = @_; |
|
|
1800 | |
|
|
1801 | my $cbor = $self->{cbor} ||= cbor_coder; |
|
|
1802 | |
|
|
1803 | my $data; |
|
|
1804 | |
|
|
1805 | sub { |
|
|
1806 | my (@value) = eval { $cbor->incr_parse ($_[0]{rbuf}) }; |
|
|
1807 | |
|
|
1808 | if (@value) { |
|
|
1809 | $cb->($_[0], @value); |
|
|
1810 | |
|
|
1811 | 1 |
|
|
1812 | } elsif ($@) { |
|
|
1813 | # error case |
|
|
1814 | $cbor->incr_reset; |
|
|
1815 | |
|
|
1816 | $_[0]->_error (Errno::EBADMSG); |
|
|
1817 | |
|
|
1818 | () |
|
|
1819 | } else { |
1710 | () |
1820 | () |
1711 | } |
1821 | } |
1712 | } |
1822 | } |
1713 | }; |
1823 | }; |
1714 | |
1824 | |
… | |
… | |
1752 | }); |
1862 | }); |
1753 | } |
1863 | } |
1754 | |
1864 | |
1755 | 1 |
1865 | 1 |
1756 | } |
1866 | } |
|
|
1867 | }; |
|
|
1868 | |
|
|
1869 | =item tls_detect => $cb->($handle, $detect, $major, $minor) |
|
|
1870 | |
|
|
1871 | Checks the input stream for a valid SSL or TLS handshake TLSPaintext |
|
|
1872 | record without consuming anything. Only SSL version 3 or higher |
|
|
1873 | is handled, up to the fictituous protocol 4.x (but both SSL3+ and |
|
|
1874 | SSL2-compatible framing is supported). |
|
|
1875 | |
|
|
1876 | If it detects that the input data is likely TLS, it calls the callback |
|
|
1877 | with a true value for C<$detect> and the (on-wire) TLS version as second |
|
|
1878 | and third argument (C<$major> is C<3>, and C<$minor> is 0..3 for SSL |
|
|
1879 | 3.0, TLS 1.0, 1.1 and 1.2, respectively). If it detects the input to |
|
|
1880 | be definitely not TLS, it calls the callback with a false value for |
|
|
1881 | C<$detect>. |
|
|
1882 | |
|
|
1883 | The callback could use this information to decide whether or not to start |
|
|
1884 | TLS negotiation. |
|
|
1885 | |
|
|
1886 | In all cases the data read so far is passed to the following read |
|
|
1887 | handlers. |
|
|
1888 | |
|
|
1889 | Usually you want to use the C<tls_autostart> read type instead. |
|
|
1890 | |
|
|
1891 | If you want to design a protocol that works in the presence of TLS |
|
|
1892 | dtection, make sure that any non-TLS data doesn't start with the octet 22 |
|
|
1893 | (ASCII SYN, 16 hex) or 128-255 (i.e. highest bit set). The checks this |
|
|
1894 | read type does are a bit more strict, but might losen in the future to |
|
|
1895 | accomodate protocol changes. |
|
|
1896 | |
|
|
1897 | This read type does not rely on L<AnyEvent::TLS> (and thus, not on |
|
|
1898 | L<Net::SSLeay>). |
|
|
1899 | |
|
|
1900 | =item tls_autostart => $tls[, $tls_ctx] |
|
|
1901 | |
|
|
1902 | Tries to detect a valid SSL or TLS handshake. If one is detected, it tries |
|
|
1903 | to start tls by calling C<starttls> with the given arguments. |
|
|
1904 | |
|
|
1905 | In practise, C<$tls> must be C<accept>, or a Net::SSLeay context that has |
|
|
1906 | been configured to accept, as servers do not normally send a handshake on |
|
|
1907 | their own and ths cannot be detected in this way. |
|
|
1908 | |
|
|
1909 | See C<tls_detect> above for more details. |
|
|
1910 | |
|
|
1911 | Example: give the client a chance to start TLS before accepting a text |
|
|
1912 | line. |
|
|
1913 | |
|
|
1914 | $hdl->push_read (tls_detect => "accept"); |
|
|
1915 | $hdl->push_read (line => sub { |
|
|
1916 | print "received ", ($_[0]{tls} ? "encrypted" : "cleartext"), " <$_[1]>\n"; |
|
|
1917 | }); |
|
|
1918 | |
|
|
1919 | =cut |
|
|
1920 | |
|
|
1921 | register_read_type tls_detect => sub { |
|
|
1922 | my ($self, $cb) = @_; |
|
|
1923 | |
|
|
1924 | sub { |
|
|
1925 | # this regex matches a full or partial tls record |
|
|
1926 | if ( |
|
|
1927 | # ssl3+: type(22=handshake) major(=3) minor(any) length_hi |
|
|
1928 | $self->{rbuf} =~ /^(?:\z| \x16 (\z| [\x03\x04] (?:\z| . (?:\z| [\x00-\x40] ))))/xs |
|
|
1929 | # ssl2 comapatible: len_hi len_lo type(1) major minor dummy(forlength) |
|
|
1930 | or $self->{rbuf} =~ /^(?:\z| [\x80-\xff] (?:\z| . (?:\z| \x01 (\z| [\x03\x04] (?:\z| . (?:\z| . ))))))/xs |
|
|
1931 | ) { |
|
|
1932 | return if 3 != length $1; # partial match, can't decide yet |
|
|
1933 | |
|
|
1934 | # full match, valid TLS record |
|
|
1935 | my ($major, $minor) = unpack "CC", $1; |
|
|
1936 | $cb->($self, "accept", $major + $minor * 0.1); |
|
|
1937 | } else { |
|
|
1938 | # mismatch == guaranteed not TLS |
|
|
1939 | $cb->($self, undef); |
|
|
1940 | } |
|
|
1941 | |
|
|
1942 | 1 |
|
|
1943 | } |
|
|
1944 | }; |
|
|
1945 | |
|
|
1946 | register_read_type tls_autostart => sub { |
|
|
1947 | my ($self, @tls) = @_; |
|
|
1948 | |
|
|
1949 | $RH{tls_detect}($self, sub { |
|
|
1950 | return unless $_[1]; |
|
|
1951 | $_[0]->starttls (@tls); |
|
|
1952 | }) |
1757 | }; |
1953 | }; |
1758 | |
1954 | |
1759 | =back |
1955 | =back |
1760 | |
1956 | |
1761 | =item custom read types - Package::anyevent_read_type $handle, $cb, @args |
1957 | =item custom read types - Package::anyevent_read_type $handle, $cb, @args |
… | |
… | |
1885 | sub _dotls { |
2081 | sub _dotls { |
1886 | my ($self) = @_; |
2082 | my ($self) = @_; |
1887 | |
2083 | |
1888 | my $tmp; |
2084 | my $tmp; |
1889 | |
2085 | |
1890 | if (length $self->{_tls_wbuf}) { |
2086 | while (length $self->{_tls_wbuf}) { |
1891 | while (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) > 0) { |
2087 | if (($tmp = Net::SSLeay::write ($self->{tls}, $self->{_tls_wbuf})) <= 0) { |
1892 | substr $self->{_tls_wbuf}, 0, $tmp, ""; |
2088 | $tmp = Net::SSLeay::get_error ($self->{tls}, $tmp); |
|
|
2089 | |
|
|
2090 | return $self->_tls_error ($tmp) |
|
|
2091 | if $tmp != $ERROR_WANT_READ |
|
|
2092 | && ($tmp != $ERROR_SYSCALL || $!); |
|
|
2093 | |
|
|
2094 | last; |
1893 | } |
2095 | } |
1894 | |
2096 | |
1895 | $tmp = Net::SSLeay::get_error ($self->{tls}, $tmp); |
2097 | substr $self->{_tls_wbuf}, 0, $tmp, ""; |
1896 | return $self->_tls_error ($tmp) |
|
|
1897 | if $tmp != $ERROR_WANT_READ |
|
|
1898 | && ($tmp != $ERROR_SYSCALL || $!); |
|
|
1899 | } |
2098 | } |
1900 | |
2099 | |
1901 | while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) { |
2100 | while (defined ($tmp = Net::SSLeay::read ($self->{tls}))) { |
1902 | unless (length $tmp) { |
2101 | unless (length $tmp) { |
1903 | $self->{_on_starttls} |
2102 | $self->{_on_starttls} |
… | |
… | |
1917 | $self->{_tls_rbuf} .= $tmp; |
2116 | $self->{_tls_rbuf} .= $tmp; |
1918 | $self->_drain_rbuf; |
2117 | $self->_drain_rbuf; |
1919 | $self->{tls} or return; # tls session might have gone away in callback |
2118 | $self->{tls} or return; # tls session might have gone away in callback |
1920 | } |
2119 | } |
1921 | |
2120 | |
1922 | $tmp = Net::SSLeay::get_error ($self->{tls}, -1); |
2121 | $tmp = Net::SSLeay::get_error ($self->{tls}, -1); # -1 is not neccessarily correct, but Net::SSLeay doesn't tell us |
1923 | return $self->_tls_error ($tmp) |
2122 | return $self->_tls_error ($tmp) |
1924 | if $tmp != $ERROR_WANT_READ |
2123 | if $tmp != $ERROR_WANT_READ |
1925 | && ($tmp != $ERROR_SYSCALL || $!); |
2124 | && ($tmp != $ERROR_SYSCALL || $!); |
1926 | |
2125 | |
1927 | while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) { |
2126 | while (length ($tmp = Net::SSLeay::BIO_read ($self->{_wbio}))) { |
… | |
… | |
1937 | |
2136 | |
1938 | =item $handle->starttls ($tls[, $tls_ctx]) |
2137 | =item $handle->starttls ($tls[, $tls_ctx]) |
1939 | |
2138 | |
1940 | Instead of starting TLS negotiation immediately when the AnyEvent::Handle |
2139 | Instead of starting TLS negotiation immediately when the AnyEvent::Handle |
1941 | object is created, you can also do that at a later time by calling |
2140 | object is created, you can also do that at a later time by calling |
1942 | C<starttls>. |
2141 | C<starttls>. See the C<tls> constructor argument for general info. |
1943 | |
2142 | |
1944 | Starting TLS is currently an asynchronous operation - when you push some |
2143 | Starting TLS is currently an asynchronous operation - when you push some |
1945 | write data and then call C<< ->starttls >> then TLS negotiation will start |
2144 | write data and then call C<< ->starttls >> then TLS negotiation will start |
1946 | immediately, after which the queued write data is then sent. |
2145 | immediately, after which the queued write data is then sent. This might |
|
|
2146 | change in future versions, so best make sure you have no outstanding write |
|
|
2147 | data when calling this method. |
1947 | |
2148 | |
1948 | The first argument is the same as the C<tls> constructor argument (either |
2149 | The first argument is the same as the C<tls> constructor argument (either |
1949 | C<"connect">, C<"accept"> or an existing Net::SSLeay object). |
2150 | C<"connect">, C<"accept"> or an existing Net::SSLeay object). |
1950 | |
2151 | |
1951 | The second argument is the optional C<AnyEvent::TLS> object that is used |
2152 | The second argument is the optional C<AnyEvent::TLS> object that is used |
… | |
… | |
1973 | my ($self, $tls, $ctx) = @_; |
2174 | my ($self, $tls, $ctx) = @_; |
1974 | |
2175 | |
1975 | Carp::croak "It is an error to call starttls on an AnyEvent::Handle object while TLS is already active, caught" |
2176 | Carp::croak "It is an error to call starttls on an AnyEvent::Handle object while TLS is already active, caught" |
1976 | if $self->{tls}; |
2177 | if $self->{tls}; |
1977 | |
2178 | |
|
|
2179 | unless (defined $AnyEvent::TLS::VERSION) { |
|
|
2180 | eval { |
|
|
2181 | require Net::SSLeay; |
|
|
2182 | require AnyEvent::TLS; |
|
|
2183 | 1 |
|
|
2184 | } or return $self->_error (Errno::EPROTO, 1, "TLS support not available on this system"); |
|
|
2185 | } |
|
|
2186 | |
1978 | $self->{tls} = $tls; |
2187 | $self->{tls} = $tls; |
1979 | $self->{tls_ctx} = $ctx if @_ > 2; |
2188 | $self->{tls_ctx} = $ctx if @_ > 2; |
1980 | |
2189 | |
1981 | return unless $self->{fh}; |
2190 | return unless $self->{fh}; |
1982 | |
2191 | |
1983 | require Net::SSLeay; |
|
|
1984 | |
|
|
1985 | $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL (); |
2192 | $ERROR_SYSCALL = Net::SSLeay::ERROR_SYSCALL (); |
1986 | $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ (); |
2193 | $ERROR_WANT_READ = Net::SSLeay::ERROR_WANT_READ (); |
1987 | |
2194 | |
1988 | $tls = delete $self->{tls}; |
2195 | $tls = delete $self->{tls}; |
1989 | $ctx = $self->{tls_ctx}; |
2196 | $ctx = $self->{tls_ctx}; |
1990 | |
2197 | |
1991 | local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session |
2198 | local $Carp::CarpLevel = 1; # skip ourselves when creating a new context or session |
1992 | |
2199 | |
1993 | if ("HASH" eq ref $ctx) { |
2200 | if ("HASH" eq ref $ctx) { |
1994 | require AnyEvent::TLS; |
|
|
1995 | |
|
|
1996 | if ($ctx->{cache}) { |
2201 | if ($ctx->{cache}) { |
1997 | my $key = $ctx+0; |
2202 | my $key = $ctx+0; |
1998 | $ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx; |
2203 | $ctx = $TLS_CACHE{$key} ||= new AnyEvent::TLS %$ctx; |
1999 | } else { |
2204 | } else { |
2000 | $ctx = new AnyEvent::TLS %$ctx; |
2205 | $ctx = new AnyEvent::TLS %$ctx; |
… | |
… | |
2233 | handles requests until the server gets some QUIT command, causing it to |
2438 | handles requests until the server gets some QUIT command, causing it to |
2234 | close the connection first (highly desirable for a busy TCP server). A |
2439 | close the connection first (highly desirable for a busy TCP server). A |
2235 | client dropping the connection is an error, which means this variant can |
2440 | client dropping the connection is an error, which means this variant can |
2236 | detect an unexpected detection close. |
2441 | detect an unexpected detection close. |
2237 | |
2442 | |
2238 | To handle this case, always make sure you have a on-empty read queue, by |
2443 | To handle this case, always make sure you have a non-empty read queue, by |
2239 | pushing the "read request start" handler on it: |
2444 | pushing the "read request start" handler on it: |
2240 | |
2445 | |
2241 | # we assume a request starts with a single line |
2446 | # we assume a request starts with a single line |
2242 | my @start_request; @start_request = (line => sub { |
2447 | my @start_request; @start_request = (line => sub { |
2243 | my ($hdl, $line) = @_; |
2448 | my ($hdl, $line) = @_; |