interface TlogInterface
Methods
|
trace()
|
||
|
debug()
|
||
|
info()
|
||
|
warning()
|
||
|
error()
|
||
|
fatal()
|
Details
at line 8
public
trace()
at line 9
public
debug()
at line 10
public
info()
at line 11
public
warning()
at line 12
public
error()
at line 13
public
fatal()


Enjoy your stay!
Rating:
Rating:
Rating:
Pizza Hub is currently located at 111 N Eastern Ave, Moore, OK 73160. Order your favorite pizza, pasta, salad, and more, all with the click of a button. We accept orders online for pickup. By 1989, 5000 stores were cooking up our signature pizza experience all over the US. Today, there are more than 11.000 Domino's Pizza around the world, 6000 of which are outside the US. Kenya is now a part of this international story of pizza success.
"Some quick example text to build on the card title and make up the bulk of the card's content."


Affilify will transform product links to affiliate links automatically. Open the browser's web tools and check the network tab for the redirect when you click on the links. The first request in the network tab is the request to the affiliate network. Usually the affiliate networks will then redirect you to the original location of the link.
Affilifiy currently works for Zanox, Amazon and Affilinet.
Here's is a sample configuration:
// init affilify plugin $("a").affilify({ zanox: { publisherId: "36434335C584445997", programs: [{ domain: "myprotein.com"}, {domain: "vaola.de" }] }, amazonPublisherId: "f07e5-21", affilinet: { publisherId: "756180", programs: [ // affilinet programs {domain: "decathlon.de", siteId: "10685"}, {domain: "fitmart.de", siteId: "12802"}, {domain: "sportscheck.com", siteId: "3617"} ] } });
http://de.myprotein.com/home.dept
http://www.vaola.de/p/reebok-classic-leather-sneaker-herren-schwarz.html
http://www.fitmart.de/Protein/ESN-Designer-Whey-1000g-Standbeutel.html
http://www.sportscheck.com/blackroll-standard-faszienrolle-p228437-F041/schwarzblauorange/


