deidei

> reports that said the app will require a confirmation of identity, such as a driver’s license, your tax records to prove income and a signed form that says you are ready to get married.

Not sure why someone would sign up for a dating app that is this invasive

yes, it is a typo from the independent.

> Its driving my insane.

Off topic, but you made another typo here lol

> The Royal Navy seems to advertise all levels of jobs on LinkedIn - and wider.

Wasn't aware of this. Can you please link to some more similar job ads? Is this the standard in other militaries too?

Based on what I know there is a roster of eligible candidates with the required experience in most countries. One of them is promoted from there to fill in the vacancy. I've never seen an ad for a post like this before.

> why would it be bad to advertise the position?

Not an expert but from what I understand a position of this level should ideally be filled internally by reassigning or promoting a officer that is already serving. These posts are really important and need someone with decades of experience in the navy. It is terrible if they cannot find someone internally.

Congrats to the team at ISRO!

It makes me wonder, what is it that ISRO does differently than most other government agencies in India that makes them so efficient.

There you go https://archive.ph/fmQR9

Sorry I should probably have put the non-paywalled link in the submission

This is exactly what I was looking for! Thank you so much for the help.

>If your user can provide an encryption key, he can as well provide the token or whatever directly.

Yeah that makes sense, thanks for pointing that out. I'm just brainstorming at this point and will consult a security person before going to prod. Thanks for your pointers!

I was checking out the docs for that and a few other similar solutions too. This is very true. Most of the secret managers are primarily intended for config-like data.

Thanks for the help. So that two options that I was thinking about -

Option A 1. My user creates an secure (with API keys or some other method) API endpoint to provide the Client secrets when I need them.

2. When my app needs to access the client secrets, I maker an API call to the users endpoint to get the Client Secret.

Option B 1. 1. When user signs up, generate an encryption key and ask the user to save it securely. (With the warning that in case this key is lost, the user would have to configure the Client Secrets again)

2. Whenever the user makes an API call (over HTTPS ofc) that involves reading/writing sensitive data, require him to provide the encryption key as well.

Which one is better?

>What are you going to do to keep the key safe in the scenarios of your threat model where an adversary can access the DB contents?

One option that I have been thinking is - 1. When user signs up, generate an encryption key and ask the user to save it securely. (With the warning that in case this key is lost, the user would have to configure the Client Secrets again) 2. Whenever the user makes an API call that involves reading/writing sensitive data, require him to provide the encryption key as well.

Here I won't store any encryption key on the server side and only the user will be able to decrypt the data.

I'm using PostgreSQL and it has a built in encryption library (pgcrypto), so I'll probably use that.

That does make sense, thanks. Do you store all the secrets using the Key Vault?

It would be better to store all the Client Secrets in such a Secrets Manager right? Or should I create an encryption key per user and store that in the Secrets Manager?

Hey, thanks for the reply. My application is a SaaS that helps developers add integrations (with apps like Slack, Linear etc.) to their apps really quick. What is the best way to securely store Client Secrets, Api Keys and Access tokens? Please let me know if you know of any external services too that can help with this.

Thanks for the reply. I'm fully aware of the dangers of rolling my own and want to avoid it at all costs. Is using a battle-tested Node.js library or the database's own API for encryption also dangerous?

>Specific answers to your questions will depend on your application and use cases (local network? global website? credit card data? health data? etc...)

Thank you so much for the reply! My application is a SaaS that helps developers add integrations (with apps like Slack, Linear etc.) to their apps really quick. The kind of sensitive data is Client Secrets and Access Tokens.