16:06:54 #startmeeting FESCO (2016-12-02) 16:06:54 Meeting started Fri Dec 2 16:06:54 2016 UTC. The chair is sgallagh. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:06:54 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:06:54 The meeting name has been set to 'fesco_(2016-12-02)' 16:06:54 #meetingname fesco 16:06:54 The meeting name has been set to 'fesco' 16:06:54 #chair maxamillion dgilmore jwb nirik paragan jsmith kalev sgallagh Rathann 16:06:54 #topic init process 16:06:54 Current chairs: Rathann dgilmore jsmith jwb kalev maxamillion nirik paragan sgallagh 16:07:01 sgallagh++ 16:07:02 maxamillion: Karma for sgallagh changed to 5 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:07:06 (just staying up-to-speed) 16:07:23 .hello sgallagh 16:07:24 sgallagh: sgallagh 'Stephen Gallagher' 16:07:52 morning. 16:08:58 .hello maxamillion 16:08:59 maxamillion: maxamillion 'Adam Miller' 16:09:05 .hello rathann 16:09:06 Rathann: rathann 'Dominik Mierzejewski' 16:09:08 .hello kalev 16:09:09 kalev: kalev 'Kalev Lember' 16:10:17 We have quorum, let's get started. 16:10:19 #topic #1651 F26 System Wide Change: Fedora 26 Boost 1.63 upgrade 16:10:20 .fesco 1651 16:10:21 sgallagh: Issue #1651: F26 System Wide Change: Fedora 26 Boost 1.63 upgrade - fesco - Pagure - https://fedorahosted.org/fesco/ticket/1651 16:10:51 +1 rubber stamp 16:10:52 +1 16:11:09 +1 16:11:27 +1, though there seems to be a typo with boost version 16:11:31 sure, +1 16:12:00 what's the typo? 16:12:08 first sentence talks about 1.62 and the next about 1.61 16:12:56 weird, I only see 1.63 everywhere 16:14:07 #agreed F26 System Wide Change: Fedora 26 Boost 1.63 upgrade is approved (+5, 0, -0) 16:14:17 #topic #1650 F26 System Wide Change: Debugging Information For Static Libraries 16:14:17 .fesco 1650 16:14:17 kalev: I'm talking about the feature wiki page 16:14:18 sgallagh: Issue #1650: F26 System Wide Change: Debugging Information For Static Libraries - fesco - Pagure - https://fedorahosted.org/fesco/ticket/1650 16:14:20 https://fedoraproject.org/wiki/Changes/F26Boost163 16:15:06 Rathann: The jump is from 1.60 to 1.63. Those two paragraphs are describing what happened in the two intermediate releases that were skipped. 16:15:12 It doesnt' look like a typo to me 16:15:17 * kalev concurs. 16:15:30 ah 16:15:34 right, I misread 16:15:37 never mind 16:16:24 +1 to this change 16:16:35 +1 16:16:54 +1 from me as well. 16:17:04 +1 16:17:51 right, I remember this one 16:17:52 +1 16:17:59 /me notes that this change must be readied before the mass-rebuild 16:18:20 indeed 16:18:21 #agreed F26 System Wide Change: Debugging Information For Static Libraries is approved (+5, 0, -0) 16:19:00 Shall we assert that the contingency plan must go into effect if it's not ready by N days before the mass-rebuild? 16:20:16 I suppose that's more or less already in the change. 16:20:25 not sure it's necessary as the Change page explicitly mentions that it needs to go in before the rebuild 16:20:26 Though "final mass rebuild" is oddly-phrased. 16:21:09 #topic #1648 F26 System Wide Change: GHC 8.0 16:21:09 .fesco 1848 16:21:14 sgallagh: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:21:43 .fesco 1648 16:21:48 sgallagh: Issue #1648: F26 System Wide Change: GHC 8.0 - fesco - Pagure - https://fedorahosted.org/fesco/ticket/1648 16:22:06 +1 16:22:08 There are four +1s in the ticket 16:22:16 " with much improved support for aarch64, ppc64, and ppc64le" -- sounds like a good time now that these are all on primary koji 16:22:16 * maxamillion meant to +1 in ticket but forgot :/ 16:22:19 +1 16:22:43 #agreed F26 System Wide Change: GHC 8.0 is approved (+6, 0, -0) 16:23:48 #topic #1635 F26 Self Contained Changes (Java Security Policy) 16:23:48 .fesco 1635 16:23:50 sgallagh: Issue #1635: F26 Self Contained Changes - fesco - Pagure - https://fedorahosted.org/fesco/ticket/1635 16:24:46 jkurik requested the Change owner to provide additional information, but it has not happened. 16:24:53 +1 - seems like a sane change, I honestly didn't know that wasn't already the case ... I don't really Java 16:25:06 what's missing? 16:25:13 maxamillion: That's one of the open questions: it sounds like it maybe was supposed to already work but there was a bug that got fixed. 16:25:24 it's driven by our crypto toolset maintainer and I definitely trust that he knows what he's doing 16:25:26 It's unclear. 16:25:27 sgallagh: ahhh ok 16:26:14 Actually, reading further... 16:26:27 Looks like it was added to F24 and F25 (as a 0day update) 16:26:52 But it wasn't called out as a Change for either release, so if we wanted to approve it solely for marketing purposes, I could get behind that, I suppose. 16:27:22 (or we could just deny it and ask that they add it to the F26 release highlights when they get put together) 16:27:33 sgallagh: +1 16:27:38 Because it looks like there's nothing technical remaining to be done 16:27:50 from the last (private) comment, it looks like it's going to get reverted in older fedora releases 16:28:10 https://bugzilla.redhat.com/show_bug.cgi?id=1249083#c40 -- note the "ok" reply 16:28:32 /me nods 16:28:45 OK, I'm thinking we perhaps don't have enough information today. 16:28:47 private comments. yuck 16:28:52 I move to defer to next week. 16:29:07 sure, +1 16:29:17 +1 16:29:23 +1 to next week 16:30:14 #info FESCo defers this discussion to next week, as it's currently unclear what is the status of the effort. 16:30:25 ok 16:30:25 OK, that's the last item on the list marked with "meeting". 16:30:37 I didn't have a chance to groom them before the meeting (I wasn't scheduled to chair). 16:30:53 Anything on https://pagure.io/fesco/issues that we want to discuss? 16:31:04 * kalev looks 16:33:00 sudo's ticket sounds like "fun" mediating between the maintainer and the person who filed the ticket 16:33:05 Anyone want to discuss https://pagure.io/fesco/issue/1646 on sudo>? 16:33:36 #topic #1646 No appropriate sudo directory for user scripts 16:33:36 .fesco 1646 16:33:40 sgallagh: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:33:55 zodbot is having a rough day 16:34:33 The earlier one I figured was because of the typo... 16:34:34 .fesco 1646 16:34:38 sgallagh: An error has occurred and has been logged. Please contact this bot's administrator for more information. 16:34:44 nirik! ;-) 16:34:52 I think the addition of /usr/local/bin and /usr/local/sbin make sense but I also think that if that's needed, an administrator can just enable it so I'm a bit torn as I like the system being secure "out of the box" 16:35:40 Well, I think part of the issue is that there's no clear guideline on what /usr/local/bin is for 16:35:53 I think it makes sense too, but I don't particularly want to override the maintainer either 16:35:55 My *intuition* is that it's meant to be there for third-party tools 16:36:15 And that's why it exists in the default PATH 16:36:38 kalev: Well, the last comment from the maintainer sounds like he is looking for FESCo's thoughts on the matter. 16:36:43 ahhh 16:36:53 I'm not sure it's an "override" so much as him asking FESCo what the correct answer is 16:37:06 fair enough, sorry, I didn't read the ticket to the end 16:37:12 hm I wonder what sudo upstream default is 16:37:31 Rathann: +1 16:37:46 /me looks 16:39:30 upstream has no secure_path in examples/sudoers 16:39:38 That said, this isn't a *default*, it's an example. 16:39:40 my opinion here is that since putting things to /usr/local/bin requires root access, it should be fine to add it to sudo's path as well 16:39:49 it's not like anyone can sneak behind an admin and add things there 16:40:06 and it makes sense to have consistency between ubuntu and fedora 16:40:51 My mistake. 16:40:58 It's actually a compile-time option: /bin:/usr/ucb:/usr/bin:/usr/sbin:/sbin:/usr/etc:/etc 16:41:26 Which is actually much more lenient than our default :) 16:41:51 I see Solaris paths :) 16:42:00 still, no /usr/local/bin 16:43:19 I think I'm a weak -1 on adding /usr/local to secure_path. 16:43:28 I'd be inclined to leave it the way it is citing that the proposed paths are not included by defualt from upstream and are not well defined paths 16:43:37 -1 here as well 16:43:40 Nowadays, most people who install third-party software do it either in /usr or /opt 16:43:46 sgallagh: +1 16:44:03 /usr/local is rapidly becoming a legacy concept 16:44:26 I think it's worth checking if other Linux distributions (apart from Ubuntu) do have /usr/local/bin there 16:45:05 The only other relevant distro I can think of would be SUSE 16:45:26 Between the Fedora/RHT family, Debian and SUSE, that's where most of the rest take their cues 16:46:47 SUSE uses `Defaults secure_path = "/bin:/usr/bin:/sbin:/usr/sbin"` 16:47:00 Debian doesn't modify secure_path as far as I can tell 16:47:23 I'm -1 to adding /usr/local 16:47:30 Rathann: "modify" how? 16:47:43 ah 16:47:53 they ship a default sudoers 16:48:01 Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" 16:48:12 so that's probably why Ubuntu has it as well 16:48:14 yeah, I lean toward -1 as well. 16:48:39 I think it makes sense to have some kind of search path in the default config where admins can install scripts 16:48:53 just so that people can avoid editing the config file 16:48:57 I'm with kalev on this one 16:49:09 well, there is /etc/sudoers.d 16:49:18 I was about to say the same 16:49:31 yes, but you need to (remember to) put a file there 16:49:36 They can modify secure_path with a dropfile in sudoers.d if they don't want to touch the main file 16:50:12 kalev: Why wouldn't admins just install scripts in /usr/bin or /usr/sbin? 16:50:15 if we want to attract Ubuntu users, then every additional step they have to do on Fedora to get the same experience is a loss 16:50:49 so, I'm +1 to adding /usr/local/{bin,sbin} 16:51:13 it doesn't make things any less secure 16:51:13 sgallagh: because /usr/bin and /usr/sbin are tracked by rpm and if they want to install something manually, it's much clearer to see what they've installed if they put things in a separate directory 16:51:50 if they install something through rpm, then I totally agree that they should put things in /usr/bin, but quite often people do one-off hacks on their systems 16:52:15 and it makes sense to have a separate directory for these hacks I think 16:52:24 also, it's already in the default $PATH 16:52:46 so not having it in secure_path may be confusing 16:53:08 kalev: +1 16:53:40 I am just trying to say that the reason that _fedora_ doesn't install anything in /usr/local doesn't mean that local admin's can't find it useful 16:54:28 "make" + "make install" usually defaults to /usr/local, for example 16:54:59 Rathann: I don't really buy the "attract from Ubuntu" argument. As a whole, the set of people who know how to use sudo sufficiently to care about secure_default is a rather small subset of Ubuntu users 16:56:40 I mean, the other side of it is that you can *still use the full path* 16:56:57 The only purpose of this option is to set the PATH variable that the elevated process sees. 16:57:14 If you type `sudo /usr/local/myscript`, it's going to work. 16:57:30 If you care about more than that, changing the config is REALLY EASY. 16:58:31 what's the argument against changing the path? 17:00:11 I am just trying to understand, maybe there are good reasons :) 17:00:19 so far it seems to me that leaving /usr/local/bin out is just a weird annoyance for users 17:00:25 something that they'd probably find their way around, but also something that we should try and make work out of the box 17:00:26 kalev: The age-old "I forgot to type ./ before my command name and I accidentally ran something in the PATH instead" situation? 17:01:04 it opens up for a non-standard and not well defined location to be default in secure_path ... however, there seems to be a decent amount of "defacto standard" around it, I'm not hard -1 ... but for now I'm -1 17:01:38 yeah, but this is more like: people try to get this to work with sudo. it doesn't work. some admins are going to figure it out. others wont, and they end up giving root access to all people instead of using more secure sudo. 17:02:04 kalev: I'd be less hesitant about a well-named location. But I really don't like using /usr/local for this. I'd be more comfortable with /usr/custom-sudo/bin or something 17:02:30 kalev: I think that's a gross overstatement. People will make bad sudo decisions no matter what. 17:02:37 It's a complicated feature 17:02:38 indeed 17:02:43 I've made my fair share of them :) 17:02:58 I doubt anyone here could say otherwise with a straight face :) 17:02:59 (many years ago before I knew it was a bad decision) 17:04:16 Do we want to attempt to take this to a vote, or punt until we have a bigger quorum? 17:04:28 /me would like to get lunch 17:04:52 yes, dinner time here too! 17:05:23 sorry for arguing and dragging this meeting so long 17:05:54 If I'm counting correctly, we have +2 and -2 17:06:18 We're clearly not going to achieve the +5 that would be needed to make a decision today. 17:06:22 yup 17:06:27 table! :D 17:07:17 :D 17:07:51 table is ok with me, I keep getting sidetracked/sucked into things and would be nice to read the bug more fully. 17:08:06 #info FESCo discussed this issue but did not reach a decision today. We will discuss it again next week with hopefully a larger attendance. 17:08:18 #topic Open Floor 17:08:42 I may be missing next week, likely on a train with spotty connection at that time 17:09:03 * nirik actually will definitely be missing next week. I can vote in tickets tho 17:10:39 afaik I will be here next week but I have jury duty on Tuesday ... so if I get selected I might not make it 17:10:43 Oh, I forgot: 17:10:43 #topic Next Week's Chair 17:11:24 I could maybe take it in two weeks, but definitely not next week 17:11:32 I have a dentist appointment next week and don't know if I'll be able to attend, much less chair 17:12:22 ... 17:12:54 I can take next week's chair ... but I'm not convinced we will have quarum 17:13:17 quorum* 17:13:17 maxamillion: Thanks. If you end up with jury duty, I'll be your backup 17:13:23 sgallagh: thanks 17:13:26 #info maxamillion to chair next week's meeting. 17:13:48 sgallagh: if that happens, I'll be sure to email to let you know so it's not a surprise thing 17:13:55 Thanks 17:15:14 OK, I'm closing out the meeting. Thanks for coming, everyone. 17:15:19 #endmeeting