//Generate an RSA key pair, sign a message and verify it using crypto++ 5.6.1 or later. | |
//By Tim Sheerman-Chase, 2013 | |
//This code is in the public domain and CC0 | |
//To compile: g++ gen.cpp -lcrypto++ -o gen | |
#include <string> | |
using namespace std; | |
#include <crypto++/rsa.h> | |
#include <crypto++/osrng.h> | |
#include <crypto++/base64.h> |
#include <math.h> | |
#include <stdio.h> | |
#include <stdlib.h> | |
#define RADIX 2.0 | |
/************************* | |
* balance a real matrix * | |
*************************/ |
Below I collected relevant links and papers more or less pertaining to the subject of tetrahedral meshes. | |
It's an ever-growing list. | |
------------------------------ | |
Relevant links: | |
http://en.wikipedia.org/wiki/Types_of_mesh | |
http://en.wikipedia.org/wiki/Tetrahedron | |
http://en.wikipedia.org/wiki/Simplicial_complex |
/* | |
* randomize.c -- generate random file name | |
* Author: Krzysztof Krolikowski <kkrolikowski@gamil.com> | |
* compilation: | |
* gcc -o randomize randomize.c | |
* running: | |
* ~$ ./randomize | |
* dyndns_nBXGV0cW | |
* | |
*/ |
/* | |
# How To Get Information from Authenticode Signed Executables | |
https://support.microsoft.com/en-us/help/323809/how-to-get-information-from-authenticode-signed-executables | |
## Summary | |
You can use the WinVerifyTrust() API to verify an Authenticode signed executable. | |
Although a signature is verified, a program may also have to do the following: |
Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill
) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.
The Wayland project seems to operate like they were starting a greenfield project, whereas at the same time they try to position Wayland as "the X11 successor", which would clearly require a lot of thought about not breaking, or at least providing a smooth upgrade path for, existing software.
In fact, it is merely an incompatible alternative, and not e