Displaying 20 results from an estimated 700 matches similar to: "how to enable PowerDNS/Weakforced with Fedora and sendmail"
2019 Mar 06
2
how to enable PowerDNS/Weakforced with Fedora and sendmail
I took suggestions from https://forge.puppet.com/fraenki/wforce to set
these in /etc/dovecot/conf.d/95-auth.conf
auth_policy_server_url = http://localhost:8084/
auth_policy_hash_nonce = our_password
auth_policy_server_api_header = "Authorization: Basic
hash_from_running_echo-n_base64"
auth_policy_server_timeout_msecs = 2000
auth_policy_hash_mech = sha256
auth_policy_request_attributes =
2019 Mar 07
2
how to enable PowerDNS/Weakforced with Fedora and sendmail
So for auth_policy_server_api_header. is the value of our_password come from the hashed response or the plain-text password? What else am I doing wrong?
Mar 7 09:20:53 olddsm wforce[17763]: WforceWebserver: HTTP Request "/" from 127.0.0.1:56416: Web Authentication failed
curl -X POST -H "Content-Type: application/json" --data '{"login?:?ouruser?, "remote":
2017 Aug 02
4
Auth Policy Server/wforce/weakforced
Is there explicit documentation available for the (probably trivial)
configuration needed for Dovecot and Wforce? I'm probably missing
something that should be perfectly obvious...
Wforce appears to start without errors. I added a file to dovecot's conf.d:
95-policy.conf:
auth_policy_server_url = http://localhost:8084/
auth_policy_hash_nonce = this_is_my_super_secret_something
2019 Jan 16
2
Dovecot + Weakforced Policy server
Hi Aki,
I've configured in this way:
vm-weakforced:~# printf 'wforce:super' | base64
d2ZvcmNlOnN1cGVy
vm-weakforced:~# cat /etc/dovecot/conf.d/95-policy.conf
auth_policy_server_url = http://localhost:8084/
auth_policy_hash_nonce = some random string
auth_policy_server_api_header = "Authorization: Basic d2ZvcmNlOnN1cGVy
With the same result...
> WforceWebserver: HTTP
2019 Mar 07
0
how to enable PowerDNS/Weakforced with Fedora and sendmail
In weakforced you have
webserver("0.0.0.0:8084", "THIS-IS-THE-PASSWORD-FOR-WFORCE")
Thus, you make the base64 blob as
~$ echo -n wforce:THIS-IS-THE-PASSWORD-FOR-WFORCE | base64
d2ZvcmNlOlRISVMtSVMtVEhFLVBBU1NXT1JELUZPUi1XRk9SQ0U=
And in dovecot you put
auth_policy_server_api_header = Authorization Basic d2ZvcmNlOlRISVMtSVMtVEhFLVBBU1NXT1JELUZPUi1XRk9SQ0U
Aki
> On 7
2019 Jan 16
2
Dovecot + Weakforced Policy server
Hi,
I'm trying to set Weakforced with Dovecot and I cannot log in policy
server. This is the config:
/root/weakforced/wforce/wforce.conf
-----------------------------------
...
webserver("0.0.0.0:8084", "super")
...
/etc/dovecot/conf.d/95-policy.conf
----------------------------------
auth_policy_server_url = http://localhost:8084/
#auth_policy_hash_nonce = wforce:super
2019 Mar 07
0
how to enable PowerDNS/Weakforced with Fedora and sendmail
wforce is the username always.
auth_policy_hash_nonce should be set to a pseudorandom value that is
shared by your server(s). Weakforced does not need it for anything.
auth_policy_server_api_header should be set to Authorization: Basic
<echo -n wforce:our_password | base64>
without the < >.
Aki
On 6.3.2019 20.42, Robert Kudyba via dovecot wrote:
> I took suggestions
2019 Mar 06
0
how to enable PowerDNS/Weakforced with Fedora and sendmail
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 6 March 2019 18:25 Robert Kudyba via dovecot <dovecot@dovecot.org> wrote:
</div>
<div>
<br>
</div>
<div>
<br>
2019 Apr 11
5
Mail account brute force / harassment
On 11/04/2019 11:43, Marc Roos via dovecot wrote:
> A. With the fail2ban solution
> - you 'solve' that the current ip is not able to access you
It is only a solution if there are subsequent attempts from the same
address. I currently have several thousand addresses blocked due to
dovecot login failures. My firewall is set to log these so I can see
that few repeat, those
2019 May 13
2
dovecot 2.2.36 and wforce
Hi list
I'm trying to setup dovecot 2.2.36 on a Centos6 to communicate with a
wforce daemon on the remote side. wforce is latest released from git
repo. Daemon part is working and I can successfully send queries from
remote systems to wforce via curl
For dovecot I configured in /etc/dovecot/conf.d/95-wforce.conf
> auth_policy_server_url = http://REMOTE_IP:8084/
>
2019 May 22
2
weakforced: Possible to access the ip address of report/allow?
Hi
I wonder if the information about the origin of report or allow can be
accessed somehow. lt.remote gives the IP of the client trying to login
but is there anything in lt which gives the ip of the system that
connects to wforced?
Thanks and have a good one
--
tobi
2019 May 14
2
weakforced and GeoIP lookups
Hi Tobi,
This looks like you haven?t included the libmaxmind libraries before running configure. GeoIP support is only compiled in if it finds the right libs.
This would be libmaxminddb-dev on Ubuntu for example.
Neil
>> Hi list
>>
>> hope it's okay to ask weakforced questions here as well, but I could not
>> find a dedicated mailinglist for wforce.
>>
2019 May 22
1
weakforced: Possible to access the ip address of report/allow?
Hi Neil
thanks for the hint with the dovecot config, adding this and I can see that
> ... attrs={local_ip="XX.XX.XX.XX"} ...
is now logged by wforce daemon. Then I tried to access that value from
wforce with the following testcode
> if (#lt.attrs > 0)
> then
> return 7, "ip_local", "ip_local", { test=test }
> end
but even if attrs are set
2019 Mar 28
2
configuring Dovecot with wforced and auth_policy_server_url with https results in assertion failed
dovecot-2.3.3-1.fc29.x86_64
Mar 28 10:04:47 auth: Panic: file http-client-request.c: line 283 (http_client_request_unref): assertion failed: (req->refcount > 0)
Mar 28 10:04:47 auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xe34fb) [0x7fe76e0834fb] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe3597) [0x7fe76e083597] -> /usr/lib64/dovecot/libdovecot.so.0(+0x51207)
2019 Sep 13
4
fts_solr: Error: fts_solr: received invalid uid '0'
Hi,
we are trying to add full text search functionality with Solr to our Doveoct setup. Our Versions:
OS: Debian 9
Tried versions:
- Dovecot 2.2.7 with Solr 3.6
- Dovecot 2.3.4 with Solr 8.2
(2.2.7 from offical Debian repository, 2.3.4 from backports)
Search is working mostly of the time perfrectly smooth. But sometimes following message appears in mail.err:
dovecot:
2019 May 14
2
weakforced and GeoIP lookups
Hi Tobi,
it should just work, but depends on the OS version.
./configure ?help tells you all the configure options, including:
--with-maxminddb-includedir
path to maxminddb include directory [default=auto]
--with-maxminddb-libdir path to maxminddb library directory [default=auto]
Neil
> On 14 May 2019, at 17:44, Tobi via dovecot <dovecot at dovecot.org>
2019 Apr 12
2
Mail account brute force / harassment
>
> Probably there's an existing solution for both problems (subsequent
> attempts and dnsbl):
>
> >
>
2017 Sep 27
2
Conditionally disabling auth policy
On Wed, Sep 27, 2017 at 10:03 AM, Marcus Rueckert <darix at opensu.se> wrote:
> On 2017-09-27 16:57:44 +0000, Mark Moseley wrote:
> > I've been digging into the auth policy stuff with weakforced lately.
> There
> > are cases (IP ranges, so could be wrapped up in remote {} blocks) where
> > it'd be nice to skip the auth policy (internal hosts that I can trust,
2017 Sep 28
2
Conditionally disabling auth policy
On Wed, Sep 27, 2017 at 10:06 PM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
>
>
> On 27.09.2017 20:14, Mark Moseley wrote:
> > On Wed, Sep 27, 2017 at 10:03 AM, Marcus Rueckert <darix at opensu.se>
> wrote:
> >
> >> On 2017-09-27 16:57:44 +0000, Mark Moseley wrote:
> >>> I've been digging into the auth policy stuff with weakforced
2017 Sep 27
2
Conditionally disabling auth policy
I've been digging into the auth policy stuff with weakforced lately. There
are cases (IP ranges, so could be wrapped up in remote {} blocks) where
it'd be nice to skip the auth policy (internal hosts that I can trust, but
that are hitting the same servers as the outside world).
Is there any way to disable auth policy, possibly inside a remote{}?
auth_policy_server_url complains that it