Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Stéphan Kochen
@stephank
I guess the PR is still a better implementation of the ICANN TLD list. And we should still add the fetch & refresh code just for that. (Plus it adds allow/block lists)
But I kinda wanted to do a DNS check any way, so don't think the public suffix list adds much.
onli
@onli
sounds right, it should not be needed if we can confirm the domain exists before sending the email
The last time the problem was that the DNS lookup could not be made async?
Stéphan Kochen
@stephank
Think so, yes. Plus we need to do both MX and A lookups, which we can't do using OS facilities, I think. So I was thinking about adding an explicit resolver option, which enables the DNS check with explanation.
Stéphan Kochen
@stephank
I don't understand why PRs aren't built by github actions. Tried tweaking the workflow, but still not working. :/
PRs from outside of the org, that is
Stéphan Kochen
@stephank
Every now and then I see outlook.com fail our DMARC rules. I assume this is legit bad actors trying to send mail from portier.io, but I'm not sure if someone has an account there and can maybe do a quick check to see if https://demo.portier.io works?
Dylan Staley
@dstaley
@stephank no issues using my outlook.com email
onli
@onli
@stephank I let someone test it with hotmail.com and that worked as well
Stéphan Kochen
@stephank
Awesome, thanks! Guess it's nothing to worry about then. :)
colemickens
@colemickens:matrix.org
[m]
hello from the Matrix side
onli
@onli
Hey Matrixside
Stéphan Kochen
@stephank
Bleh, it looks like cargo cache is getting corrupted on macOS CI. I fixed it once for #227, but now it's broken again on master. Considering we should just disable cache. :/
onli
@onli
maybe something we can keep local only, .gitignore it?
onli
@onli
ah, ok
Dylan Staley
@dstaley:matrix.org
[m]
I think the issue can be fixed by using gnu-tar. actions/cache#403
It's going to be added to the macOS images in a few weeks
colemickens:matrix.org @colemickens:matrix.org waves at Dylan
Stéphan Kochen
@stephank
Oh, good catch! Will try that now
Stéphan Kochen
@stephank
Two consecutive builds went well, so looks good. :)
Bleh, we also need to figure out why Safari tests are timing out 50% of the time :/
jestarray
@jestarray
can portier be used for applications outside the web? i was thinking of using it to authenticate users for my game made in rust. I presume all I would need to do is to make a post request to the brokers /auth path?
Dylan Staley
@dstaley:matrix.org
[m]
Yup! Just make sure to set your Accept header to json so it doesn't serve redirects and HTML.
Stéphan Kochen
@stephank
I sneaky pushed this: portier/public-infra@54b6ab8
But it appears that was the correct fix for our automated testing, which is now all green the past three days: https://server.portier.io/stats.jsonl
(We should visualise that somewhere)
I was worried it was an issue with broker key rotation, because I'm also debugging an issue in one of our products, but now also suspect something rp-side there.
Stéphan Kochen
@stephank
Can't figure out why the Redis connection is suddenly failing in E2E tests, though: https://github.com/portier/portier-broker/pull/233/checks?check_run_id=2054522504 😕
Stéphan Kochen
@stephank
Oh, it was silly. It was trying localhost ipv6 first, and we don't fallback to other resolver results, plus Docker only does ipv4. :/
Stéphan Kochen
@stephank
now the release job doesn't trigger :/
Not sure if that's related to me using the new release script and the gh command-line, but just used web to recreate the tag, and that's fine.
Stéphan Kochen
@stephank
onli
@onli
yeah, a release :)
Stéphan Kochen
@stephank
I'm seeing issues with Redis and the new release :/
thread 'tokio-runtime-worker' panicked at 'Failed to read from Redis: parse error: Parse error at 1
Unexpected `117`
Unexpected `10`
', src/utils/redis/pubsub.rs:167:33
But only after a short while. Not sure what's going on here.
I may investigate later, don't have the time for it right now. Perhaps finally upgrading to a tokio v1 stack will simply solve it, but there's a bit of work there.
onli
@onli
The heroku installation is still the old version, no?
Stéphan Kochen
@stephank
We don't use heroku anymore, but only staging is autodeployed from master. We need to update portier/public-infra manually to deploy to production. Plus I think that uses SQLite.
onli
@onli
Oi, of course. Old state tends to stay in the head...
Stéphan Kochen
@stephank
Fix appears to working for us, so I created 0.3.5: https://github.com/portier/portier-broker/releases/tag/v0.3.5
Stéphan Kochen
@stephank
Seems we never upgraded our server to NixOS 20.09. Going to give that a shot!
Stéphan Kochen
@stephank
All done, looks to be working fine. Will also try upgrading the production broker from 0.3.2 -> 0.3.5 later (not today).
Specifically wanted to upgrade because of the OpenSSL security release just now, and I think NixOS 20.03 was EOL already. :o
Plus, NixOS 20.09 hardened the nginx install, which is nice.
jestarray
@jestarray
are there any good self hosted versions of mailgun/postmark?
jestarray
@jestarray
also does anyone recommend what lightweight rust(or C libraries) to make a post request to the portier server for authentication?
Stéphan Kochen
@stephank
@jestarray Mailgun/Postmark have fairly specific APIs; I’m not aware of any reimplementations. But you can use any SMTP server with Portier, so Postfix, Exim, etc all work. Running a mailserver is almost its own profession, though. 😅
It’d be cool if we could extract the Rust client code from the Portier broker itself into a separate crate, but right now, we don’t have any Rust or C client libraries, unfortunately.