bonusfert.blogg.se - Aria2 toeken websites

ARIA2 TOEKEN WEBSITES PASSWORD

It took me a while to solve, so I'm going to share myĮxperience and understanding of the matter. I know this issue is a bit old but it has a good Pagerank on Google and I Send over a pull request and I would love to merge it in :) Adding directly to readme.md would be fine to e for now. You did really got job at explaining c3mb0!! We can make another fileĬalled setup_https.md and link it (maybe called setup https) from the Whew! You should now be able to fire up index.html from your computer at any time and have a fully encrypted and secret protected connection, assuming your ports are forwarded on the network of the machine that's running aria2. Openssl pkcs12 -export -out ia.p12 -inkey ia.key -in ia.crtĪria2c -enable-rpc -rpc-listen-all -rpc-certificate=/path/to/your/ia.p12 -rpc-secure -rpc-secret=yoursecret Since it's more convenient and more widely supported by aria2's supported TLS libraries ( see here), I like packing the certificate and its key into a PKCS12 file with the following: You can now use ia.crt with an external service, and your OS, and your OS only, will recognize it as legit. Openssl x509 -req -days 3650 -in ia.csr -CA ca.crt -CAkey ca.key -out ia.crt -CAcreateserial -extensions v3_req -extfile req.cnf Sign the request with your root certificate

ARIA2 TOEKEN WEBSITES PASSWORD

Openssl req -new -key ia.key -out ia.csr -config req.cnfĪgain, fill the additional information requested by openssl as you wish, but leave Common Name and Challenge Password as is. Now create a signing request with the configuration we just prepared:

Create a new section called and specify hosts where your aria2 will be running as such:.

Add subjectAltName = to the bottom of section.

I only see Organization Name within the storage, so I just change that to my liking and leave the rest as default.įor this step, create a copy of the openssl config file: They are not really important, fill them as you wish them to appear in the root certificate storage. Note: openssl will ask you some information for certificate details. Introduce the resulting ca.crt to your OS as a trusted root certificate. Openssl req -new -x509 -days 3650 -key ca.key -out ca.crt Start by creating a new directory and moving into it. Since we don't care about the rest of the world, what we can also do is to introduce our OS our own signature, and it will gladly accept any piece of paper signed with it. When you pay for an SSL certificate from GoDaddy, you're basically handing them a piece of paper for them to sign it, so that you can show it to other OSs and get recognized. Their root certificates are present on pretty much all OSs.

OSs come pre-installed with well established root certificates.

The list of signatures that the OS recognizes is called the root certificate storage. When the OS gets handed a piece of signed paper, it checks if the said paper is signed by someone it deems an authority. When you want to prove a 3rd party that a piece of paper is valid, you need to get it signed by an authority. If you press F12 on the index page and keep seeing net::ERR_INSECURE_RESPONSE on the console, then there's definitely something wrong with your certificates. Most probably, there's something wrong with your certificate setup. It took me a while to solve, so I'm going to share my experience and understanding of the matter. I know this issue is a bit old but it has a good Pagerank on Google and I kept landing here. I start aria2 with the following command line: /usr/bin/aria2c -enable-rpc (using systemd for curious people) # The magic happens with all the following lines # Not sure if these lines are important ProxyRequests Off # allow only users from the webui-aria2 group Require group webui-aria2 SSLCertificateKeyFile /etc/ssl/apache2/private/private.keyĪuthName "webui-aria2 " AuthUserFile th SSLCertificateFile /etc/ssl/apache2/certs/public.crt factory ( '$rpc', [ '$syscall', '$globalTimeout', '$alerts', '$utils', '$rootScope', '$location', '$authconf', function ( syscall, time, alerts, utils, rootScope, uri, authconf ) ĬustomLog /var/logs/apache/webui-aria2-access.log combinedĮrrorLog /var/logs/apache/webui-aria2-errors.log combined