SSL nachrüsten über Proxy?

[Jasch]

Hallo, folgendes Problem,
Windows Prog. (kein Sourcecode vorhanden, Developer seit Jahren nicht erreichbar) kann kein Https.

Tool lädt Infos und Bilder von Webdienst.
Bei den Bildern gibt es seit neusten einen 301 redirect auf https, somit Download failed.
Der Request ist ein ganz einfacher GET
GET /..../291517-2.jpg HTTP/1.1


Gibt es eine Möglichkeit, das Ganze mit einem Proxgebilde wieder zum laufen zu bringen?
Tool -> HTTP -> Proxy -> HTTPS-> Web
Web -> HTTPS -> Proxy -> HTTP -> Tool

Bin für Vorschläge ode Hinweise dankbar.

[PatkIllA]

Ich habe schon mal im Apache Konfigurationstools von Hardware durchgereicht.
Das klappt ganz gut solange die Teile mit relativen URLs arbeiten.
Einige Geräte generieren aber alle Links komplett ala http://ip/resources. Das kriegt man dann nicht so einfach zum laufen wenn protokoll oder Port anders sind.

[konkretor]

Da würde sich der haproxy anbieten


https://www.digitalocean.com/community/tutorials/how-to-implement-ssl-termination-with-haproxy-on-ubuntu-14-04

Oder Pound

http://www.ubuntugeek.com/load-balancing-httphttps-with-pound-on-ubuntu-14-04-server.html

[iuno]

Ja, klar geht das. Nennt sich dann reverse proxy mit SSL/TLS termination. nginx eignet sich dafuer etwa.

[qiller]

Hm, wenn das immer derselbe Server ist, der da angefunkt wird, geht vlt auch stunnel?

https://superuser.com/questions/582277/connect-to-an-https-service-using-an-http-only-client

mfg Oli

[Jasch]

