Is apksigner compliant with JCE (Java Cryptography Extension) specification? - code-signing

Is apksigner tool that comes along with Android SDK Build Tools compliant with JCE (Java Cryptography Extension) specification?

The current (as of July 25 2017) apksigner version 0.7 released in Andriod SDK Build Tools 26.0.1 supports signing using HSM keys via Sun/Oracle's PKCS #11 Provider and its extensions. For example:
apksigner sign --provider-class sun.security.pkcs11.SunPKCS11 \
--provider-arg token.cfg --ks NONE --ks-type PKCS11 app.apk
Also see https://geoffreymetais.github.io/code/key-signing/.

Related

VS code does not detect .NET Core Runtime in Linux Mint

I am trying to use the Oracle Explorer extension in vscode. When I first installed it, vscode popped up this dialog asking me to install .Net Core Runtime. I followed the link and installed the SDK and runtime (Ubuntu). It seems to have installed correctly. When I type
dotnet --info
I get this output, which looks okay to me:
.NET SDK (reflecting any global.json):
Version: 6.0.101
Commit: ef49f6213a
Runtime Environment:
OS Name: linuxmint
OS Version: 20.3
OS Platform: Linux
RID: linux-x64
Base Path: /usr/share/dotnet/sdk/6.0.101/
Host (useful for support):
Version: 6.0.1
Commit: 3a25a7f1cc
.NET SDKs installed:
6.0.101 [/usr/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.1 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.1 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download
However, when I re-open vscode I still get the dialog telling me that the Oracle Explorer extension requires the .NET Core Runtime.
I thought it might be a problem with the $PATH variable. This is the output of $PATH:
bash: /home/jh/bin:/home/jh/packages/anaconda3/bin:/home/jh/packages/anaconda3/condabin:/home/jh/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/jh/.dotnet/tools: No such file or directory
/home/jh/.dotnet/tools does not exist. I tried adding the directories from the "dotnet --info" output to PATH but that didn't work either. I'm in uncharted territory here so that's about as far as I got.
Any help is appreciated.
The extension doesn't currently support the .NET Core Runtime 6.0 (found in an answer here).
I installed the 5.0 Runtime and everything worked fine.

MAC OS project upgrades from Fabric to FirebaseCrashlytics (without CoCOPod)

We need to use Firebase Crashlytics in a project.
We do not use the CocoaPods libraries, and need a statically linked library (.a)
Could you help me with how to download Firebase Crashlytics library into our project?
Here is the error output from the build process:
Prepare build
Workspace PDF Reader Pro Edtition | Scheme PDF Reader Pro Edition | Destination My Mac
Using new build system
Building targets in parallel
Planning build
Constructing build description
Build target PDF Reader Pro Edition
Project PDF Reader Pro Edtion | Configuration Debug | Destination My Mac | SDK macOS 10.15
PDF Reader Pro Edition isn't code signed but requires entitlements. It is not possible to add entitlement...
OpenGL is deprecated. Consider migrating to Metal instead.
Building for macOS, but the linked framework 'FirebaseCrashlytics.framework' was built for Mac Catalyst.
Build failed 2020/6/28, 10:06 AM 2.9 seconds
1 error, 2 warnings
The GitHub project describes how to build the project without Cocoapods.
https://github.com/firebase/firebase-ios-sdk/tree/master/Crashlytics
Clone or download the project.
Run Crashlytics/generate_project.sh
open gen/FirebaseCrashlytics/FirebaseCrashlytics.xcworkspace

Where should I put ASP.NET Core Runtime binaries?

Some example code I'm playing with informs me that I need ASP.NET Core Runtime 2.1.14. I found it here. I'm on macOS and there is no installer, so I downloaded the "binaries" at the link "x64" under the heading "ASP.NET Core Runtime 2.1.14" on the right. I extracted the compressed folder, called "aspnetcore-runtime-2.1.14-osx-x64", which has the following contents:
dotnet
host
LICENSE.txt
shared
ThirdPartyNotices.txt
Now, I haven't the foggiest idea what I should do with these to install ASP.NET Core Runtime 2.1.14. Could someone please tell me what I should do?
To build and run ASP.NET Core apps on macOS, you need to install the SDK which also contains the runtime. There's an installer for that on the page you linked.
You can check the installed SDKs using dotnet --list-sdks and see where are they located. Same goes for the runtimes with dotnet --list-runtimes. The .NET CLI chooses the SDK version for each dotnet command, so in your case it will pick the one compatible with the version specified in your project. By default, it would use the latest.
There is an installer for MacOS on the download page for 2.1 you visited:
Make sure to download the SDK (it includes the Runtime) in the column Installers, not Binaries.
Then install it as any MacOS application. Once you did it, you can type dotnet --version in a terminal and it will return the version you just installed.

Which Openssl version compatible with Indy 10 version 5519 and 5438?

I use Indy 10 build 5438 under Delphi 5 with OpenSSL 1.0.2m.
There is some problem with TLS v1.2 e-mail sending with some (not all) e-mail accounts, and I want to try to upgrade the OpenSSL DLL files for Indy 10, but I do not know which one is compatible.
Which is the latest(!) OpenSSL version that is compatible with Indy 10 build 5438?
I already tried to install the latest Indy 10 build 5519 under Delphi 5 with fulld_5.bat, but it failed:
IdIMAP4.pas(2958) Error: Undeclared identifier: 'LLTextBuf'
IdIMAP4.pas(2958) Error: Incompatible types
IdIMAP4.pas(3185)
IdIMAP4.pas(3697)
IdIMAP4.pas(4209)
IdIMAP4.pas(4721)
IdIMAP4.pas(5233)
IdIMAP4.pas(5745)
IdIMAP4.pas(6257)
IdIMAP4.pas(6769)
IdIMAP4.pas(7251)
IndyProtocols50.dpk(267) Fatal: Could not compile used unit 'IdIMAP4.pas'
Error!
Indy 10 uses standard OpenSSL DLLs. Any 1.0.2 version of OpenSSL is compatible with Indy (Indy does not support OpenSSL 1.1.x yet). However, pre-built versions of OpenSSL 1 (built without MS Visual C++ runtime dependencies) are available on Indy's Fulgan mirror:
https://indy.fulgan.com/SSL
1: At the time of this writing, the latest version available there is 1.0.2t.
As for the IdIMAP4.pas error, that was a typo in a recent code checkin. On line 2958, the reference to LLTextBuf needs to be changed to LTextBuf instead.
LUseNonSyncLiteral := LCanUseNonSyncLiteral and ((not LNonSyncLiteralIsLimited) or (Length({LLTextBuf}LTextBuf) <= 4096)); // <-- change LLTextBuf to LTextBuf
I have now fixed that in the official Indy code (SVN revision 5520).

Is there an OpenSSL for windows?

I'm trying to generate OpenSSL certificates on Windows OS. But I find most of the commands related to OpenSSL are for *nix OS.
Is there an OpenSSL for Windows OS? If yes, from where can I get it? Is this official OpenSSL build for Windows?
Search openssl shining light production in google and download from the first link
Yes. You can do one of two things:
1) Build it yourself
You'll need a build environment (either Visual Studio or msys2 based), and a few other pre-requisites. Download the source from here:
https://www.openssl.org/source/
And (assuming you downloaded the 1.1.0 version), read the INSTALL notes here:
https://github.com/openssl/openssl/blob/OpenSSL_1_1_0-stable/INSTALL
There are also some Windows specific notes here:
https://github.com/openssl/openssl/blob/OpenSSL_1_1_0-stable/NOTES.WIN
2) Download a pre-compiled version
The OpenSSL project doesn't distribute pre-compiled binaries, but they do maintain a list of third-party provided binaries. The list is here:
https://wiki.openssl.org/index.php/Binaries
If you're using Chocolatey, you can also install with
choco install openssl
More details in here and for me it also installed some other stuff, like VC Redist:
Installed:
- kb2919355 v1.0.20160915
- kb3033929 v1.0.5
- kb2999226 v1.0.20181019
- openssl v1.1.1.1900
- vcredist2015 v14.0.24215.20170201
- kb2919442 v1.0.20160915
- vcredist140 v14.34.31931
- kb3035131 v1.0.3
- chocolatey-windowsupdate.extension v1.0.5
Packages requiring reboot:
- vcredist140 (exit code 3010)
This was done on Windows 10.
Both Cygwin and MSYS distribute pre-compiled openssl binaries, which I use everyday.
If you don't like a *nix like style, please refer this official page for standalone distrbutions.
https://wiki.openssl.org/index.php/Binaries
Disclaim: I have not tested the software listed on the page.
I am using this version https://slproweb.com/products/Win32OpenSSL.html and install it with
Essentials
winget install -e ShiningLight.OpenSSL.Light
Full
winget install -e ShiningLight.OpenSSL

Resources