[prosody-dev] proposed auth module: atack (+ logging issues)

[James Leu]

Hello all,

First time poster ... long time user

I've started working on a auth module that allows you to stack other auth 
modules.

I believe I've made good progress, but I'm trying to do some debugging and all 
my module:log messages are disappearing.

I can see my log messages from when the module is being loaded, but I cannot 
see log messages from any of the auth related
methods.

Is there something that blocks logging from the auth context?

What info should I post to help others help me?

Thank you for your time,
James

-- 
You received this message because you are subscribed to the Google Groups 
"prosody-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prosody-dev+unsubscr...@googlegroups.com.
To post to this group, send email to prosody-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/prosody-dev.
For more options, visit https://groups.google.com/d/optout.

Re: [prosody-dev] [PATCH][0.10] muc: Allow clients to change multiple affiliations or roles at once (#345)

[Lennart Sauerbeck]

On 17.04.2017 22:21, Matthew Wild wrote:
> On 17 April 2017 at 19:34, Kim Alvefur  wrote:
>> On Mon, Apr 17, 2017 at 02:32:22PM +0100, Matthew Wild wrote:
>>>   - Treat the request as an atomic change: succeed for all, or fail
>>> all (i.e. if one of the JIDs is malformed, don't allow any of the
>>> other changes in the request to take place). This would require work
>>> to either pre-verify the changes (which we don't have code for) or to
>>> roll back changes that were already made (which is a bit hacky, we'd
>>> already have sent out notifications, unless we added a new 'batch
>>> update' version of :set_affiliation()).
>>
>> I would prefer this. Possibly by collecting the changed state in a new
>> table, then overwriting the old affiliations table as a commit.
> 
> I'd prefer it too, but it's not trivial.
> 
> [...]
> 
> Does this make sense?

Yes, it does and I think I understand what you want to achieve.

I'll give it a try this weekend and if I run into problems I'll send a
patch with some pseudo-code to the list to avoid running in the wrong
direction for too long.

Best Regards
Lennart

-- 
You received this message because you are subscribed to the Google Groups 
"prosody-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prosody-dev+unsubscr...@googlegroups.com.
To post to this group, send email to prosody-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/prosody-dev.
For more options, visit https://groups.google.com/d/optout.

[prosody-dev] proposed new auth module:stack

[James Leu]

I was wondering if there is any interest in an auth modules that stacks 
existing auth modules.

Example:
stack = "a b c"

while there are entries on stack
Z = top of stack
If the users exists in Z AND passes authentication, they are authorize
else if the users exists in Z but does NOT pass authentication they are 
denied
if the user does not exist in Z then Z is removed from the stack

Use case

I have a prosody instance that has some 'privileged' JIDs but I want to 
allow anonymous access to everyone else.
I do not want anyone to be able login with a 'privileged' JID.

my stack is

internal_hashed
any

I have 'created' entries for the 'privileged' JIDs

I have created such a module and will post it here if there is interest.

-- 
You received this message because you are subscribed to the Google Groups 
"prosody-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to prosody-dev+unsubscr...@googlegroups.com.
To post to this group, send email to prosody-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/prosody-dev.
For more options, visit https://groups.google.com/d/optout.