Danke für die Hinweise, werde erstmal stunnel testen(kann man ja schön lokal installieren), da es immer der selbe server ist.
Berichte dann hier ob es funkt.
(auf der Pfsense is nen Reversproxy(Squid), ich probier erstmal den "einfachen) weg.

[Jasch]

Scheint leider nicht zu funktioneren.
Habe Stunnel installiert.
[TEST]
client = yes
accept = 127.0.0.1:80
connect = thetvdb.com:443
debug = 7

und mit Proxycap das Programm dazu bewegt den Proxy zu nutzen.
Das normale abrufen der Metadaten geht nach wie vor (auch über proxy).
Der Bilder Download scheitert leider trotzdem.
Im Stunnel ist aber nicht wirklich ein Fehler zu sehen.

Versuch eines Abrufes.


2018.02.27 18:35:47 LOG5[main]: stunnel 5.44 on x86-pc-msvc-1500 platform
2018.02.27 18:35:47 LOG5[main]: Compiled/running with OpenSSL 1.0.2m-fips 2 Nov 2017
2018.02.27 18:35:47 LOG5[main]: Threading:WIN32 Sockets:SELECT,IPv6 TLS:ENGINE,FIPS,OCSP,PSK,SNI
2018.02.27 18:35:47 LOG5[main]: Reading configuration from file stunnel.conf
2018.02.27 18:35:47 LOG5[main]: UTF-8 byte order mark detected
2018.02.27 18:35:47 LOG5[main]: FIPS mode disabled
2018.02.27 18:35:47 LOG4[main]: Service [TEST] needs authentication to prevent MITM attacks
2018.02.27 18:35:47 LOG5[main]: Configuration successful
2018.02.27 18:35:54 LOG7[0]: Service [TEST] started
2018.02.27 18:35:54 LOG7[0]: Option TCP_NODELAY set on local socket
2018.02.27 18:35:54 LOG5[0]: Service [TEST] accepted connection from 127.0.0.1:51199
2018.02.27 18:35:54 LOG6[0]: failover: round-robin, starting at entry #3
2018.02.27 18:35:54 LOG6[0]: s_connect: connecting 104.16.231.14:443
2018.02.27 18:35:54 LOG7[0]: s_connect: s_poll_wait 104.16.231.14:443: waiting 10 seconds
2018.02.27 18:35:54 LOG5[0]: s_connect: connected 104.16.231.14:443
2018.02.27 18:35:54 LOG5[0]: Service [TEST] connected remote server from 192.168.6.2:51200
2018.02.27 18:35:54 LOG7[0]: Option TCP_NODELAY set on remote socket
2018.02.27 18:35:54 LOG7[0]: Remote descriptor (FD=748) initialized
2018.02.27 18:35:54 LOG6[0]: SNI: sending servername: thetvdb.com
2018.02.27 18:35:54 LOG6[0]: Peer certificate not required
2018.02.27 18:35:54 LOG7[0]: TLS state (connect): before/connect initialization
2018.02.27 18:35:54 LOG7[0]: TLS state (connect): SSLv2/v3 write client hello A
2018.02.27 18:35:54 LOG7[0]: TLS state (connect): SSLv3 read server hello A
2018.02.27 18:35:54 LOG6[0]: Certificate verification disabled
2018.02.27 18:35:54 LOG6[0]: Certificate verification disabled
2018.02.27 18:35:54 LOG6[0]: Certificate verification disabled
2018.02.27 18:35:54 LOG7[0]: TLS state (connect): SSLv3 read server certificate A
2018.02.27 18:35:54 LOG7[0]: TLS state (connect): SSLv3 read server key exchange A
2018.02.27 18:35:54 LOG6[0]: Client certificate not requested
2018.02.27 18:35:54 LOG7[0]: TLS state (connect): SSLv3 read server done A
2018.02.27 18:35:54 LOG7[0]: TLS state (connect): SSLv3 write client key exchange A
2018.02.27 18:35:54 LOG7[0]: TLS state (connect): SSLv3 write change cipher spec A
2018.02.27 18:35:54 LOG7[0]: TLS state (connect): SSLv3 write finished A
2018.02.27 18:35:54 LOG7[0]: TLS state (connect): SSLv3 flush data
2018.02.27 18:35:54 LOG7[0]: TLS state (connect): SSLv3 read server session ticket A
2018.02.27 18:35:54 LOG7[0]: TLS state (connect): SSLv3 read finished A
2018.02.27 18:35:54 LOG7[0]: 1 client connect(s) requested
2018.02.27 18:35:54 LOG7[0]: 1 client connect(s) succeeded
2018.02.27 18:35:54 LOG7[0]: 0 client renegotiation(s) requested
2018.02.27 18:35:54 LOG7[0]: 0 session reuse(s)
2018.02.27 18:35:54 LOG6[0]: TLS connected: new session negotiated
2018.02.27 18:35:54 LOG7[0]: Peer certificate was cached (4141 bytes)
2018.02.27 18:35:54 LOG6[0]: Negotiated TLSv1.2 ciphersuite ECDHE-ECDSA-AES128-GCM-SHA256 (128-bit encryption)
2018.02.27 18:35:54 LOG7[0]: Compression: null, expansion: null
2018.02.27 18:35:54 LOG6[0]: Read socket closed (readsocket)
2018.02.27 18:35:54 LOG7[0]: Sending close_notify alert
2018.02.27 18:35:54 LOG7[0]: TLS alert (write): warning: close notify
2018.02.27 18:35:54 LOG6[0]: SSL_shutdown successfully sent close_notify alert
2018.02.27 18:35:54 LOG7[1]: Service [TEST] started
2018.02.27 18:35:54 LOG7[1]: Option TCP_NODELAY set on local socket
2018.02.27 18:35:54 LOG5[1]: Service [TEST] accepted connection from 127.0.0.1:51203
2018.02.27 18:35:54 LOG6[1]: failover: round-robin, starting at entry #4
2018.02.27 18:35:54 LOG6[1]: s_connect: connecting 104.16.227.14:443
2018.02.27 18:35:54 LOG7[1]: s_connect: s_poll_wait 104.16.227.14:443: waiting 10 seconds
2018.02.27 18:35:54 LOG6[0]: TLS socket closed (SSL_read)
2018.02.27 18:35:54 LOG7[0]: Sent socket write shutdown
2018.02.27 18:35:54 LOG5[0]: Connection closed: 271 byte(s) sent to TLS, 15560 byte(s) sent to socket
2018.02.27 18:35:54 LOG7[0]: Remote descriptor (FD=748) closed
2018.02.27 18:35:54 LOG7[0]: Local descriptor (FD=736) closed
2018.02.27 18:35:54 LOG7[0]: Service [TEST] finished (1 left)
2018.02.27 18:35:54 LOG5[1]: s_connect: connected 104.16.227.14:443
2018.02.27 18:35:54 LOG5[1]: Service [TEST] connected remote server from 192.168.6.2:51204
2018.02.27 18:35:54 LOG7[1]: Option TCP_NODELAY set on remote socket
2018.02.27 18:35:54 LOG7[1]: Remote descriptor (FD=780) initialized
2018.02.27 18:35:54 LOG6[1]: SNI: sending servername: thetvdb.com
2018.02.27 18:35:54 LOG6[1]: Peer certificate not required
2018.02.27 18:35:54 LOG7[1]: TLS state (connect): before/connect initialization
2018.02.27 18:35:54 LOG7[1]: TLS state (connect): SSLv3 write client hello A
2018.02.27 18:35:54 LOG7[1]: TLS state (connect): SSLv3 read server hello A
2018.02.27 18:35:54 LOG7[1]: TLS state (connect): SSLv3 read finished A
2018.02.27 18:35:54 LOG7[1]: TLS state (connect): SSLv3 write change cipher spec A
2018.02.27 18:35:54 LOG7[1]: TLS state (connect): SSLv3 write finished A
2018.02.27 18:35:54 LOG7[1]: TLS state (connect): SSLv3 flush data
2018.02.27 18:35:54 LOG7[1]: 2 client connect(s) requested
2018.02.27 18:35:54 LOG7[1]: 2 client connect(s) succeeded
2018.02.27 18:35:54 LOG7[1]: 0 client renegotiation(s) requested
2018.02.27 18:35:54 LOG7[1]: 1 session reuse(s)
2018.02.27 18:35:54 LOG6[1]: TLS connected: previous session reused
2018.02.27 18:35:54 LOG6[1]: Read socket closed (readsocket)
2018.02.27 18:35:54 LOG7[1]: Sending close_notify alert
2018.02.27 18:35:54 LOG7[1]: TLS alert (write): warning: close notify
2018.02.27 18:35:54 LOG6[1]: SSL_shutdown successfully sent close_notify alert
2018.02.27 18:35:54 LOG6[1]: TLS socket closed (SSL_read)
2018.02.27 18:35:54 LOG7[1]: Sent socket write shutdown
2018.02.27 18:35:54 LOG5[1]: Connection closed: 272 byte(s) sent to TLS, 4227 byte(s) sent to socket
2018.02.27 18:35:54 LOG7[1]: Remote descriptor (FD=780) closed
2018.02.27 18:35:54 LOG7[1]: Local descriptor (FD=724) closed
2018.02.27 18:35:54 LOG7[1]: Service [TEST] finished (0 left)
2018.02.27 18:35:54 LOG7[2]: Service [TEST] started
2018.02.27 18:35:54 LOG7[2]: Option TCP_NODELAY set on local socket
2018.02.27 18:35:54 LOG5[2]: Service [TEST] accepted connection from 127.0.0.1:51207
2018.02.27 18:35:54 LOG6[2]: failover: round-robin, starting at entry #0
2018.02.27 18:35:54 LOG6[2]: s_connect: connecting 104.16.230.14:443
2018.02.27 18:35:54 LOG7[2]: s_connect: s_poll_wait 104.16.230.14:443: waiting 10 seconds
2018.02.27 18:35:54 LOG5[2]: s_connect: connected 104.16.230.14:443
2018.02.27 18:35:54 LOG5[2]: Service [TEST] connected remote server from 192.168.6.2:51208
2018.02.27 18:35:54 LOG7[2]: Option TCP_NODELAY set on remote socket
2018.02.27 18:35:54 LOG7[2]: Remote descriptor (FD=796) initialized
2018.02.27 18:35:54 LOG6[2]: SNI: sending servername: thetvdb.com
2018.02.27 18:35:54 LOG6[2]: Peer certificate not required
2018.02.27 18:35:54 LOG7[2]: TLS state (connect): before/connect initialization
2018.02.27 18:35:54 LOG7[2]: TLS state (connect): SSLv3 write client hello A
2018.02.27 18:35:54 LOG7[2]: TLS state (connect): SSLv3 read server hello A
2018.02.27 18:35:54 LOG7[2]: TLS state (connect): SSLv3 read finished A
2018.02.27 18:35:54 LOG7[2]: TLS state (connect): SSLv3 write change cipher spec A
2018.02.27 18:35:54 LOG7[2]: TLS state (connect): SSLv3 write finished A
2018.02.27 18:35:54 LOG7[2]: TLS state (connect): SSLv3 flush data
2018.02.27 18:35:54 LOG7[2]: 3 client connect(s) requested
2018.02.27 18:35:54 LOG7[2]: 3 client connect(s) succeeded
2018.02.27 18:35:54 LOG7[2]: 0 client renegotiation(s) requested
2018.02.27 18:35:54 LOG7[2]: 2 session reuse(s)
2018.02.27 18:35:54 LOG6[2]: TLS connected: previous session reused
2018.02.27 18:35:54 LOG6[2]: Read socket closed (readsocket)
2018.02.27 18:35:54 LOG7[2]: Sending close_notify alert
2018.02.27 18:35:54 LOG7[2]: TLS alert (write): warning: close notify
2018.02.27 18:35:54 LOG6[2]: SSL_shutdown successfully sent close_notify alert
2018.02.27 18:35:54 LOG7[3]: Service [TEST] started
2018.02.27 18:35:54 LOG7[3]: Option TCP_NODELAY set on local socket
2018.02.27 18:35:54 LOG5[3]: Service [TEST] accepted connection from 127.0.0.1:51211
2018.02.27 18:35:54 LOG6[3]: failover: round-robin, starting at entry #1
2018.02.27 18:35:54 LOG6[3]: s_connect: connecting 104.16.228.14:443
2018.02.27 18:35:54 LOG7[3]: s_connect: s_poll_wait 104.16.228.14:443: waiting 10 seconds
2018.02.27 18:35:54 LOG6[2]: TLS socket closed (SSL_read)
2018.02.27 18:35:54 LOG7[2]: Sent socket write shutdown
2018.02.27 18:35:54 LOG5[2]: Connection closed: 254 byte(s) sent to TLS, 311 byte(s) sent to socket
2018.02.27 18:35:54 LOG7[2]: Remote descriptor (FD=796) closed
2018.02.27 18:35:54 LOG7[2]: Local descriptor (FD=744) closed
2018.02.27 18:35:54 LOG7[2]: Service [TEST] finished (1 left)
2018.02.27 18:35:54 LOG5[3]: s_connect: connected 104.16.228.14:443
2018.02.27 18:35:54 LOG5[3]: Service [TEST] connected remote server from 192.168.6.2:51212
2018.02.27 18:35:54 LOG7[3]: Option TCP_NODELAY set on remote socket
2018.02.27 18:35:54 LOG7[3]: Remote descriptor (FD=800) initialized
2018.02.27 18:35:54 LOG6[3]: SNI: sending servername: thetvdb.com
2018.02.27 18:35:54 LOG6[3]: Peer certificate not required
2018.02.27 18:35:54 LOG7[3]: TLS state (connect): before/connect initialization
2018.02.27 18:35:54 LOG7[3]: TLS state (connect): SSLv3 write client hello A
2018.02.27 18:35:54 LOG7[3]: TLS state (connect): SSLv3 read server hello A
2018.02.27 18:35:54 LOG7[3]: TLS state (connect): SSLv3 read finished A
2018.02.27 18:35:54 LOG7[3]: TLS state (connect): SSLv3 write change cipher spec A
2018.02.27 18:35:54 LOG7[3]: TLS state (connect): SSLv3 write finished A
2018.02.27 18:35:54 LOG7[3]: TLS state (connect): SSLv3 flush data
2018.02.27 18:35:54 LOG7[3]: 4 client connect(s) requested
2018.02.27 18:35:54 LOG7[3]: 4 client connect(s) succeeded
2018.02.27 18:35:54 LOG7[3]: 0 client renegotiation(s) requested
2018.02.27 18:35:54 LOG7[3]: 3 session reuse(s)
2018.02.27 18:35:54 LOG6[3]: TLS connected: previous session reused
2018.02.27 18:35:54 LOG6[3]: Read socket closed (readsocket)
2018.02.27 18:35:54 LOG7[3]: Sending close_notify alert
2018.02.27 18:35:54 LOG7[3]: TLS alert (write): warning: close notify
2018.02.27 18:35:54 LOG6[3]: SSL_shutdown successfully sent close_notify alert
2018.02.27 18:35:54 LOG7[4]: Service [TEST] started
2018.02.27 18:35:54 LOG7[4]: Option TCP_NODELAY set on local socket
2018.02.27 18:35:54 LOG5[4]: Service [TEST] accepted connection from 127.0.0.1:51215
2018.02.27 18:35:54 LOG6[4]: failover: round-robin, starting at entry #2
2018.02.27 18:35:54 LOG6[4]: s_connect: connecting 104.16.229.14:443
2018.02.27 18:35:54 LOG7[4]: s_connect: s_poll_wait 104.16.229.14:443: waiting 10 seconds
2018.02.27 18:35:54 LOG6[3]: TLS socket closed (SSL_read)
2018.02.27 18:35:54 LOG7[3]: Sent socket write shutdown
2018.02.27 18:35:54 LOG5[3]: Connection closed: 257 byte(s) sent to TLS, 314 byte(s) sent to socket
2018.02.27 18:35:54 LOG7[3]: Remote descriptor (FD=800) closed
2018.02.27 18:35:54 LOG7[3]: Local descriptor (FD=764) closed
2018.02.27 18:35:54 LOG7[3]: Service [TEST] finished (1 left)
2018.02.27 18:35:54 LOG5[4]: s_connect: connected 104.16.229.14:443
2018.02.27 18:35:54 LOG5[4]: Service [TEST] connected remote server from 192.168.6.2:51216
2018.02.27 18:35:54 LOG7[4]: Option TCP_NODELAY set on remote socket
2018.02.27 18:35:54 LOG7[4]: Remote descriptor (FD=780) initialized
2018.02.27 18:35:54 LOG6[4]: SNI: sending servername: thetvdb.com
2018.02.27 18:35:54 LOG6[4]: Peer certificate not required
2018.02.27 18:35:54 LOG7[4]: TLS state (connect): before/connect initialization
2018.02.27 18:35:54 LOG7[4]: TLS state (connect): SSLv3 write client hello A
2018.02.27 18:35:54 LOG7[4]: TLS state (connect): SSLv3 read server hello A
2018.02.27 18:35:54 LOG7[4]: TLS state (connect): SSLv3 read finished A
2018.02.27 18:35:54 LOG7[4]: TLS state (connect): SSLv3 write change cipher spec A
2018.02.27 18:35:54 LOG7[4]: TLS state (connect): SSLv3 write finished A
2018.02.27 18:35:54 LOG7[4]: TLS state (connect): SSLv3 flush data
2018.02.27 18:35:54 LOG7[4]: 5 client connect(s) requested
2018.02.27 18:35:54 LOG7[4]: 5 client connect(s) succeeded
2018.02.27 18:35:54 LOG7[4]: 0 client renegotiation(s) requested
2018.02.27 18:35:54 LOG7[4]: 4 session reuse(s)
2018.02.27 18:35:54 LOG6[4]: TLS connected: previous session reused
2018.02.27 18:35:54 LOG6[4]: Read socket closed (readsocket)
2018.02.27 18:35:54 LOG7[4]: Sending close_notify alert
2018.02.27 18:35:54 LOG7[4]: TLS alert (write): warning: close notify
2018.02.27 18:35:54 LOG6[4]: SSL_shutdown successfully sent close_notify alert
2018.02.27 18:35:54 LOG7[5]: Service [TEST] started
2018.02.27 18:35:54 LOG7[5]: Option TCP_NODELAY set on local socket
2018.02.27 18:35:54 LOG5[5]: Service [TEST] accepted connection from 127.0.0.1:51219
2018.02.27 18:35:54 LOG6[5]: failover: round-robin, starting at entry #3
2018.02.27 18:35:54 LOG6[5]: s_connect: connecting 104.16.231.14:443
2018.02.27 18:35:54 LOG7[5]: s_connect: s_poll_wait 104.16.231.14:443: waiting 10 seconds
2018.02.27 18:35:54 LOG6[4]: TLS socket closed (SSL_read)
2018.02.27 18:35:54 LOG7[4]: Sent socket write shutdown
2018.02.27 18:35:54 LOG5[4]: Connection closed: 257 byte(s) sent to TLS, 314 byte(s) sent to socket
2018.02.27 18:35:54 LOG7[4]: Remote descriptor (FD=780) closed
2018.02.27 18:35:54 LOG7[4]: Local descriptor (FD=768) closed
2018.02.27 18:35:54 LOG7[4]: Service [TEST] finished (1 left)
2018.02.27 18:35:54 LOG5[5]: s_connect: connected 104.16.231.14:443
2018.02.27 18:35:54 LOG5[5]: Service [TEST] connected remote server from 192.168.6.2:51220
2018.02.27 18:35:54 LOG7[5]: Option TCP_NODELAY set on remote socket
2018.02.27 18:35:54 LOG7[5]: Remote descriptor (FD=824) initialized
2018.02.27 18:35:54 LOG6[5]: SNI: sending servername: thetvdb.com
2018.02.27 18:35:54 LOG6[5]: Peer certificate not required
2018.02.27 18:35:54 LOG7[5]: TLS state (connect): before/connect initialization
2018.02.27 18:35:54 LOG7[5]: TLS state (connect): SSLv3 write client hello A
2018.02.27 18:35:54 LOG7[5]: TLS state (connect): SSLv3 read server hello A
2018.02.27 18:35:54 LOG7[5]: TLS state (connect): SSLv3 read finished A
2018.02.27 18:35:54 LOG7[5]: TLS state (connect): SSLv3 write change cipher spec A
2018.02.27 18:35:54 LOG7[5]: TLS state (connect): SSLv3 write finished A
2018.02.27 18:35:54 LOG7[5]: TLS state (connect): SSLv3 flush data
2018.02.27 18:35:54 LOG7[5]: 6 client connect(s) requested
2018.02.27 18:35:54 LOG7[5]: 6 client connect(s) succeeded
2018.02.27 18:35:54 LOG7[5]: 0 client renegotiation(s) requested
2018.02.27 18:35:54 LOG7[5]: 5 session reuse(s)
2018.02.27 18:35:54 LOG6[5]: TLS connected: previous session reused
2018.02.27 18:35:55 LOG6[5]: Read socket closed (readsocket)
2018.02.27 18:35:55 LOG7[5]: Sending close_notify alert
2018.02.27 18:35:55 LOG7[5]: TLS alert (write): warning: close notify
2018.02.27 18:35:55 LOG6[5]: SSL_shutdown successfully sent close_notify alert
2018.02.27 18:35:55 LOG6[5]: TLS socket closed (SSL_read)
2018.02.27 18:35:55 LOG7[5]: Sent socket write shutdown
2018.02.27 18:35:55 LOG5[5]: Connection closed: 256 byte(s) sent to TLS, 313 byte(s) sent to socket
2018.02.27 18:35:55 LOG7[5]: Remote descriptor (FD=824) closed
2018.02.27 18:35:55 LOG7[5]: Local descriptor (FD=804) closed
2018.02.27 18:35:55 LOG7[5]: Service [TEST] finished (0 left)

[Jasch]

Event. mag sich das ja mal jemand anschauen.

http://www17.zippyshare.com/v/diOGmFHH/file.html
Passwort:muhkuh
Zip entpacken mit Folder (aufC: oder Pfade im Tool anpassen). C:\Test

MySeries Manager starten

1. Get Files
2. Download selected(log download failed für Bilder)

MfG Alex

[qiller]

und mit Proxycap das Programm dazu bewegt den Proxy zu nutzen.


probier mal per DNS-Umleitung (z.B. hosts-Datei) auf localhost. Oder benutzt das Programm keine DNS-Abfragen und greift direkt auf die IP zu?

[littlejam]

Da würde sich der haproxy anbieten


https://www.digitalocean.com/community/tutorials/how-to-implement-ssl-termination-with-haproxy-on-ubuntu-14-04

Oder Pound

http://www.ubuntugeek.com/load-balancing-httphttps-with-pound-on-ubuntu-14-04-server.html
Ja, klar geht das. Nennt sich dann reverse proxy mit SSL/TLS termination. nginx eignet sich dafuer etwa.
Ist das nicht für den umgekehrten Fall?
Also ein Client spricht den Service per https an und das Backend verarbeitet http.

Denke Stunnel ist hier das richtige Tool.
Oder vielleicht Squid.

Grüße

[Jasch]

probier mal per DNS-Umleitung (z.B. hosts-Datei) auf localhost. Oder benutzt das Programm keine DNS-Abfragen und greift direkt auf die IP zu?

Gute Idee werde ich mal testen.