An SMTP relay could make a copy of your emails before they even reach your inbox. Lack of TLS support on the sender side and the context goes clear text through relays. Encryption remains the best way to guarantee against eavesdropping.
>Lack of TLS support on the sender side and the context goes clear text through relays. Encryption remains the best way to guarantee against eavesdropping.
TLS support only provides a mechanism for encryption across the wires. If your email is stored unencrypted anywhere except your own physical hardware (and sometimes not even then), whoever owns that hardware can (and the likes of Google actually does) read/modify/delete any or all of your emails at their whim.
At some point when the number of boxes and number of cronjobs become too high, I suggest looking at Rundeck as a central scheduler (not affiliated with PagerDuty, I actually work for a competiting company) or something similar.
Also, you want to make sure your job has been running. I've used a selfhosted instance of healthchecks.io in order to warn me if something has not run.
I live in the French speaking part of Belgium and have configured all my devices in English for the past 15+ years.
Apparently Google consider that if you are geo IP located in Belgium with your devices in English, you _have to be_ a Dutch speaker. While I would agree that French speaking Belgians are in majority using French UIs, there are exceptions. Please respect my browser settings!
The solution? I have to put French in my browser accepted languages (not necessarily first) and then Google understand I'm not a Dutch speaker and will stick to English.
For me it's often the other way around... system language is English but where possible (e.g. browser) I indicate Dutch/Flemish can also be used. Still, many websites seem to think that they should default to their French version despite my settings and even geo IP putting me in the non-French part...
I wish they would stop guessing and just listen to the hints...
I live in France, speak French, but work with English as my primary language.
So, I had to make the same settings change, otherwise google would keep putting French searches before English ones (despite the fact that I searched with English keywords).
I don't remember how I found this, but it might something along the lines of "I'm really annoyed today, let's fix this NOW". When you speak 2 languages or more, and they don't match with your location, Google, Microsoft, and most other big tech companies go completely nuts. So, you get used to fiddling with languages settings.
I have no idea how we got there, but my guess is that most Google engineers are either : completely ignorant of internationalization issues, don't care, or don't speak more than one language.
PS: Speech recognition, autocorrect, and mobile keyboards : Same problem.
This is why I think Google assistant is absolutely useless. Try to call someone who has a name in X language on a device that is set to English. You just can't. I love Big tech circle jerk about diversity, that somehow stops at skincolor, gender and sexual identity. You happens to bilingual? Sorry our cutting edge AI can't handle that.
Google all I want is a command for assistant, for example "OK Google, Call *in german/dutch/French/etc* <after this command everything will be interpreted on the given language, for the rest of the voice input>. See, it's not that hard.
> Google all I want is a command for assistant, for example "OK Google, Call in german/dutch/French/etc <after this command everything will be interpreted on the given language, for the rest of the voice input>. See, it's not that hard.
I had the exact same idea, it seems Google really lack good product design.
> I have no idea how we got there, but my guess is that most Google engineers are either : completely ignorant of internationalization issues, don't care, or don't speak more than one language.
Funny, if anything probably 80%+ of the eng folks in Europe for big tech speak more than one language (everyone who's not from UK or Ireland).
I think they discovered the trick. Default headers might be ignored, but anything non default (e.g. en-gb, two languages, etc.) is assumed to be correct.
If you are interested, these are two of the bugs that I filed on the subject. I might triage them again sometime, but if you are interested in ensuring that your code hasn't been affected you might want to look at them:
I see Fastmail as the good guys. Why are they targeted like that lately? If the attackers think that I'm going to move back to Gmail, they are wrong. I'm with you, Fastmail team.
Looks like it squarely competes with FreeIPA. Maybe main differentiator is that FreIPA is in python whereas this is in rust (and so less prone to bugs)?
Is it a widely held concept that Rust is less prone to bugs compared to Python? I've only heard it being compared to C, and only wrt. memory safety bugs.
Rust is statically typed and doesn't have null returns, so it's got advantages for correctness, but the big win with Rust vs. Python would be performance, not security.
There's a lot more checks and balances built into rust as a language, so the foot-gun opportunities are less likely - which makes it rather suitable for reliable systems programming.
And getting back to this particular case... kanidm is fast AND reliable. There's a lot of testing going on comparing it to 389 DS.
Yes, I write a fair bit of Rust. I'm just saying: between Python and Rust, there isn't that much of a security difference (you could nitpick things like deserialization in Python, but really the significant security win of Rust is not having memory corruption flaws, which Python has never really had.)
