| # base64url encode | |
| function base64url_encode { | |
| (if [ -z "$1" ]; then cat -; else echo -n "$1"; fi) | | |
| openssl base64 -e -A | | |
| sed s/\\+/-/g | | |
| sed s/\\//_/g | | |
| sed -E s/=+$// | |
| } | |
| # base64url decode |
Build FFmpeg with Intel's QSV enablement on an Intel-based validation test-bed:
Build platform: Ubuntu 18.04LTS
Ensure the platform is up to date:
sudo apt update && sudo apt -y upgrade && sudo apt -y dist-upgrade
Install baseline dependencies first (inclusive of OpenCL headers+)
Libuv and libev, two I/O libraries with similar names, recently had the privilege to use both libraries to write something. Now let's talk about my own subjective expression of common and different points.
The topic of high-performance network programming has been discussed. Asynchronous, asynchronous, or asynchronous. Whether it is epoll or kqueue, it is always indispensable to the asynchronous topic.
Libuv is asynchronous, and libev is synchronous multiplexing IO multiplexing.
Libev is a simple encapsulation of system I/O reuse. Basically, it solves the problem of different APIs between epoll and kqueuq. Ensure that programs written using livev's API can run on most *nix platforms. However, the disadvantages of libev are also obvious. Because it basically just encapsulates the Event Library, it is inconvenient to use. For example, accept(3) requires manual setnonblocking after connection. EAGAIN, EWOULDBLOCK, and EINTER need to be detected when reading from a socket. This is a
| /* | |
| This file had now been added to the git repo | |
| https://github.com/darrenjs/openssl_examples | |
| ... which also includes a non blocking client example. | |
| ------------------------------------------------------------------------------- | |
| ssl_server_nonblock.c -- Copyright 2017 Darren Smith -- MIT license |
| // | |
| // Simple listener.c program for UDP multicast | |
| // | |
| // Adapted from: | |
| // http://ntrg.cs.tcd.ie/undergrad/4ba2/multicast/antony/example.html | |
| // | |
| // Changes: | |
| // * Compiles for Windows as well as Linux | |
| // * Takes the port and group on the command line | |
| // |
| tar xvf VMware-vix-disklib-6.0.2-3566099.x86_64.tar.gz | |
| cd vmware-vix-disklib-distrib/bin64 | |
| sudo ln -s $(pwd)/vmware-vdiskmanager /usr/bin/vmware-vdiskmanager | |
| ls -l /usr/bin/vmware-vdiskmanager | |
| cd ../lib64/ | |
| sudo ln -s $(pwd) /usr/lib/vmware | |
| sudo bash -c "echo $(pwd) > /etc/ld.so.conf.d/vmware-vix-disklib.conf" | |
| sudo ldconfig |
| [Unit] | |
| Description=The Apache HTTP Server | |
| After=network.target | |
| [Service] | |
| Type=forking | |
| ExecStart=/usr/local/apache2/bin/apachectl -k start | |
| ExecReload=/usr/local/apache2/bin/apachectl -k graceful | |
| ExecStop=/usr/local/apache2/bin/apachectl -k graceful-stop | |
| PIDFile=/usr/local/apache2/logs/httpd.pid |
| Summary of passwords by sperglord8008s, updated November 1. 2020. For login try "root", "default", "defaul" or "root" | |
| 00000000 | |
| 059AnkJ | |
| 4uvdzKqBkj.jg | |
| 7ujMko0admin | |
| 7ujMko0vizxv | |
| 123 | |
| 1111 | |
| 1234 |
The API used for DTLS is mostly the same as for TLS, because of the mapping of generic functions to protocol specifc ones. Some additional functions are still necessary, because of the new BIO objects and the timer handling for handshake messages. The generic concept of the API is described in the following sections. Examples of applications using DTLS are available at [9].
DTLS の API は TLS とほぼ同じ。 BIO オブジェクトの生成とタイマのために追加でいくつか必要。
