office-gobmx/binaryurp
Caolán McNamara e5aa87aeeb drop requirement for rtl_random_getBytes to have "Pool" arg
Seeing as since:

commit e9531b792d
Date:   Tue Feb 6 14:39:47 2024 +0100

    sal: rtlRandomPool: require OS random device, abort if not present

    Both rtl_random_createPool() and rtl_random_getBytes() first try to get
    random data from the OS, via /dev/urandom or rand_s() (documented to
    call RtlGenRandom(), see [1]).

we don't use the initial arg to rtl_random_getBytes anymore, drop the
requirement to have one. Then simplify our usages of that, and
addtionally deprecate rtl_random_createPool and rtl_random_destroyPool.

Change-Id: I13dcc067714a8a741a4e8f2bfcf2006373f832c4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/167067
Tested-by: Jenkins
Reviewed-by: Caolán McNamara <caolan.mcnamara@collabora.com>
2024-05-08 11:29:54 +02:00
..
qa
source
CppunitTest_binaryurp_test-cache.mk
CppunitTest_binaryurp_test-unmarshal.mk
IwyuFilter_binaryurp.yaml
Library_binaryurp.mk
Makefile
Module_binaryurp.mk
README.md

UNO Remote Protocol (URP)

UNO provides a binary protocol called the UNO Remote Protocol (URP) that provides a bridge between UNO environments. This bridge allows processes and objects to send method calls and to receive return values. UNO objects in different environments are connected by way of this interprocess bridge. The underlying connection is made through a socket or pipe. Remote UNO objects are connected by means of TCP/IP using the high-level protocol of the URP.