Expropriator
Green Team
Доброго времени суток, коллеги!
Установил debian - server на virtualbox, и установил туда ХМРР сервер Prosody, для конфиденциального общения. В качестве прокси использую Socks5 i2pd, трафик кручу через i2p, используя виртуальный сервис i2pd.
Вот мануал, по которому произвожу настройку:
Ссылка скрыта от гостей
Много раз разворачивал этот проект на Kali, Whonix и Windows, все прекрасно работало, но в этот раз никак не мог достучаться Пиджином до сервера, посмотрев логи, я понял что нелады на самом сервере Prosody.
Вот конфиг сервера /etc/prosody/prosody.cfg.lua
-- Prosody Example Configuration File
--
-- Information on configuring Prosody can be found on our
-- website atСсылка скрыта от гостей
--
-- Tip: You can check that the syntax of this file is correct
-- when you have finished by running this command:
-- prosodyctl check config
-- If there are any errors, it will let you know what and where
-- they are, otherwise it will keep quiet.
--
-- The only thing left to do is rename this file to remove the .dist ending, and fill in the
-- blanks. Good luck, and happy Jabbering!
---------- Server-wide settings ----------
-- Settings in this section apply to the whole server and are the default settings
-- for any virtual hosts
-- This is a (by default, empty) list of accounts that are admins
-- for the server. Note that you must create the accounts separately
-- (seeСсылка скрыта от гостейfor info)
-- Example: admins = { "user1@example.com", "user2@example.net" }
admins = {"admin@krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p" }
-- Enable use of libevent for better performance under high load
-- For more information see:Ссылка скрыта от гостей
--use_libevent = true
-- Prosody will always look in its source directory for modules, but
-- this option allows you to specify additional locations where Prosody
-- will look for modules first. For community modules, seeСсылка скрыта от гостей
-- For a local administrator it's common to place local modifications
-- under /usr/local/ hierarchy:
plugin_paths = { "/usr/local/lib/prosody/modules" }
-- This is the list of modules Prosody will load on startup.
-- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
-- Documentation for bundled modules can be found at:Ссылка скрыта от гостей
modules_enabled = {
"roster"; "saslauth"; "tls"; "dialback"; "disco"; "posix"; "private"; "vcard"; "ping"; "register"; "admin_adhoc"; "darknet";
};
-- These modules are auto-loaded, but should you want
-- to disable them then uncomment them here:
modules_disabled = {};
-- Disable account creation by default, for security
-- For more information seeСсылка скрыта от гостей
allow_registration = false
-- Debian:
-- Do not send the server to background, either systemd or start-stop-daemon take care of that.
--
daemonize = false;
-- Debian:
-- Please, don't change this option since /run/prosody/
-- is one of the few directories Prosody is allowed to write to
--
pidfile = "/run/prosody/prosody.pid";
-- Force clients to use encrypted connections? This option will
-- prevent clients from authenticating unless they are using encryption.
c2s_require_encryption = true
-- Force servers to use encrypted connections? This option will
-- prevent servers from authenticating unless they are using encryption.
s2s_require_encryption = true
-- Force certificate authentication for server-to-server connections?
s2s_secure_auth = false
-- Some servers have invalid or self-signed certificates. You can list
-- remote domains here that will not be required to authenticate using
-- certificates. They will be authenticated using DNS instead, even
-- when s2s_secure_auth is enabled.
--s2s_insecure_domains = { "insecure.example" }
-- Even if you disable s2s_secure_auth, you can still require valid
-- certificates for some domains by specifying a list here.
--s2s_secure_domains = { "jabber.org" }
-- Select the authentication backend to use. The 'internal' providers
-- use Prosody's configured data storage to store the authentication data.
authentication = "internal_hashed"
-- Select the storage backend to use. By default Prosody uses flat files
-- in its configured data directory, but it also supports more backends
-- through modules. An "sql" backend is included by default, but requires
-- additional dependencies. SeeСсылка скрыта от гостейfor more info.
--storage = "sql" -- Default is "internal" (Debian: "sql" requires one of the
-- lua-dbi-sqlite3, lua-dbi-mysql or lua-dbi-postgresql packages to work)
-- For the "sql" backend, you can uncomment *one* of the below to configure:
--sql = { driver = "SQLite3", database = "prosody.sqlite" } -- Default. 'database' is the filename.
--sql = { driver = "MySQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
--sql = { driver = "PostgreSQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
-- Archiving configuration
-- If mod_mam is enabled, Prosody will store a copy of every message. This
-- is used to synchronize conversations between multiple clients, even if
-- they are offline. This setting controls how long Prosody will keep
-- messages in the archive before removing them.
archive_expires_after = "1w" -- Remove archived messages after 1 week
-- You can also configure messages to be stored in-memory only. For more
-- archiving options, seeСсылка скрыта от гостей
-- Logging configuration
-- For advanced logging seeСсылка скрыта от гостей
--
-- Debian:
-- Logs info and higher to /var/log
-- Logs errors to syslog also
log = {
-- Log files (change 'info' to 'debug' for debug logs):
info = "/var/log/prosody/prosody.log";
error = "/var/log/prosody/prosody.err";
-- Syslog:
{ levels = { "error" }; to = "syslog"; };
}
-- Uncomment to enable statistics
-- For more info seeСсылка скрыта от гостей
-- statistics = "internal"
-- Certificates
-- Every virtual host and component needs a certificate so that clients and
-- servers can securely verify its identity. Prosody will automatically load
-- certificates/keys from the directory specified here.
-- For more information, including how to use 'prosodyctl' to auto-import certificates
-- (from e.g. Let's Encrypt) seeСсылка скрыта от гостей
-- Location of directory to find certificates in (relative to main config file):
certificates = "certs"
-- HTTPS currently only supports a single certificate, specify it here:
--https_certificate = "/etc/prosody/certs/localhost.crt"
----------- Virtual hosts -----------
-- You need to add a VirtualHost entry for each domain you wish Prosody to serve.
-- Settings under each VirtualHost entry apply *only* to that host.
-- It's customary to maintain VirtualHost entries in separate config files
-- under /etc/prosody/conf.d/ directory. Examples of such config files can
-- be found in /etc/prosody/conf.avail/ directory.
------ Additional config files ------
-- For organizational purposes you may prefer to add VirtualHost and
-- Component definitions in their own config files. This line includes
-- all config files in /etc/prosody/conf.d/
VirtualHost "krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p"
enabled = true
ssl = {
key = "/etc/prosody/certs/krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p.key";
certificate = "/etc/prosody/certs/krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p.crt";
}
--VirtualHost "example.com"
-- certificate = "/path/to/example.crt"
------ Components ------
-- You can specify components to add hosts that provide special services,
-- like multi-user conferences, and transports.
-- For more information on components, seeСсылка скрыта от гостей
---Set up a MUC (multi-user chat) room server on conference.example.com:
--Component "conference.example.com" "muc"
--- Store MUC messages in an archive and allow users to access it
--modules_enabled = { "muc_mam" }
---Set up an external component (default component port is 5347)
--
-- External components allow adding various services, such as gateways/
-- transports to other networks like ICQ, MSN and Yahoo. For more info
-- see:Ссылка скрыта от гостей
--
--Component "gateway.example.com"
-- component_secret = "password"
Include "conf.d/*.cfg.lua"
Вот лог сервера cat /var/log/prosody/prosody.log
Apr 19 11:01:47 startup info Hello and welcome to Prosody version 0.11.2
Apr 19 11:01:47 startup info Prosody is using the select backend for connection handling
Apr 19 11:01:47 portmanager info Activated service 's2s' on [::]:5269, [*]:5269
Apr 19 11:01:47 portmanager info Activated service 'c2s' on [::]:5222, [*]:5222
Apr 19 11:01:47 portmanager info Activated service 'legacy_ssl' on no ports
Apr 19 11:04:03 mod_posix warn Received SIGTERM
Apr 19 11:04:03 startup info Shutting down: Received SIGTERM
Apr 19 11:04:03 general info Shutting down...
Apr 19 11:04:03 general info Shutdown status: Cleaning up
Apr 19 11:04:03 general info Shutdown complete
Apr 19 11:04:03 startup info Hello and welcome to Prosody version 0.11.2
Apr 19 11:04:03 startup info Prosody is using the select backend for connection handling
Apr 19 11:04:03 modulemanager error Unable to load module 'darknet': /usr/lib/prosody/modules/mod_darknet.lua: No such file or directory
Apr 19 11:04:03 certmanager error SSL/TLS: Failed to load '/etc/prosody/certs/krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p.key': Check that the path is correct, and the file exists. (for krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p)
Apr 19 11:04:03 krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p:tls error Error creating context for c2s: error loading private key (No such file or directory)
Apr 19 11:04:03 certmanager error SSL/TLS: Failed to load '/etc/prosody/certs/krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p.key': Previous error (see logs), or other system error. (for krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p)
Apr 19 11:04:03 krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p:tls error Error creating contexts for s2sout: error loading private key (system lib)
Apr 19 11:04:03 certmanager error SSL/TLS: Failed to load '/etc/prosody/certs/krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p.key': Previous error (see logs), or other system error. (for krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p)
Apr 19 11:04:03 krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p:tls error Error creating contexts for s2sin: error loading private key (system lib)
Apr 19 11:04:03 portmanager info Activated service 's2s' on [*]:5269, [::]:5269
Apr 19 11:04:03 portmanager info Activated service 'c2s' on [*]:5222, [::]:5222
Apr 19 11:04:03 portmanager info Activated service 'legacy_ssl' on no ports
Apr 19 11:04:03 modulemanager error Unable to load module 'darknet': /usr/lib/prosody/modules/mod_darknet.lua: No such file or directory
Apr 19 11:08:22 mod_posix warn Received SIGTERM
Apr 19 11:08:22 startup info Shutting down: Received SIGTERM
Apr 19 11:08:22 general info Shutting down...
Apr 19 11:08:22 general info Shutdown status: Cleaning up
Apr 19 11:08:22 general info Shutdown complete
Apr 19 11:08:22 startup info Hello and welcome to Prosody version 0.11.2
Apr 19 11:08:22 startup info Prosody is using the select backend for connection handling
Apr 19 11:08:22 portmanager info Activated service 'c2s' on [*]:5222, [::]:5222
Apr 19 11:08:22 portmanager info Activated service 'legacy_ssl' on no ports
Apr 19 11:08:22 portmanager info Activated service 's2s' on [*]:5269, [::]:5269
Apr 19 11:10:20 mod_posix warn Received SIGTERM
Apr 19 11:10:20 startup info Shutting down: Received SIGTERM
Apr 19 11:10:20 general info Shutting down...
Apr 19 11:10:20 general info Shutdown status: Cleaning up
Apr 19 11:10:20 general info Shutdown complete
Apr 19 11:10:20 startup info Hello and welcome to Prosody version 0.11.2
Apr 19 11:10:20 startup info Prosody is using the select backend for connection handling
Apr 19 11:10:20 portmanager info Activated service 'c2s' on [::]:5222, [*]:5222
Apr 19 11:10:20 portmanager info Activated service 'legacy_ssl' on no ports
Apr 19 11:10:20 portmanager info Activated service 's2s' on [::]:5269, [*]:5269
Вот лог по ошибкам cat /var/log/prosody/prosody.err
Apr 19 11:04:03 modulemanager error Unable to load module 'darknet': /usr/lib/prosody/modules/mod_darknet.lua: No such file or directory
Apr 19 11:04:03 certmanager error SSL/TLS: Failed to load '/etc/prosody/certs/krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p.key': Check that the path is correct, and the file exists. (for krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p)
Apr 19 11:04:03 krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p:tls error Error creating context for c2s: error loading private key (No such file or directory)
Apr 19 11:04:03 certmanager error SSL/TLS: Failed to load '/etc/prosody/certs/krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p.key': Previous error (see logs), or other system error. (for krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p)
Apr 19 11:04:03 krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p:tls error Error creating contexts for s2sout: error loading private key (system lib)
Apr 19 11:04:03 certmanager error SSL/TLS: Failed to load '/etc/prosody/certs/krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p.key': Previous error (see logs), or other system error. (for krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p)
Apr 19 11:04:03 krswzn3gt32blf54uam5l3otiilmu3te46333i7vy5hqwtkl4hvq.b32.i2p:tls error Error creating contexts for s2sin: error loading private key (system lib)
Apr 19 11:04:03 modulemanager error Unable to load module 'darknet': /usr/lib/prosody/modules/mod_darknet.lua: No such file or directory
ПОЖАЛУЙСТА ПОМОГИТЕ ПОНЯТЬ, В ЧЕМ ИМЕННО ДЕЛО! Спасибо заранее!
Ссылка скрыта от гостей