Except where otherwise stated, this software is distributed under a license based on the MIT X Consortium license. To view the license, see here. The OpenPGP library also includes a modified BZIP2 library which is licensed under the Apache Software License, Version 2.0.
If you have the full package you will have six jar files, bcprov*.jar which contains the BC provider, jce-*.jar which contains the JCE provider, clean room API, and bcmail*.jar which contains the mail API.
Note: if you are using JDK 1.0, you will just find a class hierarchy in the classes directory.
To view examples, look at the test programs in the packages:
To verify the packages, run the following Java programs with the appropriate classpath:
Some of the algorithms in the Bouncy Castle APIs are patented in some places. It is upon the user of the library to be aware of what the legal situation is in their own situation, however we have been asked to specifically mention the patents below, in the following terms, at the request of the patent holder.
The BC distribution contains implementations of EC MQV as described in RFC 5753, "Use of ECC Algorithms in CMS". In line with the conditions in:
https://www.ietf.org/ietf-ftp/IPR/certicom-ipr-rfc-5753.pdfWe state, where EC MQV has not otherwise been disabled or removed: "The use of this product or service is subject to the reasonable, non-discriminatory terms in the Intellectual Property Rights (IPR) Disclosures of Certicom Corp. at the IETF for Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS) implemented in the product or service."
This API has been specifically developed for those circumstances where the rich API and integration requirements of the JCE are not required.
However as a result, the light-weight API requires more effort and understanding on the part of a developer to initialise and utilise the algorithms.
To utilise the light-weight API in a program, the fundamentals are as follows;
/*
* This will use a supplied key, and encrypt the data
* This is the equivalent of DES/CBC/PKCS5Padding
*/
BlockCipher engine = new DESEngine();
BufferedBlockCipher cipher = new PaddedBlockCipher(new CBCCipher(engine));
byte[] key = keyString.getBytes();
byte[] input = inputString.getBytes();
cipher.init(true, new KeyParameter(key));
byte[] cipherText = new byte[cipher.getOutputSize(input.length)];
int outputLen = cipher.processBytes(input, 0, input.length, cipherText, 0);
try
{
cipher.doFinal(cipherText, outputLen);
}
catch (CryptoException ce)
{
System.err.println(ce);
System.exit(1);
}
The light-weight API has built in support for the following:
The base interface is BlockCipher and has the following implementations which match the modes the block cipher can be operated in.
| Name | Constructor | Notes |
|---|---|---|
| BufferedBlockCipher | BlockCipher | |
| CBCBlockCipher | BlockCipher | |
| CFBBlockCipher | BlockCipher, block size (in bits) | |
| GCFBlockCipher | BlockCipher | GOST CFB mode with CryptoPro key meshing. |
| EAXBlockCipher | BlockCipher | |
| OCBBlockCipher | BlockCipher | |
| OFBBlockCipher | BlockCipher, block size (in bits) | |
| SICBlockCipher | BlockCipher, block size (in bits) | Also known as CTR mode |
| KCTRBlockCipher | BlockCipher, block size (in bits) | DSTU7624 CTR mode |
| OpenPGPCFBBlockCipher | BlockCipher | |
| GOFBBlockCipher | BlockCipher | GOST OFB mode |
The base interface for AEAD (Authenticated Encryption Associated Data) modes is AEADBlockCipher and has the following implemenations.
| Name | Constructor | Notes |
|---|---|---|
| CCMBlockCipher | BlockCipher | Packet mode - requires all data up front. |
| EAXBlockCipher | BlockCipher | |
| CCMBlockCipher | BlockCipher | Packet mode - requires all data up front. |
| GCMBlockCipher | BlockCipher | Packet mode - NIST SP 800-38D. |
| KCCMBlockCipher | BlockCipher | DSTU 7624 Packet mode - requires all data up front. |
| OCBBlockCipher | BlockCipher | |
| ChaCha20Poly1305 | AEADCipher |
BufferedBlockCipher has a further sub-classes
| Name | Constructor | Notes |
|---|---|---|
| PaddedBufferedBlockCipher | BlockCipher | a buffered block cipher that can use padding - default PKCS5/7 padding |
| CTSBlockCipher | BlockCipher | Cipher Text Stealing |
| NISTCTSBlockCipher | BlockCipher | Cipher Text Stealing - NIST mode set. |
The following paddings can be used with the PaddedBufferedBlockCipher.
| Name | Description |
|---|---|
| PKCS7Padding | PKCS7/PKCS5 padding |
| ISO10126d2Padding | ISO 10126-2 padding |
| X932Padding | X9.23 padding |
| ISO7816d4Padding | ISO 7816-4 padding (ISO 9797-1 scheme 2) |
| ZeroBytePadding | Pad with Zeros (not recommended) |
The following cipher engines are implemented that can be used with the above modes.
| Name | KeySizes (in bits) | Block Size | Notes |
|---|---|---|---|
| AESEngine | 0 .. 256 | 128 bit | |
| AESWrapEngine | 0 .. 256 | 128 bit | Implements FIPS AES key wrapping |
| BlowfishEngine | 0 .. 448 | 64 bit | |
| CamelliaEngine | 128, 192, 256 | 128 bit | |
| CamelliaWrapEngine | 128, 192, 256 | 128 bit | |
| CAST5Engine | 0 .. 128 | 64 bit | |
| CAST6Engine | 0 .. 256 | 128 bit | |
| DESEngine | 64 | 64 bit | |
| DESedeEngine | 128, 192 | 64 bit | |
| DESedeWrapEngine | 128, 192 | 64 bit | Implements Draft IETF DESede key wrapping |
| DSTU7624Engine | 128, 256, 512 | 128/256/512 bit | DSTU7624 Block Cipher |
| DSTU7624WrapEngine | 128, 256, 512 | 128/256/512 bit | DSTU7624 key wrapper |
| GOST28147Engine | 256 | 64 bit | Has a range of S-boxes |
| GOST3412_2015Engine | 256 | 128 bit | |
| IDEAEngine | 128 | 64 bit | |
| NoekeonEngine | 128 | 128 bit | |
| RC2Engine | 0 .. 1024 | 64 bit | |
| RC532Engine | 0 .. 128 | 64 bit | Uses a 32 bit word |
| RC564Engine | 0 .. 128 | 128 bit | Uses a 64 bit word |
| RC6Engine | 0 .. 256 | 128 bit | |
| RijndaelEngine | 0 .. 256 | 128 bit, 160 bit, 192 bit, 224 bit, 256 bit | |
| SEEDEngine | 128 | 128 bit | |
| SEEDWrapEngine | 128 | 128 bit | |
| Shacal2Engine | 512 | 256 bit | |
| SerpentEngine | 128, 192, 256 | 128 bit | |
| SkipjackEngine | 0 .. 128 | 64 bit | |
| SM4Engine | 128 | 128 bit | |
| TEAEngine | 128 | 64 bit | |
| ThreefishEngine | 256/512/1024 | 256 bit/512 bit/1024 bit | Tweakable block cipher |
| TwofishEngine | 128, 192, 256 | 128 bit | |
| XTEAEngine | 128 | 64 bit |
The following additional key wrapping algorithms are also available: RFC3211WrapEngine, RFC3394WrapEngine, and RFC5649WrapEngine.
The base interface is StreamCipher and has the following implementations which match the modes the stream cipher can be operated in.
| Name | Constructor | Notes |
|---|---|---|
| BlockStreamCipher | BlockCipher |
The following cipher engines are implemented that can be used with the above modes.
| Name | KeySizes (in bits) | Notes |
|---|---|---|
| RC4Engine | 40 .. 2048 | |
| HC128Engine | 128 | |
| HC256Engine | 256 | |
| ChaChaEngine | 128/256 | 64 bit IV |
| Salsa20Engine | 128/256 | 64 bit IV |
| XSalsa20Engine | 256 | 192 bit IV |
| ISAACEngine | 32 .. 8192 | |
| VMPCEngine | 8 .. 6144 | |
| Grainv1Engine | 80 | 64 bit IV |
| Grain128Engine | 128 | 96 bit IV |
| Zuc128Engine | 128 | 128 bit IV |
| Zuc256Engine | 256 | 200 bit IV |
The base interface is AsymmetricBlockCipher and has the following implementations which match the modes the cipher can be operated in.
| Name | Constructor | Notes |
|---|---|---|
| BufferedAsymmetricBlockCipher | AsymmetricBlockCipher | |
| OAEPEncoding | AsymmetricBlockCipher | |
| PKCS1Encoding | AsymmetricBlockCipher | |
| ISO9796d1Encoding | AsymmetricBlockCipher | ISO9796-1 |
The following cipher engines are implemented that can be used with the above modes.
| Name | KeySizes (in bits) | Notes |
|---|---|---|
| RSAEngine | any multiple of 8 large enough for the encoding. | |
| ElGamalEngine | any multiple of 8 large enough for the encoding. | |
| NTRUEngine | any multiple of 8 large enough for the encoding. |
The following asymmetric ciphers are also supported and allow variable block sizes:
The base interface is Digest and has the following implementations
| Name | Output (in bits) | Notes |
|---|---|---|
| Blake2sDigest | 128, 160, 224, 256 | |
| Blake2bDigest | 224, 256, 384, 512 | |
| DSTU7564Digest | 256, 384, 512 | |
| KeccakDigest | 224, 256, 288, 384, 512 | |
| MD2Digest | 128 | |
| MD4Digest | 128 | |
| MD5Digest | 128 | |
| RipeMD128Digest | 128 | basic RipeMD |
| RipeMD160Digest | 160 | enhanced version of RipeMD |
| RipeMD256Digest | 256 | expanded version of RipeMD128 |
| RipeMD320Digest | 320 | expanded version of RipeMD160 |
| SHA1Digest | 160 | |
| SHA224Digest | 224 | FIPS 180-2 |
| SHA256Digest | 256 | FIPS 180-2 |
| SHA384Digest | 384 | FIPS 180-2 |
| SHA512Digest | 512 | FIPS 180-2 |
| SHA3Digest | 224, 256, 384, 512 | |
| SHAKEDigest | 128, 256 | cSHAKE primitive also supported. |
| SkeinDigest | any byte length | 256 bit, 512 bit and 1024 state sizes. Additional parameterisation using SkeinParameters. |
| SM3Digest | 256 | The SM3 Digest. |
| TigerDigest | 192 | The Tiger Digest. |
| GOST3411Digest | 256 | The GOST-3411 Digest. |
| GOST3411_2012_256Digest | 256 | The GOST-3411-2012-256 Digest. |
| GOST3411_2012_512Digest | 512 | The GOST-3411-2012-512 Digest. |
| WhirlpoolDigest | 512 | The Whirlpool Digest. |
| Haraka256Digest | 256 | Haraka V2 - 256 bit input version. |
| Haraka512Digest | 256 | Haraka V2 - 512 bit input version. |
The base interface is Mac and has the following implementations
| Name | Output (in bits) | Notes |
|---|---|---|
| CBCBlockCipherMac | blocksize/2 unless specified | |
| CFBBlockCipherMac | blocksize/2, in CFB 8 mode, unless specified | |
| CMac | 24 to cipher block size bits | Usable with block ciphers, NIST SP 800-38B. |
| GMac | 32 to 128 bits | Usable with GCM mode ciphers, defined for AES, NIST SP 800-38D. |
| GOST28147Mac | 32 bits | |
| ISO9797Alg3Mac | multiple of 8 bits up to underlying cipher size. | |
| HMac | digest length | |
| DSTU7564 | 256, 384, 512 bits | |
| DSTU7624 | 128, 256, 512 bits | |
| Poly1305 | 128 bits | Usable with 128 bit block ciphers. Use Poly1305KeyGenerator to generate keys. |
| SkeinMac | any byte length | 256 bit, 512 bit and 1024 state size variants. Additional parameterisation using SkeinParameters. |
| SipHash | 64 bits | |
| SipHash128 | 128 bits | |
| VMPCMac | 160 bits | |
| Zuc128Mac | 32 bits | |
| Zuc256Mac | 32, 64, 128 bits |
The base class is PBEParametersGenerator and has the following sub-classes
| Name | Constructor | Notes |
|---|---|---|
| PKCS5S1ParametersGenerator | Digest | |
| PKCS5S2ParametersGenerator | Uses SHA1/Hmac as defined | |
| PKCS12ParametersGenerator | Digest | |
| OpenSSLPBEParametersGenerator | Uses MD5 as defined |
The following password hashing schemes are supported:
| Name | Constructor | Notes |
|---|---|---|
| Argon2 | ||
| BCrypt | ||
| OpenBSDBcyrpt | ||
| SCrypt |
The IES cipher is based on the one described in IEEE P1363a (draft 10), for use with either traditional Diffie-Hellman or Elliptic Curve Diffie-Hellman.
Note: At the moment this is still a draft, don't use it for anything that may be subject to long term storage, the key values produced may well change as the draft is finalised.The base class is Committer and has the following sub-classes
| Name | Notes |
|---|---|
| HashCommitter | Hash commitment algorithm described in Usenix RPC MixNet Paper (2002) |
Two versions of Diffie-Hellman key agreement are supported, the basic version, and one for use with long term public keys. Two versions of key agreement using Elliptic Curve cryptography are also supported, standard Diffie-Hellman key agreement and standard key agreement with co-factors.
The agreement APIs are in the org.bouncycastle.crypto.agreement package. Classes for generating Diffie-Hellman parameters can be found in the org.bouncycastle.crypto.params and org.bouncycastle.crypto.generators packages.
The base class is KeyEncapsulation and has the following sub-classes
| Name | Notes |
|---|---|
| RSAKeyEncapsulation | RSA-KEM from ISO 18033-2 |
| PKCS5S2ParametersGenerator | ECIES-KEM from ISO 18033-2 |
DSA, ECDSA, ISO-9796-2, GOST-3410-94, GOST-3410-2001, GOST-3410-2012, DSTU-4145-2002, and RSA-PSS are supported by the org.bouncycastle.crypto.signers package. Note: as these are light weight classes, if you need to use SHA1 or GOST-3411 (as defined in the relevant standards) you'll also need to make use of the appropriate digest class in conjunction with these. Classes for generating DSA and ECDSA parameters can be found in the org.bouncycastle.crypto.params and org.bouncycastle.crypto.generators packages.
The org.bouncycastle.crypto.ec package contains implementations for a variety of EC cryptographic transforms such as EC ElGamal.
The org.bouncycastle.crypto.tls package contains implementations for TLS 1.1, 1.2 and DTLS 1.0, 1.2.
The org.bouncycastle.crypto.prng package contains implementations for a variety of bit generators including those from SP 800-90A and X9.31, as well as builders for SecureRandom objects based around them.
The light-weight API has direct interfaces into a package capable of reading and writing DER-encoded ASN.1 objects and for the generation of X.509 V3 certificate objects and PKCS12 files. BER InputStream and OutputStream classes are provided as well.
The Bouncy Castle provider is a JCE compliant provider that is a wrapper built on top of the light-weight API. The main provider is referred to with the name "BC", the post quantum provider is indicated by "BCPQC".
The advantage for writing application code that uses the provider interface to cryptographic algorithms is that the actual provider used can be selected at run time. This is extremely valuable for applications that may wish to make use of a provider that has underlying hardware for cryptographic computation, or where an application may have been developed in an environment with cryptographic export controls.
To utilise the JCE provider in a program, the fundamentals are as follows;
/*
* This will generate a random key, and encrypt the data
*/
Key key;
KeyGenerator keyGen;
Cipher encrypt;
Security.addProvider(new BouncyCastleProvider());
try
{
// "BC" is the name of the BouncyCastle provider
keyGen = KeyGenerator.getInstance("DES", "BC");
keyGen.init(new SecureRandom());
key = keyGen.generateKey();
encrypt = Cipher.getInstance("DES/CBC/PKCS5Padding", "BC");
}
catch (Exception e)
{
System.err.println(e);
System.exit(1);
}
encrypt.init(Cipher.ENCRYPT_MODE, key);
bOut = new ByteArrayOutputStream();
cOut = new CipherOutputStream(bOut, encrypt);
cOut.write("plaintext".getBytes());
cOut.close();
// bOut now contains the cipher text
The provider can also be configured as part of your environment via static registration by adding an entry to the java.security properties file (found in $JAVA_HOME/jre/lib/security/java.security, where $JAVA_HOME is the location of your JDK/JRE distribution). You'll find detailed instructions in the file but basically it comes down to adding a line:
security.provider.<n>=org.bouncycastle.jce.provider.BouncyCastleProvider
Where <n> is the preference you want the provider at (1 being the most prefered).
Where you put the jar is up to mostly up to you, although with jdk1.3 and jdk1.4 the best (and in some cases only) place to have it is in $JAVA_HOME/jre/lib/ext. Note: under Windows there will normally be a JRE and a JDK install of Java if you think you have installed it correctly and it still doesn't work chances are you have added the provider to the installation not being used.
Note: with JDK 1.4 and later you will need to have installed the unrestricted policy
files to take full advantage of the provider. If you do not install the policy files you are likely
to get something like the following:
java.lang.SecurityException: Unsupported keysize or algorithm parameters
at javax.crypto.Cipher.init(DashoA6275)
The policy files can be found at the same place you downloaded the JDK.
Modes:
Where (n) is a multiple of 8 that gives the blocksize in bits, eg, OFB8. Note that OFB and CFB mode can be used with plain text that is not an exact multiple of the block size if NoPadding has been specified.
All AEAD (Authenticated Encryption Associated Data) modes support
Additional Authentication Data (AAD) using the Cipher.updateAAD()
methods added in Java SE 7.
On Java 7 and later, AEAD modes will throw javax.crypto.AEADBadTagException
on an authentication failure.
On earlier version of Java, javax.crypto.BadPaddingException
is thrown.
Padding Schemes:
When placed together this gives a specification for an algorithm as;
Note: default key sizes are in bold.
| Name | KeySizes (in bits) | Block Size | Notes |
|---|---|---|---|
| AES | 0 .. 256 (192) | 128 bit | |
| AESWrap | 0 .. 256 (192) | 128 bit | A FIPS AES key wrapper |
| ARIA | 0 .. 256 (192) | 128 bit | |
| ARIAWrap | 0 .. 256 (192) | 128 bit | An ARIA key wrapper (based on RFC 5649) |
| Blowfish | 0 .. 448 (448) | 64 bit | |
| Camellia | 128, 192, 256 | 128 bit | |
| CamelliaWrap | 128, 192, 256 | 128 bit | |
| CAST5 | 0 .. 128(128) | 64 bit | |
| CAST6 | 0 .. 256(256) | 128 bit | |
| DES | 64 | 64 bit | |
| DESede | 128, 192 | 64 bit | |
| DESedeWrap | 128, 192 | 128 bit | A Draft IETF DESede key wrapper |
| DSTU7624 | 128, 256, 512 | 128/256/512 bit | DSTU7624 Block Cipher |
| DSTU7624Wrap | 128, 256, 512 | 128/256/512 bit | DSTU7624 key wrapper |
| GCM | 128, 192, 256(192) | AEAD Mode Cipher | Galois/Counter Mode, as defined in NIST Special Publication SP 800-38D. |
| GOST28147 | 256 | 64 bit | |
| IDEA | 128 (128) | 64 bit | |
| Noekeon | 128(128) | 128 bit | |
| RC2 | 0 .. 1024 (128) | 64 bit | |
| RC5 | 0 .. 128 (128) | 64 bit | Uses a 32 bit word |
| RC5-64 | 0 .. 256 (256) | 128 bit | Uses a 64 bit word |
| RC6 | 0 .. 256 (128) | 128 bit | |
| Rijndael | 0 .. 256 (192) | 128 bit | |
| SEED | 128(128) | 128 bit | |
| SEEDWrap | 128(128) | 128 bit | |
| Serpent | 128, 192, 256 (256) | 128 bit | |
| Skipjack | 0 .. 128 (128) | 64 bit | |
| SM4 | 128(128) | 128 bit | |
| TEA | 128 (128) | 64 bit | |
| Threefish-256 | 256 | 256 bit | |
| Threefish-512 | 512 | 512 bit | |
| Threefish-1024 | 1024 | 1024 bit | |
| Twofish | 128, 192, 256 (256) | 128 bit | |
| XTEA | 128 (128) | 64 bit |
Note: default key sizes are in bold.
| Name | KeySizes (in bits) | Notes |
|---|---|---|
| RC4 | 40 .. 2048 bits (128) | |
| HC128 | (128) | |
| HC256 | (256) | |
| ChaCha | 128/256 | 64 bit IV |
| Salsa20 | 128/256 | 64 bit IV |
| XSalsa20 | 256 | 182 bit IV |
| VMPC | 128/6144(128) | |
| Grainv1 | 80 | 64 bit IV |
| Grain128 | 128 | 96 bit IV |
| Zuc128 | 128 | 128 bit IV |
| Zuc256 | 256 | 200 bit IV |
Encoding:
Note: except as indicated in PKCS 1v2 we recommend you use OAEP, as mandated in X9.44.
When placed together with RSA this gives a specification for an algorithm as;
| Name | KeySizes (in bits) | Notes |
|---|---|---|
| RSA | any multiple of 8 bits large enough for the encryption(2048) | |
| ElGamal | any multiple of 8 bits large enough for the encryption(1024) |
Diffie-Hellman key agreement is supported using the "DH", "DHU" (Diffie-Hellman Unified", "ECDH", "ECCDH" (EC Cofactor DH), "ECKAEG" (BSI EC KAEG key agreement"), "ECMQV" and "ECCDHU" (EC Cofactor DH Unified) key agreement instances and their variations. Key exchange, which also uses the KeyAgreement API is supported by "NH" (the NewHope algorithm (BCPQC)). SM2 key exchange is currently supported in the lightweight API.
Support is provided for the standard SEC algorithm set for EC. Names appear in the form of [Agreement]with[KDF PRF Digest][KDF type]. For example:
Note: with basic "DH" only the basic algorithm fits in with the JCE API, if you're using long-term public keys you may want to look at the light-weight API, there are also additional JCE support classes for UserKeyingMaterial and MQVParameters in the org.bouncycastle.jcajce.spec package.
An implementation of ECIES (stream mode) as described in IEEE P 1363a. This now based more formally on Victor Shoup's paper and should be compatible with the implementation in Crypto++ (version 6 onwards).
| Name | Output (in bits) | Notes |
|---|---|---|
| Blake2b-160 | 160 | |
| Blake2b-256 | 256 | |
| Blake2b-384 | 384 | |
| Blake2b-512 | 512 | |
| Blake2s-128 | 128 | |
| Blake2s-160 | 160 | |
| Blake2s-224 | 224 | |
| Blake2s-256 | 256 | |
| DSTU7564-256 | 256 | |
| DSTU7564-384 | 384 | |
| DSTU7564-512 | 512 | |
| GOST3411 | 256 | |
| GOST3411-2012-256 | 256 | |
| GOST3411-2012-512 | 512 | |
| Haraka-256 | 256 | |
| Haraka-512 | 256 | |
| Keccak-224 | 224 | |
| Keccak-288 | 288 | |
| Keccak-256 | 256 | |
| Keccak-384 | 384 | |
| Keccak-512 | 512 | |
| MD2 | 128 | |
| MD4 | 128 | |
| MD5 | 128 | |
| RipeMD128 | 128 | basic RipeMD |
| RipeMD160 | 160 | enhanced version of RipeMD |
| RipeMD256 | 256 | expanded version of RipeMD128 |
| RipeMD320 | 320 | expanded version of RipeMD160 |
| SHA1 | 160 | |
| SHA-224 | 224 | FIPS 180-2 |
| SHA-256 | 256 | FIPS 180-2 |
| SHA-384 | 384 | FIPS 180-2 |
| SHA-512 | 512 | FIPS 180-2 |
| SHA3-224 | 224 | FIPS 202 |
| SHA3-256 | 256 | FIPS 202 |
| SHA3-384 | 384 | FIPS 202 |
| SHA3-512 | 512 | FIPS 202 |
| Skein-256-* | 128, 160, 224, 256 | e.g. Skein-256-160 |
| Skein-512-* | 128, 160, 224, 256, 384, 512 | e.g. Skein-512-256 |
| Skein-1024-* | 384, 512, 1024 | e.g. Skein-1024-1024 |
| SM3 | 256 | |
| Tiger | 192 | |
| Whirlpool | 512 |
| Name | Output (in bits) | Notes |
|---|---|---|
| Any MAC based on a block cipher, CBC (the default) and CFB modes. | half the cipher's block size (usually 32 bits) | |
| *-GMAC | 32 to 128 bits | Usable with GCM mode ciphers, defined for AES, NIST SP 800-38D. e.g. AES-GMAC. |
| VMPC-MAC | 128 | |
| HMac-GOST3411 | 256 | |
| HMac-GOST3411-2012-256 | 256 | |
| HMac-GOST3411-2012-512 | 512 | |
| HMac-KECCAK224 | 224 | |
| HMac-KECCAK256 | 256 | |
| HMac-KECCAK288 | 288 | |
| HMac-KECCAK384 | 384 | |
| HMac-KECCAK512 | 512 | |
| HMac-MD2 | 128 | |
| HMac-MD4 | 128 | |
| HMac-MD5 | 128 | |
| HMac-RipeMD128 | 128 | |
| HMac-RipeMD160 | 160 | |
| HMac-SHA1 | 160 | |
| HMac-SHA224 | 224 | |
| HMac-SHA256 | 256 | |
| HMac-SHA384 | 384 | |
| HMac-SHA512 | 512 | |
| HMac-SHA3-224 | 224 | |
| HMac-SHA3-256 | 256 | |
| HMac-SHA3-384 | 384 | |
| HMac-SHA3-512 | 512 | |
| HMAC-Skein-256-* | 128, 160, 224, 256 | e.g. HMAC-Skein-256-160 |
| HMAC-Skein-512-* | 128, 160, 224, 256, 384, 512 | e.g. HMAC-Skein-512-256 |
| HMAC-Skein-1024-* | 384, 512, 1024 | e.g. HMAC-Skein-1024-1024 |
| Siphash-2-4 (SipHash) | 64 | |
| Siphash-4-8 | 64 | |
| Siphash128-2-4 (SipHash128) | 128 | |
| Skein-MAC-256-* | 128, 160, 224, 256 | e.g. Skein-MAC-256-160 |
| Skein-MAC-512-* | 128, 160, 224, 256, 384, 512 | e.g. Skein-MAC-512-256 |
| Skein-MAC-1024-* | 384, 512, 1024 | e.g. Skein-MAC-1024-1024 |
| HMac-Tiger | 192 | |
| Poly1305-* | 128 | Defined for recent 128 bit block ciphers, e.g. Poly1305-AES, Poly1305-Serpent |
| ZUC-128 | 32 | |
| ZUC-256-32 | 32 | |
| ZUC-256-64 | 64 | |
| ZUC-256-128 | 128 |
Examples:
Schemes:
Schemes:
Defined in Bouncy Castle JCE Provider
| Name | Key Generation Scheme | Key Length (in bits) | Char to Byte conversion |
|---|---|---|---|
| PBEWithMD2AndDES | PKCS5 Scheme 1 | 64 | 8 bit chars |
| PBEWithMD2AndRC2 | PKCS5 Scheme 1 | 128 | 8 bit chars |
| PBEWithMD5AndDES | PKCS5 Scheme 1 | 64 | 8 bit chars |
| PBEWithMD5AndRC2 | PKCS5 Scheme 1 | 128 | 8 bit chars |
| PBEWithSHA1AndDES | PKCS5 Scheme 1 | 64 | 8 bit chars |
| PBEWithSHA1AndRC2 | PKCS5 Scheme 1 | 128 | 8 bit chars |
| PBKDF2WithHmacSHA1 | PKCS5 Scheme 2 | variable | UTF-8 chars |
| PBKDF2WithHmacSHA1AndUTF8 | PKCS5 Scheme 2 | variable | UTF-8 chars |
| PBKDF2WithHmacSHA1And8bit | PKCS5 Scheme 2 | variable | 8 bit chars |
| PBKDF2WithHmacSHA224 | PKCS5 Scheme 2 | variable | UTF-8 chars |
| PBKDF2WithHmacSHA256 | PKCS5 Scheme 2 | variable | UTF-8 chars |
| PBKDF2WithHmacSHA384 | PKCS5 Scheme 2 | variable | UTF-8 chars |
| PBKDF2WithHmacSHA512 | PKCS5 Scheme 2 | variable | UTF-8 chars |
| PBKDF2WithHmacSHA3-224 | PKCS5 Scheme 2 | variable | UTF-8 chars |
| PBKDF2WithHmacSHA3-256 | PKCS5 Scheme 2 | variable | UTF-8 chars |
| PBKDF2WithHmacSHA3-384 | PKCS5 Scheme 2 | variable | UTF-8 chars |
| PBKDF2WithHmacSHA3-512 | PKCS5 Scheme 2 | variable | UTF-8 chars |
| PBKDF2WithHmacGOST3411 | PKCS5 Scheme 2 | variable | UTF-8 chars |
| PBKDF2WithHmacSM3 | PKCS5 Scheme 2 | variable | UTF-8 chars |
| PBEWithSHAAnd2-KeyTripleDES-CBC | PKCS12 | 128 | 16 bit chars |
| PBEWithSHAAnd3-KeyTripleDES-CBC | PKCS12 | 192 | 16 bit chars |
| PBEWithSHAAnd128BitRC2-CBC | PKCS12 | 128 | 16 bit chars |
| PBEWithSHAAnd40BitRC2-CBC | PKCS12 | 40 | 16 bit chars |
| PBEWithSHAAnd128BitRC4 | PKCS12 | 128 | 16 bit chars |
| PBEWithSHAAnd40BitRC4 | PKCS12 | 40 | 16 bit chars |
| PBEWithSHAAndTwofish-CBC | PKCS12 | 256 | 16 bit chars |
| PBEWithSHAAndIDEA-CBC | PKCS12 | 128 | 16 bit chars |
The Bouncy Castle provider will read X.509 certficates (v2 or v3) as per the examples in the java.security.cert.CertificateFactory class. They can be provided either in the normal PEM encoded format, or as DER binaries.
The CertificateFactory will also read X.509 CRLs (v2) from either PEM or DER encodings.
In addition to the classes in the org.bouncycastle.asn1.x509 package for certificate, CRLs, and OCSP, CRMF, and CMP message generation a more JCE "friendly" class is provided in the package org.bouncycastle.cert. The JCE "friendly" classes found in the jcajce subpackages support RSA, DSA, GOST, DTSU, and EC-DSA.
The Bouncy Castle package has four implementation of a keystore.
The first "BKS" is a keystore that will work with the keytool in the same fashion as the Sun "JKS" keystore. The keystore is resistent to tampering but not inspection.
The second, Keystore.BouncyCastle, or Keystore.UBER will only work with the keytool if the password is provided on the command line, as the entire keystore is encrypted with a PBE based on SHA1 and Twofish. PBEWithSHAAndTwofish-CBC. This makes the entire keystore resistant to tampering and inspection, and forces verification. The Sun JDK provided keytool will attempt to load a keystore even if no password is given, this is impossible for this version. (One might wonder about going to all this trouble and then having the password on the command line! New keytool anyone?).
In the first case, the keys are encrypted with 3-Key-TripleDES.
The third is a PKCS12 compatible keystore. PKCS12 provides a slightly different situation from the regular key store, the keystore password is currently the only password used for storing keys. Otherwise it supports all the functionality required for it to be used with the keytool. In some situations other libraries always expect to be dealing with Sun certificates, if this is the case use PKCS12-DEF, and the certificates produced by the key store will be made using the default provider. In the default case PKCS12 uses 3DES for key protection and 40 bit RC2 for protecting the certificates. It is also possible to use 3DES for both by using PKCS12-3DES-3DES or PKCS12-DEF-3DES-3DES as the KeyStore type.
There is an example program that produces PKCS12 files suitable for loading into browsers. It is in the package org.bouncycastle.jce.examples.
The fourth is the BCFKS key store which is a FIPS compliant key store which is also designed for general key storage and based on ASN.1. This key store type is encrypted and supports the use of SCRYPT and the storage of some symmetric key types.
There are no classes for supporting EC in the JDK prior to JDK 1.5. If you are using an earlier JDK you can find classes for using EC in the following packages:
application/pkcs7-signature;; x-java-content-handler=org.bouncycastle.mail.smime.handlers.pkcs7_signature application/pkcs7-mime;; x-java-content-handler=org.bouncycastle.mail.smime.handlers.pkcs7_mime application/x-pkcs7-signature;; x-java-content-handler=org.bouncycastle.mail.smime.handlers.x_pkcs7_signature application/x-pkcs7-mime;; x-java-content-handler=org.bouncycastle.mail.smime.handlers.x_pkcs7_mime multipart/signed;; x-java-content-handler=org.bouncycastle.mail.smime.handlers.multipart_signed
import javax.activation.MailcapCommandMap; import javax.activation.CommandMap; public static void setDefaultMailcap() { MailcapCommandMap _mailcap = (MailcapCommandMap)CommandMap.getDefaultCommandMap(); _mailcap.addMailcap("application/pkcs7-signature;; x-java-content-handler=org.bouncycastle.mail.smime.handlers.pkcs7_signature"); _mailcap.addMailcap("application/pkcs7-mime;; x-java-content-handler=org.bouncycastle.mail.smime.handlers.pkcs7_mime"); _mailcap.addMailcap("application/x-pkcs7-signature;; x-java-content-handler=org.bouncycastle.mail.smime.handlers.x_pkcs7_signature"); _mailcap.addMailcap("application/x-pkcs7-mime;; x-java-content-handler=org.bouncycastle.mail.smime.handlers.x_pkcs7_mime"); _mailcap.addMailcap("multipart/signed;; x-java-content-handler=org.bouncycastle.mail.smime.handlers.multipart_signed"); CommandMap.setDefaultCommandMap(_mailcap); }


