Hi John, yes, the mercurialeclipse account is under my control and the password should be secure - I just reset it yesterday in order to access the repository settings, as I didn’t even remember it ;).
Best regards Bastian > Am 07.12.2016 um 23:33 schrieb Amenel Voglozin <[email protected]>: > > Thanks Bastian, I can now assign bugs to myself. > > John, I'll add two-factor auth to my account after I have confirmed the > pending issues with '@' character in SSH logins as resolved. > > I indeed saw the wiki history... I've experienced wikis that allow anonymous > editing or that allow anyone with an account to edit. If so, maybe that this > possibility should be denied. > > I've also forked the update site a few days ago for the issue you've > mentioned. I hope to be able to look into it next week-end. > > Thank you all. > > > 2016-12-07 22:53 GMT+01:00 John Peberdy <[email protected] > <mailto:[email protected]>>: > Hi all, > > The vandalism I saw showed up in the repo log as "Edited from the web > interface" or similar. Based on this I think it was someone with contributor > rights or someone with access to the account of a contributor was making > changes. The changes are visible in wiki history and seemed to me to point to > non-existent URLs so it didn't seem malicious. > > For this reason I revoked all contributor rights. The only account I > didn't/couldn't revoke is the "mercurialeclipse" owner account. Does someone > have access to that account and can confirm the password is secure? Bastian, > is that you? > > All contributors, please add 2 factor authentication to your bitbucket > account. > > Lastly, someone mentioned the current update site jar files were getting > blocked by an antivirus. If someone could confirm that is a false positive > and/or come up with different ideally transparent way of building the update > site I would appreciate it and it would allow us to add the update site URL > back to the wiki page. > > Cheers, > John > > > > On Wednesday, December 7, 2016 at 12:33:31 PM UTC-5, Bastian Doetsch wrote: > Id be happy to give you administration rights :) > > Bastian > -- via mobile > > Am 07.12.2016 um 17:24 schrieb Amenel Voglozin <[email protected] > <mailto:[email protected]>>: > >> Hi, >> >> I'm trying to reach any admin of the MercurialEclipse repository at >> BitBucket, so that my access to the repository may be restored. >> >> As I've discussed with John Peberdy in the past, I prefer to contribute to >> the project via pull requests and via answering people's question on the >> issue tracker instead of using my write access to the repository. However, I >> realized today that I can't edit issues. I can't assign an issue to myself >> anymore. Although that won't keep me from working on the project, it will in >> the near future be a bit more than a hindrance. >> >> I've also realized that the reply address to which I sent a reply when I was >> notified that my access level was changed to "read" is a noreply address. >> Therefore, I'll reiterate my request here: is it possible for some admin to >> make it so that I get notified when a new issue is created? >> >> I've just read John's message on the Wiki about the vandalism. Are there >> administration tools on BitBucket that can help identify and ban these >> vandals? At least, those people's actions would not negatively affect the >> project, which hasn't been seeing much activity for some time now, which in >> turn leaves me worried as Mercurial and Eclipse are both evolving while the >> project is not, or barely. >> >> What means other than this public Google Group do contributors have to reach >> the admins? The link on John's BitBucket profile is dead, the vectrace >> domain is apparently for sale, and there's no e-mail address anywhere. >> >> Last, can we create a private hgE-dev mailing list or group for the active >> contributors and the admins? >> >> Thank you. >> -Amenel. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "MercurialEclipse" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] >> <mailto:[email protected]>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "MercurialEclipse" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "MercurialEclipse" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "MercurialEclipse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
