Skip to content

Commit 333f798

Browse files
committed
Move to Codeberg
GitHub is staying as a fully functional mirror though. You can still post issues and pull requests there.
1 parent 9d2087d commit 333f798

File tree

10 files changed

+27
-20
lines changed

10 files changed

+27
-20
lines changed

README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -45,8 +45,8 @@ Follow our Mastodon feed for release notes and other acme4j related news.
4545

4646
## Contribute
4747

48-
* Fork the [Source code at GitHub](https://github.com/shred/acme4j). Feel free to send pull requests (see [Contributing](CONTRIBUTING.md) for the rules).
49-
* Found a bug? [File a bug report!](https://github.com/shred/acme4j/issues)
48+
* Fork the [Source code at Codeberg](https://codeberg.org/shred/acme4j) or [GitHub](https://github.com/shred/acme4j). Feel free to send pull requests (see [Contributing](CONTRIBUTING.md) for the rules).
49+
* Found a bug? [File a bug report!](https://codeberg.org/shred/acme4j/issues) ([GitHub](https://github.com/shred/acme4j/issues))
5050

5151
## License
5252

@@ -61,5 +61,5 @@ If you would like to support my work on _acme4j_, you can do so on at [GitHub Sp
6161
* I would like to thank Brian Campbell and all the other [jose4j](https://bitbucket.org/b_c/jose4j/wiki/Home) developers. _acme4j_ would not exist without your excellent work.
6262
* Thanks to [Daniel McCarney](https://github.com/cpu) for his help with the ACME protocol, Pebble, and Boulder.
6363
* [Ulrich Krause](https://github.com/eknori) for his help to make _acme4j_ run on IBM Java VMs.
64-
* I also like to thank [everyone who contributed to _acme4j_](https://github.com/shred/acme4j/graphs/contributors).
64+
* I also like to thank [everyone who contributed to _acme4j_](https://codeberg.org/shred/acme4j/activity/contributors).
6565
* The Mastodon account is hosted by [foojay.io](https://foojay.io).

pom.xml

+5-5
Original file line numberDiff line numberDiff line change
@@ -34,14 +34,14 @@
3434
</license>
3535
</licenses>
3636
<scm>
37-
<url>https://github.com/shred/acme4j/</url>
38-
<connection>scm:git:git@github.com:shred/acme4j.git</connection>
39-
<developerConnection>scm:git:git@github.com:shred/acme4j.git</developerConnection>
37+
<url>https://codeberg.org/shred/acme4j/</url>
38+
<connection>scm:git:git@codeberg.org:shred/acme4j.git</connection>
39+
<developerConnection>scm:git:git@codeberg.org:shred/acme4j.git</developerConnection>
4040
<tag>HEAD</tag>
4141
</scm>
4242
<issueManagement>
43-
<system>GitHub</system>
44-
<url>https://github.com/shred/acme4j/issues</url>
43+
<system>Codeberg</system>
44+
<url>https://codeberg.org/shred/acme4j/issues</url>
4545
</issueManagement>
4646
<developers>
4747
<developer>

src/doc/docs/ca/buypass.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -19,4 +19,4 @@ private static Supplier<KeyPair> ACCOUNT_KEY_SUPPLIER = () -> KeyPairUtils.creat
1919

2020
## Disclaimer
2121

22-
_acme4j_ is not officially supported or endorsed by Buypass. If you have _acme4j_ related issues, please do not ask them for support, but [open an issue here](https://github.com/shred/acme4j/issues).
22+
_acme4j_ is not officially supported or endorsed by Buypass. If you have _acme4j_ related issues, please do not ask them for support, but [open an issue here](https://codeberg.org/shred/acme4j/issues).

src/doc/docs/ca/google.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,4 +20,4 @@ _Google Trust Services_ request `HS256` as MAC algorithm. If you use the connect
2020

2121
## Disclaimer
2222

23-
_acme4j_ is not officially supported or endorsed by Google. If you have _acme4j_ related issues, please do not ask them for support, but [open an issue here](https://github.com/shred/acme4j/issues).
23+
_acme4j_ is not officially supported or endorsed by Google. If you have _acme4j_ related issues, please do not ask them for support, but [open an issue here](https://codeberg.org/shred/acme4j/issues).

src/doc/docs/ca/sslcom.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -18,4 +18,4 @@ Available since acme4j 3.2.0. **This provider is experimental!**
1818

1919
## Disclaimer
2020

21-
_acme4j_ is not officially supported or endorsed by SSL.com. If you have _acme4j_ related issues, please do not ask them for support, but [open an issue here](https://github.com/shred/acme4j/issues).
21+
_acme4j_ is not officially supported or endorsed by SSL.com. If you have _acme4j_ related issues, please do not ask them for support, but [open an issue here](https://codeberg.org/shred/acme4j/issues).

src/doc/docs/ca/zerossl.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,4 +22,4 @@ ZeroSSL does not provide a staging server (as of February 2024).
2222

2323
## Disclaimer
2424

25-
_acme4j_ is not officially supported or endorsed by ZeroSSL. If you have _acme4j_ related issues, please do not ask them for support, but [open an issue here](https://github.com/shred/acme4j/issues).
25+
_acme4j_ is not officially supported or endorsed by ZeroSSL. If you have _acme4j_ related issues, please do not ask them for support, but [open an issue here](https://codeberg.org/shred/acme4j/issues).

src/doc/docs/faq.md

+9-2
Original file line numberDiff line numberDiff line change
@@ -71,9 +71,9 @@ You can still revoke certificates without account key pair though, see [here](us
7171

7272
**Symptom:** You try to order an S/MIME certificate from a providing CA. However, the CA constantly refuses the response e-mail because the contained ACME response is purportedly invalid.
7373

74-
**Cause:** Unfortunately [RFC 8823](https://tools.ietf.org/html/rfc8823) has an ambiguous specification about how to concatenate the two token parts. The text permits two different interpretations that may give different results. _acme4j_ uses an implementation that corresponds to the [intention of the author of RFC 8823](https://mailarchive.ietf.org/arch/msg/acme/KusfZm3qC50IfcAAuTXtmbFK0KM/). If the CA is implemented following the other interpretation, the ACME e-mail response will not match (see [this issue](https://github.com/shred/acme4j/issues/123)).
74+
**Cause:** Unfortunately [RFC 8823](https://tools.ietf.org/html/rfc8823) has an ambiguous specification about how to concatenate the two token parts. The text permits two different interpretations that may give different results. _acme4j_ uses an implementation that corresponds to the [intention of the author of RFC 8823](https://mailarchive.ietf.org/arch/msg/acme/KusfZm3qC50IfcAAuTXtmbFK0KM/). If the CA is implemented following the other interpretation, the ACME e-mail response will not match (see [this issue](https://codeberg.org/shred/acme4j/issues/123)).
7575

76-
**Solution:** It is a difficult situation that is caused by an ambiguous specification, but it is like it is now. Since _acme4j_ follows the intention of the RFC author, I take the position that the _acme4j_ implementation is correct. Please open a bug report at the CA, and refer to [this issue](https://github.com/shred/acme4j/issues/123). If the two tokens are split at a position, so the first token won't have trailing base64 padding bits, the CA service can be implemented in a way that is compatible to both interpretations.
76+
**Solution:** It is a difficult situation that is caused by an ambiguous specification, but it is like it is now. Since _acme4j_ follows the intention of the RFC author, I take the position that the _acme4j_ implementation is correct. Please open a bug report at the CA, and refer to [this issue](https://codeberg.org/shred/acme4j/issues/123). If the two tokens are split at a position, so the first token won't have trailing base64 padding bits, the CA service can be implemented in a way that is compatible to both interpretations.
7777

7878
## Suddenly acme4j starts throwing `AcmeUserActionRequiredException` everywhere! How can I fix that?
7979

@@ -85,6 +85,13 @@ You can still revoke certificates without account key pair though, see [here](us
8585

8686
Unfortunately, manual action is required in any case, there is no way to automate this process. This is an intentional protocol decision, and _acme4j_ is just the messenger.
8787

88+
## Where can I find the _acme4j_ Repository?
89+
90+
* The main repository is hosted at [Codeberg](https://codeberg.org/shred/acme4j).
91+
* There is a fully functional mirror at [GitHub](https://github.com/shred/acme4j).
92+
93+
You can use both sites for posting issues and pull requests. However, Codeberg is the preferred repository.
94+
8895
## Where can I find more help?
8996

9097
* [Let's Encrypt Documentation](https://letsencrypt.org/docs/)

src/doc/docs/index.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ACME is a protocol that a certificate authority (CA) and an applicant can use to
66

77
This Java client helps to connect to an ACME server, and performing all necessary steps to manage certificates.
88

9-
The source code can be found at [GitHub](https://github.com/shred/acme4j) and is distributed under the terms of [Apache License 2.0](http://www.apache.org/licenses/LICENSE-2.0).
9+
The source code can be found at [Codeberg](https://codeberg.org/shred/acme4j) and is distributed under the terms of [Apache License 2.0](http://www.apache.org/licenses/LICENSE-2.0).
1010

1111
Latest version: ![maven central](https://shredzone.org/maven-central/org.shredzone.acme4j/acme4j/badge.svg)
1212

@@ -41,7 +41,7 @@ There is an [example source code](example.md) included in this project. It gives
4141

4242
## Modules
4343

44-
_acme4j_ consists of four modules. All modules are [available at Maven Central](https://mvnrepository.com/artifact/org.shredzone.acme4j) and can easily be added to the dependency list of your project. You can also download the jar files [at GitHub](https://github.com/shred/acme4j/releases/latest).
44+
_acme4j_ consists of four modules. All modules are [available at Maven Central](https://mvnrepository.com/artifact/org.shredzone.acme4j) and can easily be added to the dependency list of your project. You can also download the jar files [at Codeberg](https://codeberg.org/shred/acme4j/releases/latest).
4545

4646
acme4j-client
4747
: [`acme4j-client`](https://mvnrepository.com/artifact/org.shredzone.acme4j/acme4j-client/latest) is the main module. It contains everything that is required to get certificates for domains.
@@ -70,8 +70,8 @@ Follow our Mastodon feed for release notes and other acme4j related news.
7070

7171
## Contribute
7272

73-
* Fork the [Source code at GitHub](https://github.com/shred/acme4j). Feel free to send pull requests.
74-
* Found a bug? [File a bug report!](https://github.com/shred/acme4j/issues)
73+
* Fork the [Source code at Codeberg](https://codeberg.org/shred/acme4j) or [GitHub](https://github.com/shred/acme4j). Feel free to send pull requests.
74+
* Found a bug? [File a bug report!](https://codeberg.org/shred/acme4j/issues) ([GitHub](https://github.com/shred/acme4j/issues))
7575

7676
## Donate ♥️
7777

src/doc/docs/usage/debugging.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Android does not log SLF4J output by default. To enable debug logging to logcat,
3333

3434
**Do not blindly post debug logs to public bug reports or questions!**
3535

36-
Understanding the debug log output requires some basic knowledge about the [RFC 8555](https://tools.ietf.org/html/rfc8555) protocol. If you need assistance with your problem, don't hesitate to [open an issue](https://github.com/shred/acme4j/issues).
36+
Understanding the debug log output requires some basic knowledge about the [RFC 8555](https://tools.ietf.org/html/rfc8555) protocol. If you need assistance with your problem, don't hesitate to [open an issue](https://codeberg.org/shred/acme4j/issues).
3737

3838
## Example Log Output
3939

src/doc/mkdocs.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ site_name: acme4j
22
site_author: Richard Körber
33
site_url: https://acme4j.shredzone.org
44
site_dir: target/site/
5-
repo_url: https://github.com/shred/acme4j
5+
repo_url: https://codeberg.org/shred/acme4j
66
edit_uri: ''
77
use_directory_urls: false
88
theme:

0 commit comments

Comments
 (0)