Ich kann leider keine verschlüsselte Verbindung mehr aufbauen. Gestern Abend ging es komischerweise noch und ich habe nichts geändert.
Meine Config:
Code:
admins = { "[Only registered and activated users can see links. Click Here To Register...]" }
plugin_paths = { "/usr/lib/prosody/modules/prosody-modules" }
modules_enabled = {
-- Generally required
"roster"; -- Allow users to have a roster. Recommended
"saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.
"tls"; -- Add support for secure TLS on c2s/s2s connections
"dialback"; -- s2s dialback support
"disco"; -- Service discovery
"posix"; -- POSIX functionality, sends server to background, enables syslog, etc.
-- Not essential, but recommended
"private"; -- Private XML storage (for room bookmarks, etc.)
"vcard"; -- Allow users to set vCards
-- These are commented by default as they have a performance impact
--"privacy"; -- Support privacy lists
--"compression"; -- Stream compression (requires the lua-zlib package installed)
-- Nice to have
--"version"; -- Replies to server version requests
"uptime"; -- Report how long server has been running
"time"; -- Let others know the time here on this server
"ping"; -- Replies to XMPP pings with pongs
"pep"; -- Enables users to publish their mood, activity, playing music and more
"register"; -- Allow users to register on this server using a client and change passwords
-- Admin interfaces
"admin_adhoc"; -- Allows administration via an XMPP client that supports ad-hoc commands
--"admin_telnet"; -- Opens telnet console interface on localhost port 5582
-- HTTP modules
--"bosh"; -- Enable BOSH clients, aka "Jabber over HTTP"
--"http_files"; -- Serve static files from a directory over HTTP
-- Other specific functionality
--"groups"; -- Shared roster support
--"announce"; -- Send announcement to all online users
--"welcome"; -- Welcome users who register accounts
--"watchregistrations"; -- Alert admins of registrations
"motd"; -- Send a message to users when they log in
"legacyauth"; -- Legacy authentication. Only used by some old clients and bots.
"require_otr";
"strict_https";
};
hsts_header = "max-age=31556952"
daemonize = true;
pidfile = "/var/run/prosody/prosody.pid";
c2s_require_encryption = true;
legacy_ssl_ports = { 5223 }
motd_text = [[Text!
Text.]]
allow_registration = false;
ssl = {
key = "/etc/prosody/certs/keyfile.key";
certificate = "/etc/prosody/certs/certfile.crt";
}
tls_policy = "FS" -- allow only ciphers that enable forward secrecy
tls_policy = {
c2s = {
encryption = "AES"; -- Require AES (or AESGCM) encryption
protocol = "TLSv1.2"; -- and TLSv1.2
bits = 128; -- and at least 128 bits (FIXME: remember what this meant)
};
s2s = {
cipher = "AESGCM"; -- Require AESGCM ciphers
protocol = "TLSv1.[12]"; -- and TLSv1.1 or 1.2
authentication = "RSA"; -- with RSA authentication
};
}
c2s_require_encryption = true
s2s_require_encryption = true
s2s_secure_auth = true
s2s_insecure_domains = { "gmail.com" }
pidfile = "/var/run/prosody/prosody.pid"
authentication = "internal_hashed"
log = {
info = "/var/log/prosody/prosody.log"; -- Change 'info' to 'debug' for verbose logging
error = "/var/log/prosody/prosody.err";
"*syslog";
}
VirtualHost "domain.com"
-- Assign this host a certificate for TLS, otherwise it would use the one
-- set in the global section (if any).
-- Note that old-style SSL on port 5223 only supports one certificate, and will always
-- use the global one.
ssl = {
key = "/etc/prosody/certs/keyfile.key";
certificate = "/etc/prosody/certs/certfile.crt";
options = { "no_sslv2", "no_sslv3", "no_ticket", "no_compression", "cipher_server_preference", "single_dh_use", "single_ecdh_use" };
ciphers = "HIGH+kEDH:HIGH+kEECDH:HIGH:!CAMELLIA:!PSK:!SRP:!3DES:!aNULL";
dhparam = "/etc/prosody/certs/dh-2048.pem";
}
Hab's ohne und mit Legacyauth und Legacy SSL Port probiert.
Auszug prosody.log:
Code:
Dec 04 14:26:50 *string* info Client connected
Dec 04 14:26:51 *string* info Authenticated as [Only registered and activated users can see links. Click Here To Register...]
Dec 04 14:30:19 *string* info Client connected
Dec 04 14:30:20 *string* info Authenticated as [Only registered and activated users can see links. Click Here To Register...]
Dec 04 14:30:20 *string* info c2s stream for [Only registered and activated users can see links. Click Here To Register...]/androidnkT29bWk closed: Replaced by new connection
Dec 04 14:30:20 *string* info Client disconnected: connection closed
Dec 04 14:42:10 *string* info Client disconnected: closed
Dec 04 14:43:45 *string* info Client disconnected: closed
Dec 04 14:43:45 *string* info Client disconnected: closed
Dec 04 14:43:46 *string* info Client connected
Dec 04 14:53:06 *string* info Client connected
Dec 04 14:53:23 *string* info Authenticated as [Only registered and activated users can see links. Click Here To Register...]
Dec 04 14:53:24 *string* info Client disconnected: closed
Dec 04 14:53:24 *string* info Client connected
Dec 04 14:53:26 *string* info Authenticated as [Only registered and activated users can see links. Click Here To Register...]
Dec 04 15:13:57 *string* info Client disconnected: ssl handshake failed
Teilweise steht auch da "Client connected" und in der selben Sekunde "Client disconnected".
Wenn ich in ChatSecure die verschlüsselte Verbindung aktivieren will, lädt der Balken einfach nur unendlich lange und nichts passiert. Und unverschlüsselt kann ich es ja eh nicht nutzen.
Edit:
// Freundschaftsanfragen kommen an
Noch mal dem Verständnis halber: Müssen beide Clients online sein, um verschlüsselt zu schreiben (auch wenn man vorher schon mal verschlüsselt geschrieben hat)? Also muss die Verschlüsselung praktisch immer neu aufgebaut werden?