fix NC16 compatibility

[Bubu]

Caveat: I've no idea if that is the right fix. All I can say is that I'm running this in production for a few weeks now and no-one complained that passman isn't working yet.

[newhinton]

@Bubu

this is great! However, i cannot create a "proper" release, with an update for nextcloud

But: i will test this, and merge it if it is working as intended

If i have not done so by sunday evening, feel free to push ;)

[e-alfred]

this is great! However, i cannot create a "proper" release, with an update for nextcloud

Can you publish a new release at least on the Github releases page so there is at least an updated package available?

[animalillo]

I'm not sure which kind of side effects could this have on the app, but i guess we need to get the app working on nc16 so i'm aproving this merge request

[newhinton]

@Bubu I am sorry to inform you that i need you to recreate this pull request. It was not signed, and i overlooked that it was not. We require you to sign this before we can merge it to the master branch. I would still like to include your code in passman, could you recreate the pr and sign the code beforehand? That would be very helpful! Sorry for the inconvenience!

[Bubu]

It was not signed,

It was actually. (Not in the first iteration but I force-pushed to this merge request after the bot told me it needed to be signed.)

(And I actually wondered at that time, can a contribution that solely removes code actually be under copyright? 🤔 )