Re: Committer's name misspelled in Whimsy roster

> On Aug 15, 2024, at 5:38 PM, Nathan Hartman wrote: > > Hi all, > > Please CC me on replies as I'm not subscribed. > > On Apache Subversion's roster, Whimsy shows one of our PMC member's name > with incorrect spelling: Timofei Zhakov's first name is shown as Timofey (y > instead of i; i is c

[jira] [Commented] (WHIMSY-402) remove "GitHub username" from details page

[ https://issues.apache.org/jira/browse/WHIMSY-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737913#comment-17737913 ] Chris Lambertus commented on WHIMSY-402: I agree with Dave in that this f

Re: Update email addresses in whimsy/committer

> On Feb 27, 2023, at 2:44 PM, sebb wrote: > > On Mon, 27 Feb 2023 at 21:30, Craig Russell wrote: >> >> I see that I can add/update/delete email addresses using id.apache.org: >> Forwarding email address: > > That's the LDAP 'mail' attribute. Correct, the content of that LDAP attribute is

Re: ldap "meta" ou

> On Jun 15, 2022, at 4:15 PM, sebb wrote: > > On Mon, 13 Jun 2022 at 19:12, Chris Lambertus <mailto:c...@apache.org>> wrote: >> Does this seem like a reasonable approach? > > It seems quite complicated compared with just fixing the existing > scrip

Re: ldap "meta" ou

> On Jun 13, 2022, at 10:57 AM, Sam Ruby wrote: > > On Mon, Jun 13, 2022 at 1:06 PM Chris Lambertus <mailto:c...@apache.org>> wrote: >> >>> On Jun 12, 2022, at 4:54 PM, sebb wrote: >>> >>> If the problem is just that recreating o

Re: ldap "meta" ou

that >> PMC members can update LDAP the PMC (i.e., both the PMC and committers >> lists). >> >> On Sun, Jun 12, 2022 at 6:56 PM sebb wrote: >>> >>> On Sun, 12 Jun 2022 at 21:26, Chris Lambertus wrote: >>>> >>>> >>>>

ldap "meta" ou

Hi folks, I have been working on some updates to the LDAP service, and I would like to get rid of ou=meta,ou=groups,dc=apache,dc=org (or at least the process which manages it.) Some history -- this ou was created to address a problem which arose after project groups were converted to member/o

whimsy subscription data

Hi folks, Could you please refresh my memory or point me at some documentation that describes how whimsy currently communicates with hermes vis a vis mailing list information? I am looking to understand the scope of changes which will be needed as we migrate to its replacement. Thanks, Chris

[jira] [Commented] (WHIMSY-383) root@ needs access to ICLAs

[ https://issues.apache.org/jira/browse/WHIMSY-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503021#comment-17503021 ] Chris Lambertus commented on WHIMSY-383: No auth changes are needed as far

[jira] [Created] (WHIMSY-383) root@ needs access to ICLAs

Chris Lambertus created WHIMSY-383: -- Summary: root@ needs access to ICLAs Key: WHIMSY-383 URL: https://issues.apache.org/jira/browse/WHIMSY-383 Project: Whimsy Issue Type: Improvement

Re: test LDAP instance downtime/updates

> On Oct 19, 2021, at 2:14 AM, sebb wrote: > > On Tue, 19 Oct 2021 at 05:23, Chris Lambertus wrote: >> >> It will not currently work on ASF hosts against idmtest without setting >> TLS_REQCERT=never because the puppet-based ldap.conf is configured to only >

Re: test LDAP instance downtime/updates

-L -D "uid=cml,ou=people,dc=apache,dc=org" uid=cml What is the command line/bind DN you are specifying when you get the error 32? > On Oct 15, 2021, at 4:47 AM, sebb wrote: > > On Thu, 7 Oct 2021 at 19:53, Chris Lambertus <mailto:c...@apache.org>> w

Re: test LDAP instance downtime/updates

cation methods are supported now? I remember being unable to > find an incantation of ldapsearch that could authenticate. > > Matt Sicker > >> On Oct 6, 2021, at 18:40, Chris Lambertus wrote: >> >> Hi folks, just to let you know, my primary testing and implementation

Re: test LDAP instance downtime/updates

Sep 29, 2021, at 11:15 AM, Chris Lambertus wrote: > > FYI, > > In https://issues.apache.org/jira/browse/INFRA-22091 > <https://issues.apache.org/jira/browse/INFRA-22091> a test ldap instance was > provided to the Whimsy project. This is a notification that Infra will be

test LDAP instance downtime/updates

FYI, In https://issues.apache.org/jira/browse/INFRA-22091 a test ldap instance was provided to the Whimsy project. This is a notification that Infra will be performing work on that host over the next few days. The system may be down and data

[jira] [Commented] (WHIMSY-351) https://whimsy.apache.org/roster tool very slow

[ https://issues.apache.org/jira/browse/WHIMSY-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394830#comment-17394830 ] Chris Lambertus commented on WHIMSY-351: As far as I can tell, this does in

[jira] [Commented] (WHIMSY-113) Have Secretary create new accounts directly

[ https://issues.apache.org/jira/browse/WHIMSY-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376916#comment-17376916 ] Chris Lambertus commented on WHIMSY-113: I know the topic has come up be

[jira] [Commented] (WHIMSY-113) Have Secretary create new accounts directly

[ https://issues.apache.org/jira/browse/WHIMSY-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376911#comment-17376911 ] Chris Lambertus commented on WHIMSY-113: I've gone ahead and updated t

[jira] [Commented] (WHIMSY-113) Have Secretary create new accounts directly

[ https://issues.apache.org/jira/browse/WHIMSY-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376908#comment-17376908 ] Chris Lambertus commented on WHIMSY-113: It looks like generate-dotq

[jira] [Commented] (WHIMSY-113) Have Secretary create new accounts directly

[ https://issues.apache.org/jira/browse/WHIMSY-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376905#comment-17376905 ] Chris Lambertus commented on WHIMSY-113: I'm sure we can come u

[jira] [Commented] (WHIMSY-113) Have Secretary create new accounts directly

[ https://issues.apache.org/jira/browse/WHIMSY-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376900#comment-17376900 ] Chris Lambertus commented on WHIMSY-113: It would be better to use ssh wh

[jira] [Commented] (WHIMSY-113) Have Secretary create new accounts directly

[ https://issues.apache.org/jira/browse/WHIMSY-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376899#comment-17376899 ] Chris Lambertus commented on WHIMSY-113: A * in the shadow field is the

[jira] [Commented] (WHIMSY-113) Have Secretary create new accounts directly

[ https://issues.apache.org/jira/browse/WHIMSY-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376883#comment-17376883 ] Chris Lambertus commented on WHIMSY-113: Regarding karma for an account crea

[jira] [Commented] (WHIMSY-113) Have Secretary create new accounts directly

[ https://issues.apache.org/jira/browse/WHIMSY-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376881#comment-17376881 ] Chris Lambertus commented on WHIMSY-113: I can provide a test LDAP inst

[jira] [Commented] (WHIMSY-351) https://whimsy.apache.org/roster tool very slow

[ https://issues.apache.org/jira/browse/WHIMSY-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300727#comment-17300727 ] Chris Lambertus commented on WHIMSY-351: Not talking about github. Talking a

[jira] [Created] (WHIMSY-351) https://whimsy.apache.org/roster tool very slow

Chris Lambertus created WHIMSY-351: -- Summary: https://whimsy.apache.org/roster tool very slow Key: WHIMSY-351 URL: https://issues.apache.org/jira/browse/WHIMSY-351 Project: Whimsy Issue

Re: whimsy.a.o: Password disclosure, information disclosure, file creation

able to vet the Ruby code so I can’t say for sure if there are vectors for non-authenticated users. Any infra staffer can restart the whimsy-vm4 VM as needed once the situation is addressed. -Chris > On May 5, 2020, at 8:35 PM, Chris Lambertus wrote: > > Whimsy project, please r

Fwd: whimsy.a.o: Password disclosure, information disclosure, file creation

Whimsy project, please respond to root@ and security@ ASAP with your assessment. The issues described by Daniel are quite serious, and may warrant shutting down the system until the problems are addressed. > Begin forwarded message: > > From: Daniel Shahaf > Subject: whimsy.a.o: Password d

[jira] [Created] (WHIMSY-317) mirror_check.cgi broken

Chris Lambertus created WHIMSY-317: -- Summary: mirror_check.cgi broken Key: WHIMSY-317 URL: https://issues.apache.org/jira/browse/WHIMSY-317 Project: Whimsy Issue Type: Task

Re: Error 500 on user details - see INFRA-19803

> On Feb 1, 2020, at 5:25 AM, Sam Ruby wrote: > > On Fri, Jan 31, 2020 at 11:18 PM Chris Lambertus <mailto:c...@apache.org>> wrote: >> >>> On Jan 31, 2020, at 6:49 PM, Shane Curcuru wrote: >>> >>> Sam Ruby wrote on 2020-1-3

Re: Error 500 on user details - see INFRA-19803

> On Jan 31, 2020, at 6:49 PM, Shane Curcuru wrote: > > Sam Ruby wrote on 2020-1-31 9:43PM EST: >> I've stubbed out the broken code: >> >> https://github.com/apache/whimsy/commit/0b8be7daf678465c0d856fdd2fedf2b30d2a0331 >> >>

[jira] [Commented] (WHIMSY-298) create/maintain meta-groups for PMCs in LDAP

[ https://issues.apache.org/jira/browse/WHIMSY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16965206#comment-16965206 ] Chris Lambertus commented on WHIMSY-298: It has not moved to p6 yet. We do

[jira] [Created] (WHIMSY-298) create/maintain meta-groups for PMCs in LDAP

Chris Lambertus created WHIMSY-298: -- Summary: create/maintain meta-groups for PMCs in LDAP Key: WHIMSY-298 URL: https://issues.apache.org/jira/browse/WHIMSY-298 Project: Whimsy Issue Type

[jira] [Commented] (WHIMSY-279) mirror check tool requires Member access

[ https://issues.apache.org/jira/browse/WHIMSY-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16897440#comment-16897440 ] Chris Lambertus commented on WHIMSY-279: Thanks! It seems to be working

[jira] [Commented] (WHIMSY-279) mirror check tool requires Member access

[ https://issues.apache.org/jira/browse/WHIMSY-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896489#comment-16896489 ] Chris Lambertus commented on WHIMSY-279: Infra's feeling is that

[jira] [Commented] (WHIMSY-279) mirror check tool requires Member access

[ https://issues.apache.org/jira/browse/WHIMSY-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896474#comment-16896474 ] Chris Lambertus commented on WHIMSY-279: This is blocking some infra staf

[jira] [Created] (WHIMSY-279) mirror check tool requires Member access

Chris Lambertus created WHIMSY-279: -- Summary: mirror check tool requires Member access Key: WHIMSY-279 URL: https://issues.apache.org/jira/browse/WHIMSY-279 Project: Whimsy Issue Type: Bug

[jira] [Commented] (WHIMSY-270) non-PMC groups need to be treated as projects

[ https://issues.apache.org/jira/browse/WHIMSY-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853740#comment-16853740 ] Chris Lambertus commented on WHIMSY-270: This is why I suggested the

[jira] [Commented] (WHIMSY-270) non-PMC groups need to be treated as projects

[ https://issues.apache.org/jira/browse/WHIMSY-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853723#comment-16853723 ] Chris Lambertus commented on WHIMSY-270: I agree [~sebb]. I am sure they c

[jira] [Commented] (WHIMSY-270) non-PMC groups need to be treated as projects

[ https://issues.apache.org/jira/browse/WHIMSY-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853542#comment-16853542 ] Chris Lambertus commented on WHIMSY-270: [~sebb] I don't see that

[jira] [Moved] (WHIMSY-270) non-PMC groups need to be treated as projects

[ https://issues.apache.org/jira/browse/WHIMSY-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lambertus moved INFRA-18520 to WHIMSY-270: INFRA-Members: (was: [infrastructure-team]) Component/s

Re: Moving Whimsy to new host: hermes cronjob updates

I would respectfully urge caution here, certainly not because of Dave, but in general: the whimsy server itself, along with the code which runs on it, has far more privileges to extract data from the Foundation than just about anything or anyone other than root@. Some of the data that Whimsy has

[jira] [Commented] (WHIMSY-113) Have Secretary create new accounts directly

[ https://issues.apache.org/jira/browse/WHIMSY-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827801#comment-16827801 ] Chris Lambertus commented on WHIMSY-113: Pursuant to the discussion

Re: decom of project CNs in ou=groups

> On Mar 10, 2019, at 10:26 AM, Chris Lambertus wrote: > > > >> On Mar 9, 2019, at 1:16 AM, sebb wrote: >> >> On Sat, 9 Mar 2019 at 02:44, Chris Lambertus wrote: >>> >>> Thank you for your work on this, Sebb. I need to go through the th

Re: Mail delivery issues in whimsy/workbench

n Mon, Mar 18, 2019 at 8:43 PM Craig Russell wrote: >> >> Whimsy mail is not working. There are no bounce/fail messages. >> >> Secretary workbench is officially down. >> >> No documents will be processed until mail can be sent from whimsy. >> >&

Re: Mail delivery issues in whimsy/workbench

If mail failed/bounced, it would bounce to the original sender address. -Chris > On Mar 18, 2019, at 3:28 PM, Craig Russell wrote: > > Hi, > > Whimsy could not deliver email after the reconfiguration(?) last week. > > Was there supposed to be some notification when mail was not delivered? >

workflow surrounding podling LDAP creation

Hi folks, There are two non-automated processes related to podling creation right now on the Infra side. One is creating DNS. The other is creating the LDAP entries for the podling. The LDAP creation is simply a matter of pushing a button in Whimsy. Is there a way the latter could be better a

Re: decom of project CNs in ou=groups

> On Mar 9, 2019, at 1:16 AM, sebb wrote: > > On Sat, 9 Mar 2019 at 02:44, Chris Lambertus wrote: >> >> Thank you for your work on this, Sebb. I need to go through the threads and >> make sure all the ’t’s are dotted and all the ‘i’s crossed, but then I’ll >

Re: decom of project CNs in ou=groups

ver is left (e.g. member, committers) >>> This involves fixing phonebook and projects.a.o; there are probably others. >>> >>> The cutover date of Feb 9th might be somewhat optimistic. >>> >>> I think we need to find out if there are any other projects using t

decom of project CNs in ou=groups

Sam, Whimsy Dev, Some time ago we migrated projects to use the ou=groups,ou=project format with owner and member attributes. The time has come to delete the legacy CNs. Sebb has outlined a potential issue with tac-pmc (INFRA-16188), but I’ve asked him for clarification as I’m not entirely cl

Re: ldap-eu-ro.apache.org timeouts

> On Feb 23, 2018, at 1:51 PM, sebb wrote: > >> >> Whimsy is in a US EC2 AZ. It should be using ldap-us-ro with eu-ro as a >> fallback. > > It uses all the defined LDAP servers in turn. CC: dev@whimsical In the case of Whimsy, which writes to LDAP, it could be switched over to ldap-mast

LDAP

Hi folks, I know some of you run a local test instance of Whimsy. If you do so, please note that Infra is replacing all LDAP servers with geo CNAMEs ldap-us-ro and ldap-eu-ro. If you have an LDAP configuration that uses anything other than these two names, please update it ASAP to avoid loss of

[jira] [Moved] (WHIMSY-154) Username display broken on whimsy.a.o

[ https://issues.apache.org/jira/browse/WHIMSY-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lambertus moved INFRA-15485 to WHIMSY-154: INFRA-Members: (was: [infrastructure-team]) Description

[jira] [Created] (WHIMSY-145) add redirect to mlreq page

Chris Lambertus created WHIMSY-145: -- Summary: add redirect to mlreq page Key: WHIMSY-145 URL: https://issues.apache.org/jira/browse/WHIMSY-145 Project: Whimsy Issue Type: Improvement

Re: LDAP title field

> On Apr 9, 2017, at 5:22 PM, Craig Russell wrote: > > tl;dr Adding title field is fine. I see it as secretary's responsibility to > harmonize iclas.txt and ldap. Ack. > We might as well add Suffix to LDAP to cater for the 23 III and 6 II that we > have. I've added a comment to IIINFRA-13850

LDAP title field

Hi Whimsy, I’m proposing in https://issues.apache.org/jira/browse/INFRA-13850 that we implement the Title field in LDAP. This would require some tooling changes that would involve Secretary, possibly whimsy code, and infra mods to the ap-addus

Re: Bug in account creation process?

marked as Only > in LDAP and synchronize that with iclas.txt. > > Please confirm. > > Regards, > > Craig > >> On Apr 4, 2017, at 7:58 PM, Chris Lambertus > <mailto:c...@apache.org>> wrote: >> >> >>> On Apr 4, 2017, at

Re: Bug in account creation process?

> On Apr 4, 2017, at 4:38 PM, sebb wrote: > > There are some other issues with the sn field: I don’t see any issues in your output. To improve LDAP tooling and functionality as we bring more LDAP-based services online, I fixed the ap-adduser script to add a valid givenName and sn to new acco

[jira] [Commented] (WHIMSY-49) Does INFRA-7390 have implications for allowable user ids?

[ https://issues.apache.org/jira/browse/WHIMSY-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15201924#comment-15201924 ] Chris Lambertus commented on WHIMSY-49: --- It was assigned to whimsy due to a bit

[jira] [Commented] (WHIMSY-51) can't remove pgp fingerprint from id.apache.org

[ https://issues.apache.org/jira/browse/WHIMSY-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181841#comment-15181841 ] Chris Lambertus commented on WHIMSY-51: --- I think all of that is TBD. There

[jira] [Moved] (WHIMSY-52) Duplicate emails after git merge

[ https://issues.apache.org/jira/browse/WHIMSY-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lambertus moved INFRA-7 to WHIMSY-52: --- INFRA-Members: (was: [infrastructure-team]) Component/s

[jira] [Commented] (WHIMSY-51) can't remove pgp fingerprint from id.apache.org

[ https://issues.apache.org/jira/browse/WHIMSY-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15181565#comment-15181565 ] Chris Lambertus commented on WHIMSY-51: --- Kicking this over to the whimsy pro

[jira] [Moved] (WHIMSY-51) can't remove pgp fingerprint from id.apache.org

[ https://issues.apache.org/jira/browse/WHIMSY-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lambertus moved INFRA-10234 to WHIMSY-51: --- Security: (was: public) Workflow: jira (was: INFRA

[jira] [Moved] (WHIMSY-49) Does INFRA-7390 have implications for allowable user ids?

[ https://issues.apache.org/jira/browse/WHIMSY-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lambertus moved INFRA-8396 to WHIMSY-49: -- Security: (was: public) Workflow: jira (was: INFRA Workflow

Re: Bug in new account page

Can you try this again please? This may have been due to a transient issue with LDAP. > On Jul 6, 2015, at 1:23 PM, Craig L Russell wrote: > > Hi, > > The drop down for project is unresponsive when accessing the new account page > from within the secretary assistant tool. Or outside. If I pre