- To provide and maintain the Service
- To notify you about changes to our Service
- To allow you to participate in interactive features of our Service when you choose to do so
- To provide customer care and support
- To provide analysis or valuable information so that we can improve the Service
- To monitor the usage of the Service
- To detect, prevent and address technical issues
Transfer Of Data
Your information, including Personal Data, may be transferred to — and maintained on — computers located outside of your state, province, country or other governmental jurisdiction where the data protection laws may differ than those from your jurisdiction.
If you are located outside United States and choose to provide information to us, please note that we transfer the data, including Personal Data, to United States and process it there.
Your consent to this Privacy Policy followed by your submission of such information represents your agreement to that transfer.
Clarify | Music Your Way will take all steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy and no transfer of your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of your data and other personal information.
Disclosure Of Data
Legal Requirements
Clarify | Music Your Way may disclose your Personal Data in the good faith belief that such action is necessary to:
- To comply with a legal obligation
- To protect and defend the rights or property of Clarify | Music Your Way
- To prevent or investigate possible wrongdoing in connection with the Service
- To protect the personal safety of users of the Service or the public
- To protect against legal liability
Security Of Data
The security of your data is important to us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.
Service Providers
We may employ third party companies and individuals to facilitate our Service ("Service Providers"), to provide the Service on our behalf, to perform Service-related services or to assist us in analyzing how our Service is used.
These third parties have access to your Personal Data only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose.
Links To Other Sites
Our Service may contain links to other sites that are not operated by us. If you click on a third party link, you will be directed to that third party's site. We strongly advise you to review the Privacy Policy of every site you visit.
We have no control over and assume no responsibility for the content, privacy policies or practices of any third party sites or services.
Children's Privacy
Our Service does not address anyone under the age of 18 ("Children").
We do not knowingly collect personally identifiable information from anyone under the age of 18. If you are a parent or guardian and you are aware that your Children has provided us with Personal Data, please contact us. If we become aware that we have collected Personal Data from children without verification of parental consent, we take steps to remove that information from our servers.
Changes To This Privacy Policy
We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page.
We will let you know via email and/or a prominent notice on our Service, prior to the change becoming effective and update the "effective date" at the top of this Privacy Policy.
You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.
Contact Us
If you have any questions about this Privacy Policy, please contact us:
By visiting this page on our website: Contact Us


