pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feed[pgjdbc/pgjdbc] issue #3349: SSL connection is not established
31+ messages / 4 participants
[nested] [flat]
* [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-19 10:53 "Shalaka1197 (@Shalaka1197)" <[email protected]>
0 siblings, 0 replies; 31+ messages in thread
From: Shalaka1197 (@Shalaka1197) @ 2024-08-19 10:53 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
I am getting below exception when I am trying to connect to postgres using ssl. I am connecting by using root.crt file and verify-full mode.
`Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors, at java.base/sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:369), at java.base/sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:275), at java.base/sun.security.validator.Validator.validate(Validator.java:264), at java.base/sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:231), at java.base/sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:132), at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.checkServerCerts(CertificateMessage.java:1341), ... 84 common frames omittedCaused by: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors, at java.base/sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:157), at java.base/sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:83), at java.base/java.security.cert.CertPathValidator.validate(CertPathValidator.java:309), at java.base/sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:364), ... 89 common frames omitted`
@davecramer Please let me know what can be the issue ?
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-19 14:03 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2024-08-19 14:03 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
did you follow https://jdbc.postgresql.org/documentation/ssl/
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-20 05:06 "Shalaka1197 (@Shalaka1197)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: Shalaka1197 (@Shalaka1197) @ 2024-08-20 05:06 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer Please see below parameters used.
SSL =true ;
SSL_MODE= verify-full;
SSL_RESPONSE_TIMEOUT =5000;
SSL_ROOT_CERT = root crt path
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-20 09:05 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2024-08-20 09:05 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Hi @Shalaka1197
If you are doing verify full then you also need the client certificates.
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-21 08:17 "Shalaka1197 (@Shalaka1197)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: Shalaka1197 (@Shalaka1197) @ 2024-08-21 08:17 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer in which mode root.crt file verification is done ?
In the documentation this is not specified point - "verify full then you also need the client certificates"
https://jdbc.postgresql.org/documentation/ssl/
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-21 14:53 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2024-08-21 14:53 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
The server `root.crt` will be verified on every SSL connection
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-22 19:31 "Shalaka1197 (@Shalaka1197)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: Shalaka1197 (@Shalaka1197) @ 2024-08-22 19:31 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Is there any test cases for expired root.crt server.crt files ?
How is it validated from postgres end ? @davecramer
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-22 19:31 "Shalaka1197 (@Shalaka1197)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: Shalaka1197 (@Shalaka1197) @ 2024-08-22 19:31 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer How to check the connection is made with ssl or without ssl in postgres ?
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-22 19:51 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2024-08-22 19:51 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
install the sslinfo contrib module https://www.postgresql.org/docs/current/sslinfo.html#SSLINFO
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-23 05:06 "Shalaka1197 (@Shalaka1197)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: Shalaka1197 (@Shalaka1197) @ 2024-08-23 05:06 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer for checking the validity of server and root certificate is there any use case or test case ?
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-23 10:41 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2024-08-23 10:41 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
You can just use openssl to verify your certs
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-23 12:54 "Shalaka1197 (@Shalaka1197)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: Shalaka1197 (@Shalaka1197) @ 2024-08-23 12:54 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer From postgres code is there any mechanism to check certificate expiry for root.crt file and client.crt files ?
It is connecting for expired certificates as well.
Its seems to be bug from postgres side.
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-23 14:52 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2024-08-23 14:52 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
https://www.enterprisedb.com/blog/authentication-ssl-client-certificates#:~:text=If%20the%20authenti....
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-29 03:59 "Shalaka1197 (@Shalaka1197)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: Shalaka1197 (@Shalaka1197) @ 2024-08-29 03:59 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer Please see below use case of mine.
I am trying to connect with the postgres via one way tls protocol(only root.crt file verified).
so from postgres server side we have configured the server.crt file and root.crt file and its path is given under the postgresql.conf file.
Now I am trying to connect to server application via root.crt file from client application. The below is code snippet.
`
SSL =true ;
SSL_MODE= verify-ca;
SSL_RESPONSE_TIMEOUT =5000;
SSL_ROOT_CERT = /tmp/server.crt
`
for ssl root cert parameter we are passing server.crt as it is giving the issues when I passed root.crt file. It is able to connect via client application as well using server.crt file.
Now for negative test case scenario, I have created server.crt file with 1 day expiry and passed the same file in ssl_root_cert parameter , after one day the certificate is expired for server.crt file .
From psql command part below is the error we got.
**PSQL error for expired server.crt file - certificate verification failed.
java application - its able to connect via expired server.crt file**
Now I am given root.crt file for ssl_root_cert parameter and got the below error.
`
Caused by: java.security.cert.CertificateExpiredException: NotAfter: Fri Aug 23 11:44:37 UTC 2024, at java.base/sun.security.x509.CertificateValidity.valid(CertificateValidity.java:277)
, at java.base/sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:627)
, at java.base/sun.security.provider.certpath.BasicChecker.verifyValidity(BasicChecker.java:190)
, at java.base/sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:144)
`
Now please tell me why server.crt file is able to connect via postgres even its certificate is expired ?
root.crt file is giving error and server.crt file also should throw the same error right ?
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-29 11:35 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2024-08-29 11:35 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
I would be happy to look into this for you.
Please provide detailed instructions on how to replicate your problem
Cheers,
Dave
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-30 06:27 "Shalaka1197 (@Shalaka1197)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: Shalaka1197 (@Shalaka1197) @ 2024-08-30 06:27 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer
When you are creating root.crt and server.crt file , try to create it with 0 days validity.
for example command :
`
openssl req -new -x509 -days 0 -nodes -text -out server.crt -keyout server.key -subj "/CN=localhost"
`
and put both the certificates in postgres server.
Below is sample code for replicating the issue.
ssl: true
sslmode:verify-ca
sslrootcert: resources/server.crt
public class ConnectDB {
private final String url = "jdbc:postgresql://abcd:5432/postgres?" +
"sslmode=verify-ca&sslrootcert=resources/server.crt";
private final String user = "postgres";
private final String password = "abcd";
public Connection connect() {
Connection conn = null;
try {
conn = DriverManager.getConnection(url, user, password);
System.out.println("Connected to the PostgreSQL server successfully.");
} catch (SQLException e) {
System.out.println(e.getMessage());
}
return conn;
}
public static void main(String[] args) {
ConnectDB db = new ConnectDB();
db.connect();
}
`
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-30 12:31 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2024-08-30 12:31 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Thanks, I was able to replicate this issue.
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-30 16:44 "Shalaka1197 (@Shalaka1197)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: Shalaka1197 (@Shalaka1197) @ 2024-08-30 16:44 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer Looking for support from postgres end for this issue.
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-08-31 11:35 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2024-08-31 11:35 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@Shalaka1197 I don't think this is a server issue.
Turns out that java doesn't check the end date of the certificate
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-09-02 11:18 "Shalaka1197 (@Shalaka1197)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: Shalaka1197 (@Shalaka1197) @ 2024-09-02 11:18 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer But for root.crt file its checking validity and throwing certificate error. Why is it not happening server.crt file ?
For java its doesn't check validity do you have any reference links for the same ?
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-09-02 11:47 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2024-09-02 11:47 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
https://security.stackexchange.com/questions/105637/does-trustmanager-pkix-or-rfc-3280-x-509-really-...
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-09-03 05:30 "Shalaka1197 (@Shalaka1197)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: Shalaka1197 (@Shalaka1197) @ 2024-09-03 05:30 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer How is it checking expiry for root.crt files and throwing below exception ? Why is it not applicable for server.crt file ?
`Caused by: java.security.cert.CertificateExpiredException: NotAfter: Fri Aug 23 11:44:37 UTC 2024, at java.base/sun.security.x509.CertificateValidity.valid(CertificateValidity.java:277) , at java.base/sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:627) , at java.base/sun.security.provider.certpath.BasicChecker.verifyValidity(BasicChecker.java:190) , at java.base/sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:144)`
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-09-03 11:27 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2024-09-03 11:27 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
I am on vacation and will be back next week.
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2024-11-04 08:18 "kaushalaroraharman (@kaushalaroraharman)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: kaushalaroraharman (@kaushalaroraharman) @ 2024-11-04 08:18 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer Any update on this issue?
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2025-05-08 07:25 "kaushalaroraharman (@kaushalaroraharman)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: kaushalaroraharman (@kaushalaroraharman) @ 2025-05-08 07:25 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
We are still facing this issue. Please provide an update on when this can be resolved.
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2025-05-08 10:31 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2025-05-08 10:31 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@kaushalaroraharman I don't have any updates. Can you remind me what exactly the issue is ?
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2025-05-08 11:13 "kaushalaroraharman (@kaushalaroraharman)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: kaushalaroraharman (@kaushalaroraharman) @ 2025-05-08 11:13 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer A brief of the issue is that even with an expired certificate, client is able to connect to Postgres. The expectation is that with an expired certificate, connection should be refused.
Please go through https://github.com/pgjdbc/pgjdbc/issues/3349#issuecomment-2320206340, the previous comments and description for details on the issue.
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2025-05-08 11:29 "davecramer (@davecramer)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: davecramer (@davecramer) @ 2025-05-08 11:29 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
As I mentioned previously the default trustmanager does not check the expiry date https://security.stackexchange.com/questions/105637/does-trustmanager-pkix-or-rfc-3280-x-509-really-...
If you want to enforce it you may want to implement a different trustmanager
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2025-05-08 12:06 "kaushalaroraharman (@kaushalaroraharman)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: kaushalaroraharman (@kaushalaroraharman) @ 2025-05-08 12:06 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer Yes, I have went through this. But the question remains, how it is working when root certificate is expired? The same which was also highlighted under [comment#](https://github.com/pgjdbc/pgjdbc/issues/3349#issuecomment-2325634390). Can you please share some inputs on this?
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2025-05-09 14:58 "sehrope (@sehrope)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: sehrope (@sehrope) @ 2025-05-09 14:58 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
It works when the certificate is expired because the default TrustManager used to validate the certificate does not check the certificate expiration. It only checks if server's certificate matches or is signed by the `root.crt`.
This is due to the implementations of TrustManager not including that check in their default validation. That's part of the JDK classes, it's not specific to this driver, and . It's possible that could change in the future, but I doubt it will ever happen as it would break a lot of legacy applications.
The rationale for this is because once you've added a certificate to the trust store, it is assumed that you trust it. The trust store itself does not subsequently check if the certificate is expired or invalidated. That is supposed to happen at a higher level prior to creation of the trust store. For a long running application there's the additional complexity of the application "breaking" after it has been online.
We could consider adding such an "is expired" check to the PGJDBC driver's `LibPQFactory` (the default that performs most TLS validation) when it reads the certificates from `root.crt`, however I think it'd have to be optional / opt-in. Changing that default to reject expired certificates would definitely break existing application, in particular the legacy ones that would be more likely to have such expired certificates.
In the meantime if you want to ensure that expired certificates are rejected, you can create your own SSLSocketFactory that clones the behavior in `LibPQFactory` with the extra expiration check by invoking [`checkValidity()`](https://docs.oracle.com/javase/8/docs/api/java/security/cert/X509Certificate.html#checkValidity--) on each certificate before as it is [added to the list](https://github.com/pgjdbc/pgjdbc/blob/d9e20874590f59543c39a99b824e09344f00a813/pgjdbc/src/main/java/...).
^ permalink raw reply [nested|flat] 31+ messages in thread
* Re: [pgjdbc/pgjdbc] issue #3349: SSL connection is not established
@ 2025-05-09 19:03 "kaushalaroraharman (@kaushalaroraharman)" <[email protected]>
29 siblings, 0 replies; 31+ messages in thread
From: kaushalaroraharman (@kaushalaroraharman) @ 2025-05-09 19:03 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@sehrope Thank you for sharing the detailed explanation. It helped me understand the cause of the issue clearly. I will look into the custom SSLSocketFactory as suggested.
^ permalink raw reply [nested|flat] 31+ messages in thread
end of thread, other threads:[~2025-05-09 19:03 UTC | newest]
Thread overview: 31+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-08-19 10:53 [pgjdbc/pgjdbc] issue #3349: SSL connection is not established "Shalaka1197 (@Shalaka1197)" <[email protected]>
2024-08-19 14:03 ` "davecramer (@davecramer)" <[email protected]>
2024-08-20 05:06 ` "Shalaka1197 (@Shalaka1197)" <[email protected]>
2024-08-20 09:05 ` "davecramer (@davecramer)" <[email protected]>
2024-08-21 08:17 ` "Shalaka1197 (@Shalaka1197)" <[email protected]>
2024-08-21 14:53 ` "davecramer (@davecramer)" <[email protected]>
2024-08-22 19:31 ` "Shalaka1197 (@Shalaka1197)" <[email protected]>
2024-08-22 19:31 ` "Shalaka1197 (@Shalaka1197)" <[email protected]>
2024-08-22 19:51 ` "davecramer (@davecramer)" <[email protected]>
2024-08-23 05:06 ` "Shalaka1197 (@Shalaka1197)" <[email protected]>
2024-08-23 10:41 ` "davecramer (@davecramer)" <[email protected]>
2024-08-23 12:54 ` "Shalaka1197 (@Shalaka1197)" <[email protected]>
2024-08-23 14:52 ` "davecramer (@davecramer)" <[email protected]>
2024-08-29 03:59 ` "Shalaka1197 (@Shalaka1197)" <[email protected]>
2024-08-29 11:35 ` "davecramer (@davecramer)" <[email protected]>
2024-08-30 06:27 ` "Shalaka1197 (@Shalaka1197)" <[email protected]>
2024-08-30 12:31 ` "davecramer (@davecramer)" <[email protected]>
2024-08-30 16:44 ` "Shalaka1197 (@Shalaka1197)" <[email protected]>
2024-08-31 11:35 ` "davecramer (@davecramer)" <[email protected]>
2024-09-02 11:18 ` "Shalaka1197 (@Shalaka1197)" <[email protected]>
2024-09-02 11:47 ` "davecramer (@davecramer)" <[email protected]>
2024-09-03 05:30 ` "Shalaka1197 (@Shalaka1197)" <[email protected]>
2024-09-03 11:27 ` "davecramer (@davecramer)" <[email protected]>
2024-11-04 08:18 ` "kaushalaroraharman (@kaushalaroraharman)" <[email protected]>
2025-05-08 07:25 ` "kaushalaroraharman (@kaushalaroraharman)" <[email protected]>
2025-05-08 10:31 ` "davecramer (@davecramer)" <[email protected]>
2025-05-08 11:13 ` "kaushalaroraharman (@kaushalaroraharman)" <[email protected]>
2025-05-08 11:29 ` "davecramer (@davecramer)" <[email protected]>
2025-05-08 12:06 ` "kaushalaroraharman (@kaushalaroraharman)" <[email protected]>
2025-05-09 14:58 ` "sehrope (@sehrope)" <[email protected]>
2025-05-09 19:03 ` "kaushalaroraharman (@kaushalaroraharman)" <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox