BIO_s_mem.pod 8.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209
  1. =pod
  2. =head1 NAME
  3. BIO_s_secmem, BIO_s_dgram_mem,
  4. BIO_s_mem, BIO_set_mem_eof_return, BIO_get_mem_data, BIO_set_mem_buf,
  5. BIO_get_mem_ptr, BIO_new_mem_buf - memory BIO
  6. =head1 SYNOPSIS
  7. #include <openssl/bio.h>
  8. const BIO_METHOD *BIO_s_mem(void);
  9. const BIO_METHOD *BIO_s_dgram_mem(void);
  10. const BIO_METHOD *BIO_s_secmem(void);
  11. BIO_set_mem_eof_return(BIO *b, int v);
  12. long BIO_get_mem_data(BIO *b, char **pp);
  13. BIO_set_mem_buf(BIO *b, BUF_MEM *bm, int c);
  14. BIO_get_mem_ptr(BIO *b, BUF_MEM **pp);
  15. BIO *BIO_new_mem_buf(const void *buf, int len);
  16. =head1 DESCRIPTION
  17. BIO_s_mem() returns the memory BIO method function.
  18. A memory BIO is a source/sink BIO which uses memory for its I/O. Data
  19. written to a memory BIO is stored in a BUF_MEM structure which is extended
  20. as appropriate to accommodate the stored data.
  21. BIO_s_secmem() is like BIO_s_mem() except that the secure heap is used
  22. for buffer storage.
  23. BIO_s_dgram_mem() is a memory BIO that respects datagram semantics. A single
  24. call to L<BIO_write(3)> will write a single datagram to the memory BIO. A
  25. subsequent call to L<BIO_read(3)> will read the data in that datagram. The
  26. L<BIO_read(3)> call will never return more data than was written in the original
  27. L<BIO_write(3)> call even if there were subsequent L<BIO_write(3)> calls that
  28. wrote more datagrams. Each successive call to L<BIO_read(3)> will read the next
  29. datagram. If a L<BIO_read(3)> call supplies a read buffer that is smaller than
  30. the size of the datagram, then the read buffer will be completely filled and the
  31. remaining data from the datagram will be discarded.
  32. It is not possible to write a zero length datagram. Calling L<BIO_write(3)> in
  33. this case will return 0 and no datagrams will be written. Calling L<BIO_read(3)>
  34. when there are no datagrams in the BIO to read will return a negative result and
  35. the "retry" flags will be set (i.e. calling L<BIO_should_retry(3)> will return
  36. true). A datagram mem BIO will never return true from L<BIO_eof(3)>.
  37. Any data written to a memory BIO can be recalled by reading from it.
  38. Unless the memory BIO is read only any data read from it is deleted from
  39. the BIO.
  40. Memory BIOs except BIO_s_dgram_mem() support BIO_gets() and BIO_puts().
  41. BIO_s_dgram_mem() supports L<BIO_sendmmsg(3)> and L<BIO_recvmmsg(3)> calls
  42. and calls related to B<BIO_ADDR> and MTU handling similarly to the
  43. L<BIO_s_dgram_pair(3)>.
  44. If the BIO_CLOSE flag is set when a memory BIO is freed then the underlying
  45. BUF_MEM structure is also freed.
  46. Calling BIO_reset() on a read write memory BIO clears any data in it if the
  47. flag BIO_FLAGS_NONCLEAR_RST is not set, otherwise it just restores the read
  48. pointer to the state it was just after the last write was performed and the
  49. data can be read again. On a read only BIO it similarly restores the BIO to
  50. its original state and the read only data can be read again.
  51. BIO_eof() is true if no data is in the BIO.
  52. BIO_ctrl_pending() returns the number of bytes currently stored.
  53. BIO_set_mem_eof_return() sets the behaviour of memory BIO B<b> when it is
  54. empty. If the B<v> is zero then an empty memory BIO will return EOF (that is
  55. it will return zero and BIO_should_retry(b) will be false. If B<v> is non
  56. zero then it will return B<v> when it is empty and it will set the read retry
  57. flag (that is BIO_read_retry(b) is true). To avoid ambiguity with a normal
  58. positive return value B<v> should be set to a negative value, typically -1.
  59. Calling this macro will fail for datagram mem BIOs.
  60. BIO_get_mem_data() sets *B<pp> to a pointer to the start of the memory BIOs data
  61. and returns the total amount of data available. It is implemented as a macro.
  62. Note the pointer returned by this call is informative, no transfer of ownership
  63. of this memory is implied. See notes on BIO_set_close().
  64. BIO_set_mem_buf() sets the internal BUF_MEM structure to B<bm> and sets the
  65. close flag to B<c>, that is B<c> should be either BIO_CLOSE or BIO_NOCLOSE.
  66. It is a macro.
  67. BIO_get_mem_ptr() places the underlying BUF_MEM structure in *B<pp>. It is
  68. a macro.
  69. BIO_new_mem_buf() creates a memory BIO using B<len> bytes of data at B<buf>,
  70. if B<len> is -1 then the B<buf> is assumed to be nul terminated and its
  71. length is determined by B<strlen>. The BIO is set to a read only state and
  72. as a result cannot be written to. This is useful when some data needs to be
  73. made available from a static area of memory in the form of a BIO. The
  74. supplied data is read directly from the supplied buffer: it is B<not> copied
  75. first, so the supplied area of memory must be unchanged until the BIO is freed.
  76. All of the five functions described above return an error with
  77. BIO_s_dgram_mem().
  78. =head1 NOTES
  79. Writes to memory BIOs will always succeed if memory is available: that is
  80. their size can grow indefinitely. An exception is BIO_s_dgram_mem() when
  81. L<BIO_set_write_buf_size(3)> is called on it. In such case the write buffer
  82. size will be fixed and any writes that would overflow the buffer will return
  83. an error.
  84. Every write after partial read (not all data in the memory buffer was read)
  85. to a read write memory BIO will have to move the unread data with an internal
  86. copy operation, if a BIO contains a lot of data and it is read in small
  87. chunks intertwined with writes the operation can be very slow. Adding
  88. a buffering BIO to the chain can speed up the process.
  89. Calling BIO_set_mem_buf() on a secmem or dgram BIO will give undefined results,
  90. including perhaps a program crash.
  91. Switching a memory BIO from read write to read only is not supported and
  92. can give undefined results including a program crash. There are two notable
  93. exceptions to the rule. The first one is to assign a static memory buffer
  94. immediately after BIO creation and set the BIO as read only.
  95. The other supported sequence is to start with a read write BIO then temporarily
  96. switch it to read only and call BIO_reset() on the read only BIO immediately
  97. before switching it back to read write. Before the BIO is freed it must be
  98. switched back to the read write mode.
  99. Calling BIO_get_mem_ptr() on read only BIO will return a BUF_MEM that
  100. contains only the remaining data to be read. If the close status of the
  101. BIO is set to BIO_NOCLOSE, before freeing the BUF_MEM the data pointer
  102. in it must be set to NULL as the data pointer does not point to an
  103. allocated memory.
  104. Calling BIO_reset() on a read write memory BIO with BIO_FLAGS_NONCLEAR_RST
  105. flag set can have unexpected outcome when the reads and writes to the
  106. BIO are intertwined. As documented above the BIO will be reset to the
  107. state after the last completed write operation. The effects of reads
  108. preceding that write operation cannot be undone.
  109. Calling BIO_get_mem_ptr() prior to a BIO_reset() call with
  110. BIO_FLAGS_NONCLEAR_RST set has the same effect as a write operation.
  111. Calling BIO_set_close() with BIO_NOCLOSE orphans the BUF_MEM internal to the
  112. BIO, _not_ its actual data buffer. See the examples section for the proper
  113. method for claiming ownership of the data pointer for a deferred free operation.
  114. =head1 RETURN VALUES
  115. BIO_s_mem(), BIO_s_dgram_mem() and BIO_s_secmem() return a valid memory
  116. B<BIO_METHOD> structure.
  117. BIO_set_mem_eof_return(), BIO_set_mem_buf() and BIO_get_mem_ptr()
  118. return 1 on success or a value which is less than or equal to 0 if an error occurred.
  119. BIO_get_mem_data() returns the total number of bytes available on success,
  120. 0 if b is NULL, or a negative value in case of other errors.
  121. BIO_new_mem_buf() returns a valid B<BIO> structure on success or NULL on error.
  122. =head1 EXAMPLES
  123. Create a memory BIO and write some data to it:
  124. BIO *mem = BIO_new(BIO_s_mem());
  125. BIO_puts(mem, "Hello World\n");
  126. Create a read only memory BIO:
  127. char data[] = "Hello World";
  128. BIO *mem = BIO_new_mem_buf(data, -1);
  129. Extract the BUF_MEM structure from a memory BIO and then free up the BIO:
  130. BUF_MEM *bptr;
  131. BIO_get_mem_ptr(mem, &bptr);
  132. BIO_set_close(mem, BIO_NOCLOSE); /* So BIO_free() leaves BUF_MEM alone */
  133. BIO_free(mem);
  134. Extract the BUF_MEM ptr, claim ownership of the internal data and free the BIO
  135. and BUF_MEM structure:
  136. BUF_MEM *bptr;
  137. char *data;
  138. BIO_get_mem_data(bio, &data);
  139. BIO_get_mem_ptr(bio, &bptr);
  140. BIO_set_close(mem, BIO_NOCLOSE); /* So BIO_free orphans BUF_MEM */
  141. BIO_free(bio);
  142. bptr->data = NULL; /* Tell BUF_MEM to orphan data */
  143. BUF_MEM_free(bptr);
  144. ...
  145. free(data);
  146. =head1 COPYRIGHT
  147. Copyright 2000-2023 The OpenSSL Project Authors. All Rights Reserved.
  148. Licensed under the Apache License 2.0 (the "License"). You may not use
  149. this file except in compliance with the License. You can obtain a copy
  150. in the file LICENSE in the source distribution or at
  151. L<https://www.openssl.org/source/license.html>.
  152. =cut