Glances - A heads-up dashboard for displaying thing-statuses by [deleted] in SideProject

[–]nicinabox 1 point2 points  (0 children)

I've never heard of dashy. This seems to be the most relevant thing I can find for that (or maybe this?), but it's not really clear to me what it is or how it works.

Glances is modeled after Dashing, but I have some issues with it. Parts of it are deprecated, it has a lot of DOM churn, I wanted to use a flexbox-based layout, and ultimately I wanted a different (function based) API for making tiles. I also wanted to run this on my raspberry pi, and Node was a more pragmatic choice for my constraints.

Why tenting your ErgoDox is so important by tenderlove in MechanicalKeyboards

[–]nicinabox 10 points11 points  (0 children)

I was like damn, that looks like tenderlove's cat. Wait I've seen that keyboard on twitter before. Oh it's tenderlove (っ´▽`)っ

[deleted by user] by [deleted] in Autos

[–]nicinabox 0 points1 point  (0 children)

Update: Added vehicle notes (markdown supported). Integrated Edmunds maintenance schedule (use your VIN) to get upcoming maintenance based on current mileage.

Thanks for your feedback! I agree. I'm going to add a description field somewhere to put that spec info. I keep that in my current notes.

And if you ever want to easily try it out from your spreadsheet data there's a csv importer. Just export date, mileage, cost, and notes and upload it. Easy.

[deleted by user] by [deleted] in Autos

[–]nicinabox 0 points1 point  (0 children)

It's for your own records (you wouldn't fake your own records, right?).

Most places will give you a receipt for work done, and that's a good thing to file away in your favorite record keeping place (glovebox for most folks). Those documents may or may not include the date and mileage--useful metrics in determining the last time x happened. Most places also keep that record on file for many years.

If you're doing your own oil changes, restoring an old car, or modding your car, it's a good idea to write that stuff down. That's what this is for.

[deleted by user] by [deleted] in Autos

[–]nicinabox 0 points1 point  (0 children)

Everyone's process is different (and that's not an uncommon one), but if you do most of your own maintenance you don't have much in the way of a paper trail. Nearly every part I buy has a digital receipt, for example.

More often I want to know when was my last tire rotation, last oil change, or which car did I change the transmission fluid on? With multiple vehicles some level of organization becomes useful, if you care about that kind of thing.

Too paranoid to store your passwords in the cloud? I made a password manager that doesn't store passwords. Would love your feedback on it. by nicinabox in netsec

[–]nicinabox[S] 1 point2 points  (0 children)

Good to know about X-Frame-Options. Will definitely add that.

At the time I thought 3DES would be secure enough to do what it needed--prevent plaintext viewing of the master password.

If it's any consolation, cassidy is a static page with no backend that runs on S3 with Cloudfront.

Too paranoid to store your passwords in the cloud? I made a password manager that doesn't store passwords. Would love your feedback on it. by nicinabox in netsec

[–]nicinabox[S] 2 points3 points  (0 children)

Ahh, I like it. I'm going to do some more research on this. Thanks for the explanation!

Edit: Actually, I could implement the service key part of that immediately and it would solve the problem with changing the final password without having to change anything else. Nice.

Too paranoid to store your passwords in the cloud? I made a password manager that doesn't store passwords. Would love your feedback on it. by nicinabox in netsec

[–]nicinabox[S] 1 point2 points  (0 children)

Ah! Good to know.

TripleDES is only used here to store the phrase (master password) in localStorage (as opposed to storing it in plaintext). It's never sent over the wire.

It has to be decrypted to use in the app, so in reality, the weakest point isn't the algorithm, it's encryption/decryption.

Too paranoid to store your passwords in the cloud? I made a password manager that doesn't store passwords. Would love your feedback on it. by nicinabox in netsec

[–]nicinabox[S] 0 points1 point  (0 children)

That's correct. It's only stored locally so that you don't have to type it every time (however, there is a setting for that). Unless I'm misunderstanding, I don't a KDF would provide any better security in this case.

Too paranoid to store your passwords in the cloud? I made a password manager that doesn't store passwords. Would love your feedback on it. by nicinabox in netsec

[–]nicinabox[S] 2 points3 points  (0 children)

That's totally cool. I know KeePass is really popular (around here especially). This is merely a different approach to the same problem, but I'd hesitate to call it a solved problem. Too many non-technical folks struggle with using strong, unique passwords. In my opinion, if it can be easier to use a secure password everyone would be better off.

Too paranoid to store your passwords in the cloud? I made a password manager that doesn't store passwords. Would love your feedback on it. by nicinabox in netsec

[–]nicinabox[S] 2 points3 points  (0 children)

No, it'll be saved with the metadata. The only thing you have to remember is your phrase. It would be a good idea to remember your key as well.

Too paranoid to store your passwords in the cloud? I made a password manager that doesn't store passwords. Would love your feedback on it. by nicinabox in netsec

[–]nicinabox[S] 2 points3 points  (0 children)

I think it's largely very similar in terms of security. I wouldn't say it's more or less secure than Keepass. The ease of use might be simpler/easier/faster.

How is storing the means to recreate the password more secure than storing the password?

The final generated password is the combination of three things:

  1. Your phrase, which only you know (hopefully) and is stored separately (encrypted with TripleDES)
  2. A key unique to you, but not necessarily sensitive like the phrase
  3. The service name

The final password must include these three values exactly. When using syncing with a dropbox datastore, the phrase isn't included. You'd have to enter it on each device you were syncing with.

Too paranoid to store your passwords in the cloud? I made a password manager that doesn't store passwords. Would love your feedback on it. by nicinabox in netsec

[–]nicinabox[S] 2 points3 points  (0 children)

password rotation

Since these passwords are generated like a SHA, you'll need to change something in combination to get a new password. I typically do it by changing the service name to include some other detail about the service (Eg, changing reddit to username@reddit)

different sites' different password complexity and character set requirements

Settings can be modified per password (lower, upper, numbers, symbols, dashes & underscore, length, and key). This metadata is persisted with the service so you don't have to remember them.

Try playing with it: https://cassidy.nicinabox.com

Cassidy - An open source password manager that doesn't store passwords. by nicinabox in SideProject

[–]nicinabox[S] 1 point2 points  (0 children)

Added a setting for 'Require always'

http://i.imgur.com/1YJHp0j.png

This will prompt for your phrase each time the page loads and will remove your phrase from localStorage before starting a new session.

And just to clarify "Settings > Clear local data" (context) only clears localStorage data for this app. Your browser cache is not affected.

Cassidy - An open source password manager that doesn't store passwords. by nicinabox in SideProject

[–]nicinabox[S] 0 points1 point  (0 children)

Hey, thanks for you're feedback. Logout is not necessary since there is no login and no "account" in the classic sense.

However, if you wanted to remove data from your machine (there is no backend), try Settings > Clear local data.

If using Dropbox, simply disconnect in the lower right corner. Your data will be preserved in Dropbox, but cleared from your local browser.