serv/mox
1
0
Fork 0
mirror of https://github.com/mjl-/mox.git synced 2024-12-26 16:33:47 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
mox/go.mod

38 lines
1.2 KiB
Modula-2
Raw Normal View History

mox!
2023-01-30 16:27:06 +03:00
module github.com/mjl-/mox
replace packages slog and slices from golang.org/x/exp with stdlib since we are now at go1.21 as minimum.
2024-02-08 16:49:01 +03:00
go 1.21
mox!
2023-01-30 16:27:06 +03:00
require (
update to latest adns with fix for endless loop for incoming corrupt packets
2024-05-09 12:30:42 +03:00
github.com/mjl-/adns v0.0.0-20240509092456-2dc8715bf4af
update dependencies
2024-03-08 11:28:09 +03:00
github.com/mjl-/autocert v0.0.0-20231214125928-31b7400acb05
add debug logging about bstore db schema upgrades bstore was updated to v0.0.6 to add this logging. this simplifies some of the db-handling code in mtastsdb,tlsrptdb,dmarcdb. we now call the package-level Init() and Close() in all tests properly.
2024-05-10 15:44:37 +03:00
github.com/mjl-/bstore v0.0.6
update to latest sconf, for improved error messages for mixed tab/space indenting in config files based on chat with niklas/broitzer
2024-06-10 19:02:47 +03:00
github.com/mjl-/sconf v0.0.7
replace http basic auth for web interfaces with session cookie & csrf-based auth the http basic auth we had was very simple to reason about, and to implement. but it has a major downside: there is no way to logout, browsers keep sending credentials. ideally, browsers themselves would show a button to stop sending credentials. a related downside: the http auth mechanism doesn't indicate for which server paths the credentials are. another downside: the original password is sent to the server with each request. though sending original passwords to web servers seems to be considered normal. our new approach uses session cookies, along with csrf values when we can. the sessions are server-side managed, automatically extended on each use. this makes it easy to invalidate sessions and keeps the frontend simpler (than with long- vs short-term sessions and refreshing). the cookies are httponly, samesite=strict, scoped to the path of the web interface. cookies are set "secure" when set over https. the cookie is set by a successful call to Login. a call to Logout invalidates a session. changing a password invalidates all sessions for a user, but keeps the session with which the password was changed alive. the csrf value is also random, and associated with the session cookie. the csrf must be sent as header for api calls, or as parameter for direct form posts (where we cannot set a custom header). rest-like calls made directly by the browser, e.g. for images, don't have a csrf protection. the csrf value is returned by the Login api call and stored in localstorage. api calls without credentials return code "user:noAuth", and with bad credentials return "user:badAuth". the api client recognizes this and triggers a login. after a login, all auth-failed api calls are automatically retried. only for "user:badAuth" is an error message displayed in the login form (e.g. session expired). in an ideal world, browsers would take care of most session management. a server would indicate authentication is needed (like http basic auth), and the browsers uses trusted ui to request credentials for the server & path. the browser could use safer mechanism than sending original passwords to the server, such as scram, along with a standard way to create sessions. for now, web developers have to do authentication themselves: from showing the login prompt, ensuring the right session/csrf cookies/localstorage/headers/etc are sent with each request. webauthn is a newer way to do authentication, perhaps we'll implement it in the future. though hardware tokens aren't an attractive option for many users, and it may be overkill as long as we still do old-fashioned authentication in smtp & imap where passwords can be sent to the server. for issue #58
2024-01-04 15:10:48 +03:00
github.com/mjl-/sherpa v0.6.7
webadmin: don't show runtime typecheck error for invalid values in dmarc and tls reports several fields in dmarc and tls reports have known string values. we have a Go string type for them. sherpats (through sherpadoc) turns those strings into typescript enums, and sherpats generates runtime-typechecking code (to enforce correct types for incoming json, to prevent failing deeper in the code when we get invalid data (much harder to debug)). the Go not-really-enum types allow other values, and real-world reports have unknown/unspecified/invalid values. this uses the sherpadoc -rename flag to turn those enums into regular untyped strings, so sherpats doesn't generate enum-enforcing runtime type checking code. this required an update to sherpadoc, to properly handling renaming a type to a basic type instead of another named type. for issue #161 by RobSlgm, thanks for reporting!
2024-05-09 16:58:14 +03:00
github.com/mjl-/sherpadoc v0.0.16
mox!
2023-01-30 16:27:06 +03:00
github.com/mjl-/sherpaprom v0.0.2
update to latest sherpats fixing typo in error message, handle absent dmarc "policy override" reason
2024-03-09 17:43:49 +03:00
github.com/mjl-/sherpats v0.0.6
update dependencies
2024-01-05 13:12:24 +03:00
github.com/prometheus/client_golang v1.18.0
new website for www.xmox.nl most content is in markdown files in website/, some is taken out of the repo README and rfc/index.txt. a Go file generates html. static files are kept in a separate repo due to size.
2024-01-10 18:48:53 +03:00
github.com/russross/blackfriday/v2 v2.1.0
update to latest bbolt with two changes, both not resulting in different behaviour for us.
2024-05-09 11:31:34 +03:00
go.etcd.io/bbolt v1.3.10
update to latest golang.org/x dependencies
2024-04-28 14:53:37 +03:00
golang.org/x/crypto v0.22.0
golang.org/x/exp v0.0.0-20240416160154-fe59bbe5cc7f
golang.org/x/net v0.24.0
update dependencies
2023-11-09 23:19:51 +03:00
golang.org/x/text v0.14.0
make setting up apple mail clients easier by providing .mobileconfig device management profiles including showing a qr code to easily get the file on iphones. the profile is currently in the "account" page. idea by x8x in issue #65
2023-09-23 13:05:40 +03:00
rsc.io/qr v0.2.0
mox!
2023-01-30 16:27:06 +03:00
)
require (
github.com/beorn7/perks v1.0.1 // indirect
update latest prometheus client dependency and its dependencies
2023-11-09 23:43:47 +03:00
github.com/cespare/xxhash/v2 v2.2.0 // indirect
update to latest github.com/prometheus/common to drop dependency on github.com/golang/protobuf
2023-12-14 16:05:50 +03:00
github.com/matttproud/golang_protobuf_extensions/v2 v2.0.0 // indirect
add comment about the sconf config file format at the top of the config files hopefully this helps admins editing the file and prevent mistakes about config files. for issue #56 by kikoreis, thanks!
2023-09-21 09:59:10 +03:00
github.com/mjl-/xfmt v0.0.2 // indirect
update dependencies
2024-01-05 13:12:24 +03:00
github.com/prometheus/client_model v0.5.0 // indirect
update to latest github.com/prometheus/common to drop dependency on github.com/golang/protobuf
2023-12-14 16:05:50 +03:00
github.com/prometheus/common v0.45.0 // indirect
update dependencies
2024-01-05 13:12:24 +03:00
github.com/prometheus/procfs v0.12.0 // indirect
update to latest golang.org/x dependencies
2024-04-28 14:53:37 +03:00
golang.org/x/mod v0.17.0 // indirect
golang.org/x/sync v0.7.0 // indirect
golang.org/x/sys v0.19.0 // indirect
golang.org/x/tools v0.20.0 // indirect
update latest prometheus client dependency and its dependencies
2023-11-09 23:43:47 +03:00
google.golang.org/protobuf v1.31.0 // indirect
mox!
2023-01-30 16:27:06 +03:00
)
Reference in a new issue Copy permalink