La description :blog personal de damià pages about cookies blogroll damia english blog securityartwork archives archives select month december 2015 (1) september 2014 (1) february 2012 (1) may 2011 (2) october 2010 (...
Classement Alexa Global: # 4,173,109
Server:Apache/2.4.25...
L'adresse IP principale: 91.121.102.12,Votre serveur France,Roubaix
ISP:OVH SAS TLD:net Code postal:fr
Ce rapport est mis à jour en 04-Aug-2018
Created Date:
1997-09-27
Changed Date:
2017-02-25
Données techniques du damia.net
Geo IP vous fournit comme la latitude, la longitude et l'ISP (Internet Service Provider) etc. informations.
Notre service GeoIP a trouvé l'hôte damia.net.Actuellement, hébergé dans France et son fournisseur de services est OVH SAS .
Les informations d'en-tête HTTP font partie du protocole HTTP que le navigateur d'un utilisateur envoie à appelé Apache/2.4.25 contenant les détails de ce que le navigateur veut et acceptera de nouveau du serveur Web.
MX preference = 10, mail exchanger = correo.damia.net.
HtmlToText
blog personal de damià pages about cookies blogroll damia english blog securityartwork archives archives select month december 2015 (1) september 2014 (1) february 2012 (1) may 2011 (2) october 2010 (1) august 2010 (1) april 2010 (1) february 2010 (1) october 2009 (1) july 2009 (1) march 2009 (1) december 2008 (1) october 2008 (1) september 2008 (1) july 2008 (1) march 2008 (1) january 2008 (4) december 2007 (9) november 2006 (3) september 2006 (1) august 2006 (3) july 2006 (2) june 2006 (2) april 2006 (1) march 2006 (3) february 2006 (1) december 2005 (2) october 2005 (3) june 2005 (3) may 2005 (7) april 2005 (3) march 2005 (7) february 2005 (1) january 2005 (3) december 2004 (5) november 2004 (2) october 2004 (1) september 2004 (4) august 2004 (1) july 2004 (6) june 2004 (8) may 2004 (6) april 2004 (8) march 2004 (3) february 2004 (4) january 2004 (6) december 2003 (5) november 2003 (9) october 2003 (3) august 2003 (1) july 2003 (1) june 2003 (1) automatización de let’s encrypt en debian december 3, 2015 by damia gracias a la inciativa https://letsencrypt.org/ respaldado por akamai, cisco, mozilla and eff, vamos a poder disponer de certificados ssl gratuitos. en este post os explicare como he automatizado el proceso de generación y renovación en un servidor debian, con diversos virtualhost, modificando lo menos posible y de una manera muy controlada los ficheros de configuración de apache. la intención del proyecto letsencrypt es extender al máximo la utilización de certificados ssl, para ello los propios servidores podran autogenerar sus certificados sin interacción manual, para forzar que todo sea automatico, los certificados tendran 90 dias de validez, obligandonos a todos los administradores de sistemas a automatizar el proceso. para generar un certicado, la autoridad de certificación de let’s encrypt, consulta el dns y accede a tu servidor web preguntandole por unas credenciales para de esta manera validar la generación o renovación del certificado. por lo tanto el servidor web debe de responder a las consultas realizadas por ca, para la emisión y renovación de los certificados. el software de letsencrypt es capaz de modificar los ficheros de configuración de apache, o incluso levantar un servidor propio. ninguno de los dos metodos me convencen, quiero tener pleno control de todas las modificaciones en la configuración de apache, dispongo de diversidad de virtualhost con configuraciones muy especificas, el levantar un servidor independiente hace que dejes de dar servicio por lo que tampoco es aceptable. afortunadamente letsencrypt proporciona un mecanismo denominado webroot, por el cual lo unico que necesita es dejar un fichero en algun lgugar accesible del website, con este modo podemos automatizar plenamente el proceso y mantener pleno control sobre lo que esdta sucediendo. lo primero de todos es seguir la instrucciones de instalación de letsencrypt (probado en debian jessie y debian wheezy) apt-get install git git clone https://github.com/letsencrypt/letsencrypt cd letsencrypt ./letsencrypt-auto vamos allá, la única modificación necesaria en cada virtualhost para poder responder a la autenticación de let’s encrypt es: alias /.well-known /var/www/html/le/.well-known reiniciamos el apache, y ya podemos lanzar el comando para la emisión y renovación del certificado. /root/.local/share/letsencrypt/bin/letsencrypt --renew-by-default -a webroot --webroot-path /var/www/html/le/ --server https://acme-v01.api.letsencrypt.org/directory --email admin@damia.net --text --agree-tos --agree-dev-preview -d eblog.damia.net auth con esto ya tenemos los certificados listos: /etc/letsencrypt/live/eblog.damia.net/cert.pem /etc/letsencrypt/live/eblog.damia.net/chain.pem /etc/letsencrypt/live/eblog.damia.net/fullchain.pem /etc/letsencrypt/live/eblog.damia.net/privkey.pem podemos añadir otro virtualhost en el puerto 443, con: [...] sslengine on sslcertificatefile /etc/letsencrypt/live/eblog.damia.net/cert.pem sslcertificatekeyfile /etc/letsencrypt/live/eblog.damia.net/privkey.pem sslcertificatechainfile /etc/letsencrypt/live/eblog.damia.net/fullchain.pem [...] hecho, ya tenemos nuestra web segura. ahora podemos automatizar el proceso de creación y renovación de certificados, he desarrollado un script que realiza las siguiente tareas: comprueba la fecha de expiración de los certificados y los renueva cuando estan por debajo de un numero de dias definido. comprueba que letsencrypt puede acceder al directorio de validación envia un correo al administrador si no puede renovar lso certificados. puedes ver el codigo a continuación o descargarte el fichero desde aqui: autole #!/bin/bash ## ## ## lets encrypt automation ## ## by damia soler ## contact damia (at) damia (dot) net ## https://blog.damia.net ## https://github.com/damiadev/autole/ ## ## ##================================================== ## setup ## ## ## ## remaining days to expire before renew ## daystorenew=10 ## ## remaining days to expire before alert ## daystoalert=5 ## ## email to alert if unable to renew ## alertemail=root@localhost ## ## email account on lets encrypt ## leemail=admin@example.com ## webroot=/www/htdocs/le/ ##webroot=/www/htdocs/le/$1 ## ## lebin=/root/.local/share/letsencrypt/bin/letsencrypt ## certfile=/etc/letsencrypt/live/$1/cert.pem ##==================================================================================== if test $1 = "--renew-all" ; then echo checking certificates ls -1 /etc/letsencrypt/live|xargs -n1 $0 ; /etc/init.d/apache2 graceful exit ; fi; ##==================================================================================== if test -a $certfile ; then d1=$(date -d "`openssl x509 -in $certfile -text -noout|grep "not after"|cut -c 25-`" +%s) d2=$(date -d "now" +%s) days=` echo \( $d1 - $d2 \) / 86400 |bc ` echo -n `date` domain $1 will expire in $days days " " else echo -n `date` domain $1 new days=$daystoalert; fi; if test $days -lt $daystorenew ; then echo trying to renew ; ### pretest to not mess le servers if you are not answering the challenge testfile=$random echo test> $webroot/.well-known/acme-challenge/$testfile url=http://$1/.well-known/acme-challenge/$testfile mkdir -p $webroot/.well-known/acme-challenge touch $webroot/.well-known/acme-challenge/index.html echo test> $webroot/.well-known/acme-challenge/$testfile if curl --output /dev/null --silent --head --fail "$url"; then echo $lebin --renew-by-default -a webroot --webroot-path $webroot --email $leemail --text --agree-tos -d $1 auth $lebin --renew-by-default -a webroot --webroot-path $webroot --email $leemail --text --agree-tos -d $1 auth echo sslengine on echo sslcertificatefile /etc/letsencrypt/live/$1/cert.pem echo sslcertificatekeyfile /etc/letsencrypt/live/$1/privkey.pem echo sslcertificatechainfile /etc/letsencrypt/live/$1/fullchain.pem else echo "can not access the pre-challenge $url please add alias to your virtualhost conf" ; echo "alias /.well-known $webroot/.well-known" ; fi rm $webroot/.well-known/acme-challenge/$testfile else echo no close to expire ; fi ; if test $days -lt $daystoalert ; then echo alert domain $1 certificate renewal problem|mail $alertemail ; echo alert domain $1 certificate renewal problem ; fi; you can use ./autole www.mydomain.com and you will have your new certificate available for this domain. (remeber to add previously the alias on apache). and ./autole --renew-all and all your certificates will be renewed. the idea is to add this to the crontab, and your certificates will be ready and renew automatically. aviso: a día de hoy con debian 9 “stretch” ya no es necesario hacer este hack, el paquete dehydrated que viene en la propia distribución hace todo el trabajo de manera similar. filed under: cosas tecnicas , varios lego wedo en debian con scratch september 7, 2014 by damia recientemente le he comprado a mi hijo el juego lego wedo , se compone de diversas piezas de lego technic y un hub usb al que le puedes conectar un motor y dos sensores, uno de distanci
Whois est un protocole qui permet d'accéder aux informations d'enregistrement.Vous pouvez atteindre quand le site Web a été enregistré, quand il va expirer, quelles sont les coordonnées du site avec les informations suivantes. En un mot, il comprend ces informations;
For more information on Whois status codes, please visit https://icann.org/epp
NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.
TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.
The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.
REGISTRAR Domain.com, LLC
SERVERS
SERVER net.whois-servers.net
ARGS domain =damia.net
PORT 43
TYPE domain RegrInfo DOMAIN
NAME damia.net
CHANGED 2017-02-25
CREATED 1997-09-27
STATUS clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Nous utilisons des cookies pour personnaliser votre expérience sur notre site. En poursuivant votre navigation, vous acceptez cette utilisation. Apprendre encore plus
damia.net rapport :
Visitez le site