Hot answers tagged

4

openpgp.org has a facility for https. Just imported a few keys by their fingerprints. The path is predictable you just need to replace ${KEY_FINGERPRINT} with the fingerprint of the key you want to import. Which of course must be already uploaded to https://keys.openpgp.org: curl --sSL https://keys.openpgp.org/vks/v1/by-fingerprint/${KEY_FINGERPRINT} | \ ...


3

EDIT: Debugging the user setup, it was found with netstat there is already a process using 1996/TCP: netstat -nlp | grep 1996 tcp 0 0 0.0.0.0:1996 0.0.0.0:* LISTEN 4729/python So the configuration examples, were changed to 1997/TCP. Apache/mod_ssl have to be told 1997/TCP and 1980/TCP are HTTPS ports. By default 443/TCP is already known, but any others ...


3

I don't know what most administrators do after that, but I can tell you what I do before executing something like that: I look for a package for the distribution I intend to use, and if I do not find one satisfying my requirements, either I'll create a new sandbox, install the software there and check what the installation did and the software does, or I'll ...


2

The security updates can't be retrieved from https connection , explained on debian The security.debian.org hosts currently do not have publicly verifiable SSL certificates on HTTPS and hence cannot be used with HTTPS at the moment. Your can edit your /etc/apt/sources.list as follow: deb https://deb.debian.org/debian jessie main deb http://security....


1

A HTTP/1 response requires a HTTP header (status code, meta data) and a HTTP body (i.e. the content). Your index.html is likely only the content. If this is an accepted response depends on your client supporting the more than 20 year obsolete HTTP/0.9 protocol (where no header is sent) or not. Many don't.


1

You have not enabled SSL in your nginx server {} block. The line that needs changing: listen 3120 ; should instead be: listen 3120 ssl; This will enable SSL for that nginx server {} block, but if you have not noticed already, HTTP (non-SSL) will stop working on port 3120. You may be able to set that server {} block to listen to both HTTP and HTTPS ...


1

After some further research, I found conntrack achieves what I need -- specifically conntrack -E provides a list of active incoming connections.


1

In general, this isn't possible. For it to be possible, it must be the case that either (1) SSH-over-443 is being done naively rather than actually being tunneled over SSL, or (2) you're breaking all SSL connections and have convinced all clients to accept your fake root CA.


1

In order to use Apache as a Reverse Proxy, make sure you have modules mod_proxy and mod_proxy_http enabled in your server (e.g. sudo a2enmod proxy_http). Add ProxyPass and ProxyPassReverse to the bottom of your VirtualHost sections and you should be good. Restart the server afterwards with sudo service apache2 restart. <VirtualHost *:80> # ...


1

In case anyone else is coming across this error from within vmWare ESXi or another BusyBox environment, you aren't actually using wget: Output from wget -V for me: wget: invalid option -- 'V' BusyBox v1.22.1 (2018-07-23 19:34:44 PDT) multi-call binary. Usage: wget [-csq] [-O FILE] [-Y on/off] [-P DIR] [-U AGENT] URL... Retrieve files via HTTP or FTP ...


Only top voted, non community-wiki answers of a minimum length are eligible