All Projects → fm4dd → webcert

fm4dd / webcert

Licence: MIT license
WebCert is a Web application to generate and manage digital certificates in cases where no "full" CA is needed.

Programming Languages

c
50402 projects - #5 most used programming language
HTML
75241 projects
shell
77523 projects
CSS
56736 projects

Projects that are alternatives of or similar to webcert

openssl ca
openssl_ca with QT GUI
Stars: ✭ 16 (-20%)
Mutual labels:  openssl, pki, certificate-authority
pki
Certificate Authority management suite
Stars: ✭ 23 (+15%)
Mutual labels:  openssl, pki, certificate-authority
openssl-ca
Shell scripts to manage a private Certificate Authority using OpenSSL
Stars: ✭ 38 (+90%)
Mutual labels:  openssl, certificate-authority
tls-ca-manage
Multi-level Certificate Authority Management tool, front-end tool to OpenSSL, written in bash shell.
Stars: ✭ 19 (-5%)
Mutual labels:  openssl, certificate-authority
Pric
Simple zero-config tool to create Private Certificate Authority & issue locally-trusted development server certificates with any domain names you'd like. SSL certificates for development purposes.
Stars: ✭ 87 (+335%)
Mutual labels:  openssl, certificate-authority
littleca
littleca是一个基于BC的小型ca库,支持ecc,rsa,dsa,sm2的证书签发,加密解密,签名验签操作,支持国密加解密,证书签发
Stars: ✭ 44 (+120%)
Mutual labels:  openssl, pki
Pebble
A miniature version of Boulder, Pebble is a small RFC 8555 ACME test server not suited for a production certificate authority. Let's Encrypt is hiring! Work on Pebble with us.
Stars: ✭ 359 (+1695%)
Mutual labels:  pki, certificate-authority
Libpki
Easy-to-use high-level library for PKI-enabled applications
Stars: ✭ 36 (+80%)
Mutual labels:  openssl, pki
Django X509
Reusable django app implementing x509 PKI certificates management
Stars: ✭ 326 (+1530%)
Mutual labels:  pki, certificate-authority
win-ca
Get Windows System Root certificates
Stars: ✭ 78 (+290%)
Mutual labels:  openssl, certificate-authority
Mutual Tls Ssl
🔐 Tutorial of setting up Security for your API with one way authentication with TLS/SSL and mutual mutual authentication for a java based web server and a client with both Spring Boot. Different clients are provided such as Apache HttpClient, OkHttp, Spring RestTemplate, Spring WebFlux WebClient Jetty and Netty, the old and the new JDK HttpClient, the old and the new Jersey Client, Google HttpClient, Unirest, Retrofit, Feign, Methanol, vertx, Scala client Finagle, Featherbed, Dispatch Reboot, AsyncHttpClient, Sttp, Akka, Requests Scala, Http4s Blaze, Kotlin client Fuel, http4k, Kohttp and ktor. Also other server examples are available such as jersey with grizzly. Also gRPC examples are included
Stars: ✭ 163 (+715%)
Mutual labels:  openssl, certificate-authority
x509sak
X.509 Swiss Army Knife is a toolkit atop OpenSSL to ease generation of CAs and aid white-hat pentesting
Stars: ✭ 23 (+15%)
Mutual labels:  openssl, pki
Pki
The Dogtag Certificate System is an enterprise-class Certificate Authority (CA) which supports all aspects of certificate lifecycle management, including key archival, OCSP and smartcard management.
Stars: ✭ 97 (+385%)
Mutual labels:  pki, certificate-authority
Boulder
An ACME-based certificate authority, written in Go.
Stars: ✭ 4,091 (+20355%)
Mutual labels:  pki, certificate-authority
labca
A private Certificate Authority for internal (lab) use, based on the open source ACME Automated Certificate Management Environment implementation from Let's Encrypt (tm).
Stars: ✭ 126 (+530%)
Mutual labels:  pki, certificate-authority
openssl-certificate-authority-guide
Bu kılavuz, OpenSSL komut satırı araçlarını kullanarak kendi sertifika yetkilinizi (CA) kurup nasıl kullanacağınızı gösterir.
Stars: ✭ 17 (-15%)
Mutual labels:  openssl, certificate-authority
Certificates
🛡️ A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management, so you can use TLS everywhere & SSO for SSH.
Stars: ✭ 3,693 (+18365%)
Mutual labels:  pki, certificate-authority
Xipki
Highly scalable and high-performance open source PKI (CA and OCSP responder). Minimal dependencies, No-JPA, No-Spring
Stars: ✭ 311 (+1455%)
Mutual labels:  pki, certificate-authority
Easycert
EasyCert quickly generates web server TLS certificates that have been self-signed by a private certificate authority that it also creates.
Stars: ✭ 121 (+505%)
Mutual labels:  openssl, certificate-authority
pki-manager
IT Freelancers : Manage small PKI for multiple projects (or clients) with 2 bash scripts
Stars: ✭ 36 (+80%)
Mutual labels:  openssl, pki

