| 00:05.27 | Patlabor221 | awww... no bzflag webGL version until they fix the bugs :( |
| 00:12.31 | blast007 | which bugs? |
| 00:14.09 | Patlabor221 | memory bugs :) |
| 00:14.40 | Patlabor221 | https://www.invertedpolarity.com/code/bzflag/BZU_WebGL/ |
| 00:16.25 | Patlabor221 | and that's giving it a gig |
| 00:17.10 | Patlabor221 | no more free vs pro feature BS tho |
| 01:08.26 | *** join/#bzflag Constitution (~josh@bzflag/developer/Constitution) |
| 01:34.08 | allejo | is it intentional for bz_grantPerm() to only grant built-in perms? |
| 03:05.45 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 05:30.42 | *** join/#bzflag Pimpinella (~frank@gondolin.pimpi.org) |
| 06:25.06 | BulletCatcher | allejo, look to see how 2.99 does it. |
| 06:25.25 | allejo | bz_grantPerm() or the slash command? |
| 06:25.44 | BulletCatcher | bz_grantPerm() |
| 06:32.52 | allejo | doesn't seem to be a change |
| 06:34.41 | *** join/#bzflag noyb (~noyb@cpe-172-248-224-184.socal.res.rr.com) |
| 06:39.35 | BulletCatcher | A comment in Permissions.cxx says "custom perms are ONLY on groups" so the behavior seems to be intentional. |
| 06:39.36 | BulletCatcher | I don't know the rationale, though. |
| 06:40.10 | allejo | wait so you can't bz_grantPerm() to a specific player? that's lame |
| 06:40.33 | BulletCatcher | It works on built-in permissions, but not custom ones. |
| 06:41.01 | allejo | git blames Patlabor221 |
| 06:41.22 | allejo | well yea, you can't bz_grantPerm() a custom perm to a specific player* |
| 06:41.40 | Patlabor221 | Custom perms didn't exist then |
| 06:42.31 | allejo | ohh that would explain it |
| 06:42.43 | Patlabor221 | I can't think of any reason to not let them work, other then the perms arnt really "registered" |
| 06:43.05 | Patlabor221 | So you may not know if a word is a valid perm or not |
| 06:43.40 | allejo | does that matter? there would just be a typo in the perm, the plugin would ignore it since it only looks for a specific word |
| 06:44.16 | Patlabor221 | It's not good to let the user think something worked when it may not have |
| 06:44.26 | Patlabor221 | You loose typo protection |
| 06:44.55 | Patlabor221 | Now you've made kull a valid perm |
| 06:45.08 | Patlabor221 | Make the plugin register valid perm strings |
| 06:45.19 | allejo | but there's no check for invalid perms atm |
| 06:45.32 | Patlabor221 | Maybe there should be |
| 06:45.37 | allejo | otherwise, how would custom perms work? |
| 06:45.44 | Patlabor221 | But that's the only thing that comes to mind |
| 06:46.19 | Patlabor221 | They were intended to let plugins know about crap in groups |
| 06:46.54 | Patlabor221 | Probably just me thinking individual perms are a bad idea |
| 06:47.03 | Patlabor221 | Roles are more secure |
| 06:47.28 | allejo | i agree they are but without individual perms, it renders plugins like superUser useless with custom perms |
| 06:47.41 | Patlabor221 | If you are going to keep per user perms then make them all consistent |
| 06:48.12 | allejo | consistent how? |
| 06:48.13 | Patlabor221 | Maybe it's a useless plugin :) |
| 06:48.29 | Patlabor221 | Custom and std perms should work the same |
| 06:48.45 | Patlabor221 | And both should be validated for typos IMHO |
| 06:49.05 | Patlabor221 | Users should not have care if it's custom or std |
| 06:50.00 | Patlabor221 | It doesn't really matter what the intent was, make it useful for what you need |
| 06:50.16 | allejo | superUseless isn't useless, there are times you want to give only a specific some permissions without the need for a group just for a single user |
| 06:50.37 | Patlabor221 | If you say so |
| 06:51.05 | Patlabor221 | That is the path of madness imho, but it's your server |
| 06:51.49 | allejo | :x |
| 06:51.50 | BulletCatcher | You can define server-local groups with bzfs -groupdb. |
| 06:52.20 | Patlabor221 | Yeah |
| 06:52.52 | BulletCatcher | Or maybe -userdb (or both). It's been a long time since I used that feature. |
| 06:53.05 | Patlabor221 | With individual perms you have people who don't conform to a role, and from a general security standpoint that makes audits harder |
| 06:53.23 | Patlabor221 | Not that bzflag user files are super big |
| 06:54.14 | Patlabor221 | With all the security problems of late, do you really want another way for someone to get elevated permissions? |
| 06:54.42 | allejo | I was under the impression that local groups were discouraged for that reason |
| 06:54.44 | Patlabor221 | With groups you HAVE to edit a file on the server to add perms |
| 06:55.00 | Patlabor221 | Local passdb is discouraged |
| 06:55.16 | Patlabor221 | Local gropups are probably more secure then global |
| 06:55.31 | Patlabor221 | If the bags is properly secured |
| 06:55.43 | Patlabor221 | Bzflag server sorry |
| 06:55.48 | Patlabor221 | Silly ipad |
| 06:55.51 | allejo | lol |
| 06:56.28 | Patlabor221 | Local user do is probably just as secure |
| 06:56.48 | allejo | are there any sample userdb files? it's been a while since i've used that |
| 06:57.01 | Patlabor221 | Probably somewhere |
| 06:57.14 | Patlabor221 | It's where you'd have to store the perms |
| 06:59.05 | Patlabor221 | But I can see no practical reason in the scope of a silly tank game to not make custom perms work on a per user basis |
| 06:59.39 | Patlabor221 | I think you should register them for spellcheck and autocomplete if people are going to be typing them in |
| 07:00.15 | Patlabor221 | Since they were in groups before we didn't need to have them sent over chat |
| 07:00.25 | allejo | the only typing of perms would be in the config file, no user input. at least for my needs right now |
| 07:00.44 | Patlabor221 | If you spell a std perm wrong does it get added to the user file now? |
| 07:01.00 | Patlabor221 | K |
| 07:01.40 | Patlabor221 | If you do send them over the wire I can see some issues blindly storing unknown perms |
| 07:02.06 | allejo | I mean the only change would be support custom perms in the API, if a plugin allows for user input then that would be on the plugin dev's |
| 07:02.18 | Patlabor221 | I |
| 07:02.20 | Patlabor221 | I |
| 07:02.23 | Patlabor221 | Bath |
| 07:02.27 | Patlabor221 | Bahhhhhhh |
| 07:02.41 | Patlabor221 | Silly apple thing |
| 07:02.43 | allejo | uhm what? |
| 07:03.06 | Patlabor221 | I was tying to just type "K" |
| 07:03.19 | Patlabor221 | But the thumbs |
| 07:03.24 | Patlabor221 | , they fail me |
| 07:03.37 | allejo | lol |
| 07:03.44 | BulletCatcher | My old userdb file has the callsign on line 1, space separated list of groups on line 2, and 2 blank lines. |
| 07:03.45 | BulletCatcher | Repeat for each user. |
| 07:04.08 | BulletCatcher | Line 3 is probably reserved for something. |
| 07:04.08 | Patlabor221 | Yeah I recall it being pretty simple |
| 07:04.56 | Patlabor221 | Iirc it's add perms on line 3 then deny perms after that |
| 07:05.03 | Patlabor221 | Or something like that |
| 07:05.16 | BulletCatcher | "Use the source, Luke." |
| 07:05.31 | Patlabor221 | Not on an iPad ð |
| 07:05.39 | allejo | writes that down for future reference |
| 07:06.20 | Patlabor221 | It's allejo's fault for making the thing show me a notification |
| 07:06.46 | Patlabor221 | was clashing his clan |
| 07:06.50 | allejo | :D |
| 07:12.15 | Patlabor221 | Also getting up to view source would anger the cats that are using me as a heat source |
| 08:16.41 | *** join/#bzflag Not-dca0 (~notifico@198.199.82.216) |
| 08:16.41 | Not-dca0 | [02bzflag-import-3] 07allejo pushed 031 commit to 03v2_4_x [+0/-0/±3] 13http://git.io/x1HV |
| 08:16.44 | Not-dca0 | [02bzflag-import-3] 07allejo 03547fdba - Add support for custom perms to the plugin API bz_grantPerm() and bz_revokePerm() will now be able to add/remove custom perms on a per-player basis |
| 08:18.42 | allejo | Not's back! |
| 08:40.24 | *** join/#bzflag Delusional_ (~Delusiona@unaffiliated/delusional) |
| 11:02.17 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 11:02.23 | *** join/#bzflag death__ (~I_Died_On@c-71-226-67-5.hsd1.ga.comcast.net) |
| 11:47.16 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 11:56.39 | blast007 | also, I believe the API function for getting a list of permissions for a group only returns the permissions that the group gets, not the ones that the group takes away. So, -TALK or !TALK wouldn't show up in the returned data. |
| 11:57.45 | blast007 | unless that has changed, which I doubt. I recall having issues with that when I was writing my authorPerms plugin (which took the bzid of a map author and gave additional permissions based on a custom local group). |
| 11:58.59 | blast007 | I think it was be okay to require "registering" custom permissions with a plugin since they really only do something if you have a custom plugin |
| 11:59.28 | blast007 | but, to avoid breaking plugins, that would probably go into 2.5 |
| 15:26.44 | *** join/#bzflag rodgort (~rodgort@105.ip-167-114-152.net) |
| 16:58.17 | *** join/#bzflag sirquine (~quine@c-67-162-133-17.hsd1.co.comcast.net) |
| 20:12.58 | *** join/#bzflag unclelightning (~chatzilla@pool-64-222-254-157.port.east.myfairpoint.net) |
| 22:13.03 | *** join/#bzflag DTRemenak (~DTRemenak@cpe-76-90-124-134.socal.res.rr.com) |
| 22:13.04 | *** join/#bzflag DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 22:13.04 | *** mode/#bzflag [+v DTRemenak] by ChanServ |