UKCloud Limited (“UKC”) and Virtual Infrastructure Group Limited (“VIG”) (together “the Companies”) – in Compulsory Liquidation
On 25 October 2022, the Companies were placed into Liquidation with the Official Receiver appointed as Liquidator and J Robinson and A M Hudson simultaneously appointed as Special Managers to manage the liquidation process on behalf of the Official Receiver.
Further information regarding the Liquidations can be found here: https://www.gov.uk/government/news/virtual-infrastructure-group-limited-and-ukcloud-limited-information-for-creditors-and-interested-parties
Contact details:
For any general queries relating to the Liquidations please email<EMAIL_ADDRESS>For customer related queries please email<EMAIL_ADDRESS>For supplier related queries please email<EMAIL_ADDRESS>Understanding PSN core services
Overview
This document outlines the responsibilities between you and UKCloud with regards to Public Services Network (PSN) core services, such as DNS.
The intended audience is organisations who are either consuming or presenting a service over the PSN --- both PSN Assured and PSN Protected.
To be connected to the PSN, you must have a PSN compliance certificate. For more information, see https://www.gov.uk/guidance/public-services-network-psn-compliance.
In this article, we use PSN to represent both PSN Protected and PSN Assured unless otherwise specified.
PSN core services
While you can procure PSN connectivity from multiple service providers, PSN core services are provided by Vodafone (gateways) and Nominet (DNS). Traditionally, this was through the GSI Convergence Framework (GCF), whereby all core services were bundled into a single contract, regardless of whether you used them all.
Core services include:
DNS
Gateways to other networks, both government and public
UKCloud has procured PSN connectivity on your behalf, giving you access to the PSN through a shared bandwidth model. We'll supply you with PSN IP addresses, enabling you to present and consume services over the PSN.
PSN connectivity does not grant you access to PSN core services. Access to these must be purchased as a separate contract with Vodafone, and is available through Government Digital Marketplace (G-Cloud) or via Direct Award through the Network Services Framework with Vodafone. If you are a commercial organisation then you can take a contract out directly with Vodafone or Nominet for core services.
Making changes to PSN core services
When you have a contract with Vodafone or Nominet for PSN core services, you can add and change these to suit your service.
To add or change the core services, complete the appropriate forms and send them to Vodafone or Nominet for approval to raise a change. Depending on the contract you have with Vodafone or Nominet , you will need to raise these changes differently.
GCF contract customers
If you have a GCF contract still in place with Vodafone, complete and submit the GCF change form:
https://www.gov.uk/government/publications/gcf-customer-change-form
For DNS changes a ticket should be raised with Nominet:
https://nominetpsn.atlassian.net
G-Cloud, direct award or commercial contract customers
If you have contracted through G-Cloud, have been directly awarded a contract or have a commercial contract with Vodafone, complete and submit the PSN change forms:
https://www.gov.uk/government/publications/psn-dns-change-forms
Responsibilities
When completing the change forms, it's important that you complete the correct forms and that they are submitted by the correct people.
As per GDS guidance, requests for new PSN domain names must be accompanied by the PSN domain name authorisation form. This needs to be completed by the domain contract owner.
All requests for changes to the core services must come from the core service contract owner. If anyone else requests changes then they will be referred to the contract owner, which could cause a delay.
Customer responsibility
When you're given PSN connectivity by UKCloud, we'll provide you with all the IP information you require to submit a PSN core service change request to Vodafone or Nominet. You are responsible for the creation of domain names and additional information that may need to be submitted in the change form.
You are responsible for completing and submitting the PSN core service change forms.
UKCloud's responsibility
UKCloud has no responsibility for facilitating a contract between Vodafone or Nominet and our customers or partners for PSN core services. You must approach and contract with Vodafone or Nominet directly.
UKCloud has no responsibility for completing or submitting any change forms for changes to PSN core services on behalf of customers or partners. We may help you complete the form but you are ultimately responsible for validating and submitting the forms. UKCloud does not accept responsibility for incorrect information supplied within the change forms.
Complex responsibility
In certain circumstances, there may be complex aspects to responsibility:
Scenario 1 - If a non-government organisation has not got a direct contract with Vodafone or Nominet, but is contracted through a managed service provider, then responsibilities may be shared between the organisation and MSP.
Both parties may need to complete the form, however as per GDS guidance, it is ultimately the domain contract owner who owns the validation and submission of the forms. The domain contract should sit with the non-government organisation and not the managed service provider.
Scenario 2 - If a non-government organisation is currently hosted on a different hosting provider, and is thinking about moving to UKCloud, then they need to consider their current contracting relationship for core services with Vodafone or Nominet.
If the non-government organisation has no direct contract with Vodafone or Nominet but is contracted through the hosting provider, then when they move to UKCloud they may need to take out a new contract directly with Vodafone or Nominet for PSN core services.
Another consideration is the domain contract ownership. As only the domain contract owner can validate and submit change requests, it's important to ensure that the domain is owned by the non-government organisation, and not the hosting provider. If the hosting provider is the current domain contract owner, then the non-government organisation should work with the hosting provider to change the ownership before moving services to UKCloud.
New PSN DNS
A new PSN DNS is being developed that will be free at the point of use for PSN users, relieving them of the responsibility to contract with Nominet for DNS services.
For more information visit https://www.gov.uk/guidance/introducing-the-uk-public-sector-dns
More information
For more information about PSN, see the Public Services Network (PSN) FAQs.
Feedback
If you find a problem with this article, click Improve this Doc to make the change yourself or raise an issue in GitHub. If you have an idea for how we could improve any of our services, send an email to feedback@ukcloud.com.


