Portal:Java Security/Certification Articles

Comments

(no comments yet)

Log in or Join to leave comments.

This portal contains Java ME topics associated with: Category:Security, Category:Authentication, Category:Platform Security, Category:SSL/TLS, Category:Signing and Certification, Category:Java Verified, Category:Security and Trust Services API (JSR-177), Category:Self Signed.

Recently Edited Jad & manifest entries/attributes . . balagopalks Signed to Either Operator or Manufacturer Domain . . balagopalks How to conform with Unified Testing Criteria . . skalogir Java Verified . . skalogir Encrypting and decrypting in Java ME . . jumantyn Thawte signing for Java ME . . hamishwillee Create a certificate using OpenSSL . . mgroeber9110 Java Security Domains . . traud API access rights on phones, Series 40 6th FP1 . . traud RIPEMD160 encryption in JavaME . . cipiripper MIDP 2.0 API access rights . . liahoy OVI Certificates . . oviJude Domain name with spaces in certificate path results in MIDlet installation failure on S60 (Known Issue) . . Forum Nokia KB API access rights on phones, Series 40 6th . . r2j7 Signed HelloWorld example MIDlet . . traud

Most Viewed Java Security Domains How to conform with Unified Testing Criteria AT&T Java security domains OVI Certificates Jad & manifest entries/attributes Verisign signing - Java ME Java Verified AT&T API access rights v3 Create a certificate using OpenSSL Thawte signing for Java ME API access rights on phones, Series 40 6th Java ME signing for dummies Encrypting and decrypting in Java ME API access rights on phones, Series 40 3rd FP1 AT&T API access rights v1

Code Examples

There are 1 Code Example (Articles with downloadable source code packages).

R

• RIPEMD160 encryption in JavaME

Articles

There are 46 Articles (without downloadable source code packages.)

A API access rights on phones, S60 2nd FP2 API access rights on phones, S60 2nd FP3 API access rights on phones, Series 40 3rd FP1 API access rights on phones, Series 40 3rd FP2 API access rights on phones, Series 40 5th FP1 API access rights on phones, Series 40 6th API access rights on phones, Series 40 6th FP1 AT&T API access rights v1 AT&T API access rights v3 AT&T Java security domains AT&T branded 6085 C China Unicom Java security domains Create a certificate using OpenSSL D Designing your MIDlet for JavaVerified Domain name with spaces in certificate path results in MIDlet installation failure on S60 (Known Issue) E Encrypting and decrypting in Java ME

E cont. Encryption of data using JSR-177 H How to change the Java API access settings on S60 phones How to change the Java API access settings on Series 40 phones How to conform with Unified Testing Criteria How to find the Java signing certificates on the phones Hutchinson 3G API access rights Hutchinson 3G security domains I Installation of a signed midlet fails J JTWI API access rights Jad & manifest entries/attributes Java ME signing for dummies Java Security Domains Java Verified M MIDP 2.0 API access rights MIDP 2.0.1 API access rights MIDP 2.1 API access rights

O OVI Certificates Obfuscation P Permissions S Security and Trust Services API Security and Trust Services API (JSR-177) Signed HelloWorld example MIDlet Signed to Either Operator or Manufacturer Domain Signing Signing process in Java ME Sprint Java security domains T T-Mobile U.S. API access rights T-Mobile U.S. Java security domains Thawte signing for Java ME V Verisign signing - Java ME

Archived

There are 7 Archived Articles/Code Examples

A Archived:API access rights on S60 3rd Edition devices Archived:API access rights on S60 3rd FP1 devices Archived:API access rights on S60 3rd FP2 devices

S Archived:SecureConnection with SSL connection string fails in Symbian^3 (Known Issue) Archived:Signed MIDlets with invalid country code fail to launch on S60 3rd Edition (Known Issue) V Archived:Variance in security domains for MIDlets on certain operator variant Series 40 2nd Edition phones (Known Issue)

V cont. Archived:VeriSign signed MIDlets cannot be installed on Series 40 5th Edition FP1 devices (Known Issue)

54