We learn something new every day. This is a community dedicated to informing each other and helping to spread knowledge.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rule 1- All posts must begin with TIL. Linking to a source of info is optional, but highly recommended as it helps to spark discussion.
** Posts must be about an actual fact that you have learned, but it doesn't matter if you learned it today. See Rule 6 for all exceptions.**
Rule 2- Your post subject cannot be illegal or NSFW material.
Your post subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Posts and comments which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding non-TIL posts.
Provided it is about the community itself, you may post non-TIL posts using the [META] tag on your post title.
Rule 7- You can't harass or disturb other members.
If you vocally harass or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
For further explanation, clarification and feedback about this rule, you may follow this link.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Unless included in our Whitelist for Bots, your bot will not be allowed to participate in this community. To have your bot whitelisted, please contact the moderators for a short review.
You can view our partnered communities list by following this link. To partner with our community and be included, you are free to message the moderators or comment on a pinned post.
For inquiry on becoming a moderator of this community, you may comment on the pinned post of the time, or simply shoot a message to the current moderators.
pass --generate -c
Or just use your password manager. Where you save that password.
gasp what??
Your password manager does this too!
That's fucked up, they should not do that. Even if they do it in a way that users are actually secure (maybe generating the password in the browser, nothing serverside?), it isn't good to train people to trust a website for this.
$ Openssl rand 16 | base64
today I learned. Thanks :)
No thank you, KeepAssXC for me!
hunter2
All I see is *******.
correct horse battery staple
This seems like one picked up data packet away from being a bad idea. Am I overthinking this?
This is probably ok. First of all, they're probably actually doing it in Javascript in the browser. It probably never travels over the network at all. And, if it did, with HTTPS it would be hard to intercept and decrypt except by a government or something.
But, it still gives me the willies to generate a password on a web page. Fundamentally a web browser is still a tool for sending and receiving data over the Internet, and that's not the kind of tool I'd want to be generating something that I don't want other people to know or see.
What happens if there's a bug? If the password is being generated in an app on my local system a badly designed app with a bug could maybe log my newly generated password in a local log file somewhere. If there's a bug in DuckDuckGo's javascript, who knows where that newly generated password might be logged?
With https as protocol, picked up data packets won't do much harm.
But relying on anything but a local password manager is imho still a bad idea.
This is probably fine. The connection to DDG will be over HTTPS, so a captured packet would need to be decoded first. And if someone were to manage to break the encryption, then they would also need to know what service you used the password for.
Ultimately, it's more secure to generate locally, but it would be a huge amount of work to get anything usable out of a packet capture
Are they sending data? I'm pretty sure this will just be generated on the client.
Yeah, I tested it. It's not a client side thing, it is part of the search page output.
oof
You are not overthinking it. Exploiting this would be a bit more complex than capturing a packet on the wire, but it is possible.
If you intend to use a passphrase for anything important, it's best to generate it locally.
Yeah I think I'll just click an icon in my password manager instead.
I like the little tools like this that DuckDuckGo has. A couple others:
my favorite is "qr code" best and easiest qr code generator
I like this as most qr generator websites make a link shortener kind of thing and put ads before my content.
If you're going to auto generate passwords, just use BitWarden.
If you're going to use a password vault, use one you host yourself and not someone else's service.
The difference in complexity in setting up bitwarden and using your own self-hosted instance of bitwarden is fucking massive. For 99.9% of people rhem using bitwarden would greatly improve their password security and bitwarden has proven to be better than the competition.
FYI Vaultwarden is simpler and should be easier to self-host
Would love to set up Vaultwarden, but I trust my own skills in hardening a server less than Bitwardens
I don't even trust my server skills enough to open my jellyfin to the internet.
Lol, no. I don't trust myselft to keep it well maintained, up to date, nor available when it matters most.
Most people can not host it. Of those who can, many shouldn't host it, for their own safety.
That isn't great from a security perspective
$ pwgen -s -1 32
You can also just use "random password x" with x being a number. What I use more often is "random uuid" which I hope is self explanatory.
Fun fact: You can generate a random UUID in your web browser without needing to visit a website. Just open your browser console and type crypto.randomUUID()
Stop putting crypto into everything!
(/jk)
Or just use a locally hosted password generator for one that isn't handfed to you by a for-profit company...
Ok but you should use passphrases. Better to type and remember in case you need to
There are instances where sites prevent copy-paste, or you are on another machine without your password manager available
If you have a password vault, use the vault first.
For rotating PC login credentials, I use codified passphrases. They typically meet security needs, are unique and nearly unguessable because it could be ANYTHING in your office, and don't contain dictionary words. Example:
Annual evaluations are due before summer. Be sure to mention the Grodsky project! aeadB4S.Bs2mtGp.
Where did Julie's candy go? I ate it! She'll never know >:D
WdJcg?I8i!Snn>:D
Even if I had a perfectly secure connection, I'm still getting a password from a service that could be tracking me.
Alternatively, you can just roll your face on the keyboard and then take a screenshot of the resulting password to save it. 🤷♂️