WebCert

test

A Web Tool for Generation and Management of digital Certificates

Digital Certificates are needed everywhere in today's world. They are used to enable secure SSL web traffic, e-mail encryption and other technologies.

To get a digital certificate, you'll either have to get one from a commercial provider (who usually charges $$$), or you have to install, configure and run your own certificate authority (also $$ and, at the very least something more to learn and manage, which is very time and resource consuming). Often we don't need the extensive functionality and complexity of a full CA management system.

As a result, I wrote WebCert to be able to quickly generate certificates on my own, and to enable my colleagues without knowledge of the details to do so as well. The first version became an instant hit with over 300 certificate generations per year. It encouraged me to improve it to the version you see here.

WebCert live URL

WebCert runs at http://webcert.fm4dd.com/

WebCert Design

WebCert is using the OpenSSL libraries for certificate operations. It is not just a frontend to the openssl program, but independently written. It only requires standard C libraries, the OpenSSL libraries and the CGIC library from Thomas Boutell. As a result, you don't need to maintain any of the web-application enabling technologies like JSP, PHP, Phyton... It is using simple CGI technology for easiest installation and maintenance.

External Dependencies:

Make sure you have: -I<path-to-cgic-includes> and -L<path-to-cgic-lib>, and -I<path-to-openssl-includes> and -L<path-to-openssl-lib> in the Makefiles

Configuration:

Apart from the Makefiles in the root and src/ directories, check the file webcert.h in the src/ directory. The upper section can be configured to set the URL location and the default webcert parameters.

Making and installing WebCert:

  • vi Makefile and src/Makefile to adjust various path's for cgi and html destinations and ssl include and library directories

  • vi src/webcert.h to adjust the path's for your webserver and cert store (if you have one - for listing of local certificate copies)

  • vi src/certsign.h if you want to adjust certificate properties such as lifetime, extensions, comments, etc

  • make && make install "make install" expects a directory structure somewhere below your document root i.e. apache/htdocs/webcert containing the following sub directories: images cgi-bin style. The application is expected to be accessed via URL http://<www.yourdomain.com>/webcert.

  • don't forget to enable the cgi directory in your webserver, i.e. in apache's httpd.conf add the line: ScriptAlias /webcert/cgi-bin/ "/var/apache/htdocs/webcert/cgi-bin/"

A more complete installation procedure is provided in INSTALL.

Security:

It is highly adviseable to provide access control and SSL encryption to the WebCert interface for any use other then experimental. The webserver writeable certificate and export directory should be secured (i.e. by a Apache directive).

Copyright and License:

WebCert was written by Frank4DD. It is distributed under the MIT license.

Legal Disclaimer:

Of course this software and its created certificates come WITHOUT ANY WARRANTY.

Thanks and Credits:

  • to Thomas Boutell for providing the CGIC library:
  • to the authors of O'Reilly's book "Network Security with OpenSSL" who provided a guiding "light" in the OpenSSL jungle.
  • to the authors of OpenSSL, whose code ensures that only the true & dedicated will learn its power ;-)

CGIC, copyright 1996, 1997, 1998, 1999, 2000, 2001, 2002 by Thomas Boutell and Boutell.Com, Inc.. Permission is granted to use CGIC in any application, commercial or noncommercial, at no cost. HOWEVER, this copyright paragraph must appear on a "credits" page accessible in the public online and offline documentation of the program. Modified versions of the CGIC library should not be distributed without the attachment of a clear statement regarding the author of the modifications, and this notice may in no case be removed. Modifications may also be submitted to the author for inclusion in the main CGIC distribution.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].