@uwi: We removed the ciphersuite from the server and tested with 4.2.0 that you get an update notification now. Because of some caching you may need to

This is due to an update of the server providing the version info. The server (Apache) uses a smaller hash than the ECC key. This is allowed behaviour and was fixed in our TLS library in 2022; see T6059. However, the new library was released only early this year an. We will check whether we can tell our Apache to use a more correct hash algorithm.

Is currently not enabled, sorry. Use git:// ot the mirror here at dev.gnupg.org. Note that we sign all our commits using a token and as such it is a stronger security prove than a just an arbitrary TLS connection.

The site is on purpose w/o Javascript which might be the cause for things you reported. But I agree that the tab order is not as one would expect.

Anyway, thanks for fixing this.

It does work indeed!

Guessing that it works now.

Meanwhile fixed.

We have new box meanwhile.

We do manual approvals.

Here's mirroring script that is in place currently:

#!/bin/bash -e

@jukivili was so kind and does the mirroring now.

I just moved Phabricator to a new machine and created separte certificates for files.gnupg.net and dev.gnupg.org.

Sorry.

Thank you for the answer then! You can probably review our guide then https://github.com/ossf/great-mfa-project/blob/main/guide/token-usage-guide.md :)

Thanks for the offer. However, the core developers are using tokens for more than a decade meanwhile. We even make our own tokens ;-).

Since the migration to a new machine with lots of config changes this spring the redirect rules for bugs.gnupg.org were not properly adjusted and when running into an error, it seems that the admin back then ignored the problem and simply removed bugs.gnupg.org from dehydrated's list of domains. Thanks again for reporting. Should now work again.

Right, our installation really needs an update. It is not gnupg.org mail but just the mails from phabricator - which unfortunately does not use our standard mail system

@dkg: Please keep using slashes. The problem was that slashes are not allowed in git config keys. We use the branch name in some git config keys and thus they need to be mapped to soemthing different (ie. '-').

It works for me.

fwiw, i'm used to using slashes in my branch names in dozens of other projects. I was trying to keep my branches scoped under dkg/ so that others could ignore them if they wanted. If the only issue is that i need to not do that, i'm fine naming them with hyphens instead of slashes (or whatever). I'll use that rule for future work.

Just did that: slashes and dots are now mapped to hyphens. Let me know if the problem persists.

That is due to the update hook which has code like this:

That might have been a regression since one of the Phrabricator updates (we need to apply out own patches each time).

Reolved since summer last year.

well, Firefox DE on OSX gives same error Unhandled Exception ("HTTPFutureHTTPResponseStatus")

When did you last try to login to dev.gnupg.org? What browser and OS are you using. Did you try with this account?

I will disable your account but destroying the account and all data is not possible because this has public interlinked content. The intro page at dev.gnupg.org clearly explains this as welll as the privacy policy linked from the side menu; excerpt

close my account

I disabled your account but the I won't delete any comments of yours. They are considered to be in the public domain (see welcome page) and are parts of other bug reports. Thanks for those comments.

For transparency reasons: Intevation will make Werner an offer for maintaining dev.gnupg.org.

The new tool is called txxmpp.

I disabled your account. If might be possible to remove mail addresses from the DB but I don't known how to do that.

Nice code. Need to revisit the jabber protocol to understand what to do.

I am now looking into libstrophe.

No problems, if you get struggled I am here up to go extra mile for an ideal. Regards "convenience" ... well I quite agree with Richard Stallman on the specific topic the trade off between " freedom Vs convenience" https://www.youtube.com/watch?v=CP8CNp-vksc (jump to video @1minutes, 15 seconds) ;-)

We already have a donated machine with everything setup. This is not going to change. Twitter logon is just a convenience for many folks because there are just so many twitter accounts. And after all this is a public tracker.

Hi, Werner what are the machinery requirements required for running the VM ? I can try to squeeze my academic schedule to do it but I probably would like to change twitter login for something more 'GNU' such as https://mastodon.sdf.org/about

Done. Thank you for stopping by.

Retested today: Works again. So I can confirm the resolution of this task.
Thanks @marcus !

No new tools.

The server was replaced due to failure. New IP addresses are: 109.235.43.70 and 2001:678:340::70. I updated the DNS entries, and they seem to have propagated (but your local cache may still refer to the old entries).

Unfortunately, I cannot find a better tool that seems mature, maintained, and packaged for Debian. Maybe it is best to improve the current tool.

Gathered information:

To avoid a single point of failure I would prefer to keep the wiki off from al-kindi and, if Intevation agrees, to keep it where it is.

@marcus you've closed it while I was adding stuff. Where shall we document the way forward? In wiki.gnupg.org or https://dev.gnupg.org/w/ or in this task?

Mail send: https://lists.gnupg.org/pipermail/gnupg-devel/2017-August/033012.html

After reviewing the content on the wiki, I don't think anymore that migrating the wiki as a whole is a good strategy, so I will close this simplicistic task. Discussing on the mailing list is of course appropriate.

Note that we could switch the wiki.gnupg.org back to local authentification
(or any other authentification that moinmo.in provides, see https://moinmo.in/AuthMarket)
and continue using it.

Good enough for now.