Sessions that are complete with lead presenters that have complete profiles awaiting approval or denial.


@* * Copyright 2021 HM Revenue & Customs * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. *@ @import testOnly.views.html.templates.stub_template @import testOnly.models.SchemaModel @import testOnly.forms.StubSchemaForm._ @import testOnly.views.html.helpers._ @import uk.gov.hmrc.play.views.html.helpers.form @(stubSchemaForm: Form[SchemaModel], postAction: Call, showSuccess: Boolean, errorMessage: Option[String])(implicit request: Request[_], messages: Messages, appConfig: config.FrontendAppConfig) @stub_template(title = "ITVC Stub Schemas", bodyClasses = None) { @summaryErrorHelper(stubSchemaForm)
@errorMessage.get


@Target(value={METHOD,FIELD}) @Retention(value=RUNTIME) public @interface RDFSubject
Applied to: Method declaration
Value: prefix
(String, optional)
@RDFSubject annotation indicates that the annotated getter method returns a value of the RDFBean object identifier property.
An RDFBean class or interface should declare only one identifier property. If the property is declared, all identifier properties inherited from other classes (interfaces) are ignored. Otherwise, if no identifier property is declared on a given class or interface, it can be inherited from the nearest ancestors.
If no identifier property is found in the classes/interfaces hierarchy, the RDFBean object cannot be represented with an RDF resource in the model. However, it is still possible to represent it as a blank node (anonymous RDFBean).
The prefix
parameter defines the optional prefix part of RDFBean identifier and must contain either a namespace URI or a reference to namespace defined by RDFNamespaces
annotation.
If the prefix is specified, it is expected that the method returns a local part of RDFBean identifier. Otherwise, the method must return a value of RDFBean identifier as a fully qualified name.
Examples:
@RDFSubject(prefix="http://rdfbeans.example.com/persons/")
public String getPersonId() {
...
@RDFNamespaces("persons=http://rdfbeans.example.com/persons/");
...
@RDFSubject(prefix="persons:")
public String getPersonId() {
...
@RDFSubject
public String getPersonId() {
... // A fully qualified name must be returned
public abstract String prefix
An optional namespace prefix of RDFBean identifiers
Copyright © 2017. All rights reserved.


In any kind of creative endeavour there is bound to be a lot of trial and error.It is difficult to get things right the first time.I had to learn that the hard way.It is important therefore to have a place where one is free to experiment.A laboratory where it is okay to make mistakes.Where the only way to learn is by doing.This is probably the reason why many craftsmen never talk about their work until they are done with it.They like to work in the shadows where they are not being observed.Obscurity is warm blanket for the frosty process of creativity.
There is a reason I call creativity a cold process.Any artist will tell you they spend months of sleepless nights working on their art.They just can’t help it.Often midway they realize that the idea they have been working on is just not good enough.This is very common.Until a possibility is explored, peeked into there is no way to tell if it is good or bad.Some times it will require little tweaking other times a complete rework.Either way it is unlikely that the final product will come out exactly as you imagined it at the commencement.It can be gut wrenching to start all over again with fresh ideas.But this is exactly what most of us do.
Now imagine that instead of working in the darkness you publicize what you are doing and have all the attention on your work.Would you be be comfortable working, knowing that you are in the limelight?Would any one be?I don’t think so.It will be hard to try out new ideas knowing that if you fail there is a possibility of humiliation and embarrassment.It will prohibit risks and force you to play safe.This is where obscurity can be helpful.It shields us from fear of public failure.It provides a genial environment where one is free to experiment with different ideas.
I made my share of mistakes with brislink, there were some ideas that failed (actually it failed entirely).But those ideas failed quickly and cheaply .It was a great learning experience for me.I spent time exploring different ideas and learning new technologies.I am stronger, better and more confident.There is no guarantee that what I am doing now will succeed.But that won’t stop me from looking into new possibilities and if I fail no one needs to know.
brislink has reincarnated as specter, the posts in the brislink blog have moved to my personal blog


The purpose of this page is to serve as a space to test iNat API Queries for the Forest Health Watch Program.
View more observations from Western Redcedar Dieback Map on
iNaturalist »


above |
Ch'ien The Creative, Heaven |
|
below |
Ken Keeping Still, Mountain |
Retreat. Success.
In what is small, perseverance furthers.
Mountain under heaven: the image of Retreat.
Thus the superior man keeps the inferior man at a distance,
Not angrily but with reserve.
Six at the beginning means:
At the tail in retreat. This is dangerous.
One must not wish to undertake anything.
Six in the second place means:
He holds him fast with yellow oxhide.
No one can tear him loose.
Nine in the third place means:
A halted retreat
Is nerve-wracking and dangerous.
To retain people as men- and maidservants
Brings good fortune.
Nine in the fourth place means:
Voluntary retreat brings good fortune to the superior man
And downfall to the inferior man.
Nine in the fifth place means:
Friendly retreat. Perseverance brings good fortune.
Nine at the top means:
Cheerful retreat. Everything serves to further.


Tag: array
-
Leetcode 0011. Container With Most Water (14 Aug 2021)
-
Leetcode 0027. Remove Element (14 Aug 2021)
-
Leetcode 0031. Next Permutation (14 Aug 2021)
-
Leetcode 0034. Find First and Last Position of Element in Sorted Array (14 Aug 2021)
-
Leetcode 0041. First Missing Positive (14 Aug 2021)
-
Leetcode 0056. Merge Intervals (14 Aug 2021)
-
Leetcode 0057. Insert Interval (14 Aug 2021)
-
Leetcode 0080. Remove Duplicates from Sorted Array II (14 Aug 2021)
-
Leetcode 0088. Merge Sorted Array (14 Aug 2021)
-
Leetcode 0090. Subsets II (14 Aug 2021)
-
Leetcode 0128. Longest Consecutive Sequence (14 Aug 2021)
-
Leetcode 0135. Candy (14 Aug 2021)
-
Leetcode 0162. Find Peak Element (14 Aug 2021)
-
Leetcode 0163 Missing Ranges (14 Aug 2021)
-
Leetcode 0229. Majority Element II (14 Aug 2021)
-
Leetcode 0243 Shortest Word Distance (14 Aug 2021)
-
Leetcode 0245. Shortest Word Distance III (14 Aug 2021)
-
Leetcode 0277. Find the Celebrity (14 Aug 2021)
-
Leetcode 0280 Wiggle Sort (14 Aug 2021)
-
Leetcode 0300. Longest Increasing Subsequence (14 Aug 2021)
-
Leetcode 0307. Range Sum Query - Mutable (14 Aug 2021)
-
Leetcode 0334. Increasing Triplet Subsequence (14 Aug 2021)
-
Leetcode 0339. Nested List Weight Sum (14 Aug 2021)
-
Leetcode 0360. Sort Transformed Array (14 Aug 2021)
-
Leetcode 0370. Range Addition (14 Aug 2021)
-
Leetcode 0442. Find All Duplicates in an Array (14 Aug 2021)
-
Leetcode 0495. Teemo Attacking (14 Aug 2021)
-
Leetcode 0509. Fibonacci Number (14 Aug 2021)
-
Leetcode 0532. K-diff Pairs in an Array (14 Aug 2021)
-
Leetcode 0546. Remove Boxes (14 Aug 2021)
-
Leetcode 0581. Shortest Unsorted Continuous Subarray (14 Aug 2021)
-
Leetcode 0605. Can Place Flowers (14 Aug 2021)
-
Leetcode 0621. Task Scheduler (14 Aug 2021)
-
Leetcode 0665. Non-decreasing Array (14 Aug 2021)
-
Leetcode 0667. Beautiful Arrangement II (14 Aug 2021)
-
Leetcode 0713. Subarray Product Less Than K (14 Aug 2021)
-
Leetcode 0714. Best Time to Buy and Sell Stock with Transaction Fee (14 Aug 2021)
-
Leetcode 0735. Asteroid Collision (14 Aug 2021)
-
Leetcode 0746. Min Cost Climbing Stairs (14 Aug 2021)
-
Leetcode 0775. Global and Local Inversions (14 Aug 2021)
-
Leetcode 0795. Number of Subarrays with Bounded Maximum (14 Aug 2021)
-
Leetcode 0804. Unique Morse Code Words (14 Aug 2021)
-
Leetcode 0845. Longest Mountain in Array (14 Aug 2021)
-
Leetcode 0849. Maximize Distance to Closest Person (14 Aug 2021)
-
Leetcode 0870. Advantage Shuffle (14 Aug 2021)
-
Leetcode 0915 Partition Array into Disjoint Intervals (14 Aug 2021)
-
Leetcode 0927. Three Equal Parts (14 Aug 2021)
-
Leetcode 0932. Beautiful Array (14 Aug 2021)
-
Leetcode 0941. Valid Mountain Array (14 Aug 2021)
-
Leetcode 0954. Array of Doubled Pairs (14 Aug 2021)
-
Leetcode 0969. Pancake Sorting (14 Aug 2021)
-
Leetcode 0977. Squares of a Sorted Array (14 Aug 2021)
-
Leetcode 1004. Max Consecutive Ones III (14 Aug 2021)
-
Leetcode 1007. Minimum Domino Rotations For Equal Row (14 Aug 2021)
-
Leetcode 1010. Pairs of Songs With Total Durations Divisible by 60 (14 Aug 2021)
-
Leetcode 1125. Smallest Sufficient Team (14 Aug 2021)
-
Leetcode 1133. Largest Unique Number (14 Aug 2021)
-
Leetcode 1187. Make Array Strictly Increasing (14 Aug 2021)
-
Leetcode 1217. Minimum Cost to Move Chips to The Same Position (14 Aug 2021)
-
Leetcode 1224. Maximum Equal Frequency (14 Aug 2021)
-
Leetcode 1250. Check If It Is a Good Array (14 Aug 2021)
-
Leetcode 1266. Minimum Time Visiting All Points (14 Aug 2021)
-
Leetcode 1330. Reverse Subarray To Maximize Array Value (14 Aug 2021)
-
Leetcode 1335. Minimum Difficulty of a Job Schedule (14 Aug 2021)
-
Leetcode 1340. Jump Game V (14 Aug 2021)
-
Leetcode 1383. Maximum Performance of a Team (14 Aug 2021)
-
Leetcode 1402. Reducing Dishes (14 Aug 2021)
-
Leetcode 1406. Stone Game III (14 Aug 2021)
-
Leetcode 1423. Maximum Points You Can Obtain from Cards (14 Aug 2021)
-
Leetcode 1425. Constrained Subsequence Sum (14 Aug 2021)
-
Leetcode 1437. Check If All 1s Are at Least Length K Places Away (14 Aug 2021)
-
Leetcode 1480. Running Sum of 1d Array (14 Aug 2021)
-
Leetcode 1499. Max Value of Equation (14 Aug 2021)
-
Leetcode 1526 Minimum Number of Increments on Subarrays to Form a Target Array (14 Aug 2021)
-
Leetcode 1539. Kth Missing Positive Number (14 Aug 2021)
-
Leetcode 1553. Minimum Number of Days to Eat N Oranges (14 Aug 2021)
-
Leetcode 1563. Stone Game V (14 Aug 2021)
-
Leetcode 1569. Number of Ways to Reorder Array to Get Same BST (14 Aug 2021)
-
Leetcode 1575. Count All Possible Routes (14 Aug 2021)
-
Leetcode 1595. Minimum Cost to Connect Two Groups of Points (14 Aug 2021)
-
Leetcode 1601. Maximum Number of Achievable Transfer Requests (14 Aug 2021)
-
Leetcode 1606. Find Servers That Handled Most Number of Requests (14 Aug 2021)
-
Leetcode 1640. Check Array Formation Through Concatenation (14 Aug 2021)
-
Leetcode 1646. Get Maximum in Generated Array (14 Aug 2021)
-
Leetcode 1675. Minimize Deviation in Array (14 Aug 2021)
-
Leetcode 1690. Stone Game VII (14 Aug 2021)
-
Leetcode 1710. Maximum Units on a Truck (14 Aug 2021)
-
Leetcode 1835. Find XOR Sum of All Pairs Bitwise AND (14 Aug 2021)
-
Leetcode 1899. Merge Triplets to Form Target Triplet (14 Aug 2021)
-
Leetcode 1911. Maximum Alternating Subsequence Sum (14 Aug 2021)
-
Leetcode 1923. Longest Common Subpath (14 Aug 2021)