Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: 1.9.x - Implement SECUREDACCESS  (Read 3430 times)

0 Members and 1 Guest are viewing this topic.

Charles Kingsley

  • Contributor
  • *
  • Offline Offline
  • Posts: 1405
1.9.x - Implement SECUREDACCESS
« on: August 02, 2009, 10:11:11 AM »

Viper raised bug #1084:

Quote
chan_set_correct_modes() does not currently remove voices that are not "legally
acquired" (not on access list when secureops is on)..
Main issue is whether secureops should apply to voices too.. it s a simple
on/off and currently affects qaoh, but not v..

I ran into the issue because one of my modules uses this function to
synchronize  users' status with the access list and voices never were removed..
Whether it s something that needs to be changed, is up for discussion.. :)

It has been decided to leave it as is on the stable branch but to open the idea of SECUREDACCESS which does include voice's for 1.9.x.

Thoughts?
Logged

MeiR

  • Anope User
  • Offline Offline
  • Posts: 49
Re: 1.9.x - Implement SECUREDACCESS
« Reply #1 on: August 02, 2009, 05:54:46 PM »

hm.. I belive that SecureOPS refers to.. well, ops.
but still, why not making it a conf directive? "SecureOpsIncVoice" or something..
in order to leave the decision for every spceific channel owner?

and how "chan_set_correct_modes()" will act after implementing SECUREDACCESS? by checking whether it's on or off and update voices accordingly?
Logged

Darth Panda

  • Anope User
  • Offline Offline
  • Posts: 33
    • Cheap Software
Re: 1.9.x - Implement SECUREDACCESS
« Reply #2 on: August 02, 2009, 10:48:02 PM »

Since +v has no privileges other than the ability to talk in +m channels, I fail to see how devoicing a user would be considered "more secure" in any scenario.

I agree it should remain as is too.
Logged
Some things just don't need to be fixed.
Less is usually more.
One meets his destiny often on the road he takes to avoid it.

MeiR

  • Anope User
  • Offline Offline
  • Posts: 49
Re: 1.9.x - Implement SECUREDACCESS
« Reply #3 on: August 02, 2009, 11:10:11 PM »

we discussed it a bit on the IRC channel
mooncup suggested "/cs set #chan secure 0/1/2"
but since:
Quote
«20:22:26» (%Namegduf) Ew.
«20:22:31» (mooncup) :P
«20:22:42» (mooncup) numberphobic? D:
I think "/cs set #chan secure ops|all|off" will be good
Logged

Taylor

  • Contributor
  • *
  • Offline Offline
  • Posts: 99
Re: 1.9.x - Implement SECUREDACCESS
« Reply #4 on: August 02, 2009, 11:33:41 PM »

I like your way  /cs set $chan secure ops|all|off
i sometimes like to remove even voice cause we use it as a VIP status :P
so yea
Logged
Cronus
irc.cncirc.net
http://CnCIRC.net
Pages: [1]   Go Up