528 karma · joined February 3, 2011
How come you aren't bothered? I ask because I can't image apart from:
a. I use short or cryptically unsafe passphrases,
b. I use passphrases and type them easily,
c. I only need to log in a few times.
Am I forgetting others?
The only (somewhat big) downside to this, and related unix pw managers is the sheer lack of browser compatibility - mobile would also be nice, as that's one of the places where it's a PITA to use and enter long passphrases.
pass claims to have both, but doesn't:
https://github.com/jvenant/passff#readme does not work.
The iOS app has disappeared from github: https://github.com/rephorm/pass-ios#readme
It's solvable problems, I just find it a somewhat important part of a password manager.
I didn't know there was a 10.10.3 patch - I never said there wasn't. OP said there wasn't, I said it remains to be shown. You're more than welcome to correct me on that.
I don't understand what my patch sentence has to do with whining - or how that is whining about the HN crowd?
It's still unclear what was unwanted about my original comment, so I can't really correct my behavior (which was what I wanted all along).
> Apple appears to be in no rush to fix the first one, I wouldn't bet my money on this vulnerability getting a fix any time soon, either ...
As it was clearly stated, there is a fix. Whether or not they'll release a 10.10 patch remains to be shown, and "no rush" is speculation.
I'll never understand the HN crowd, but I guess providing additional information to clear up a false statement, while correcting OPs assumptions is against the rules.
But start the mac hate train regardless - if facts don't count :)
Perhabs someone with experience on large complex applications can share some insights?
Otherwise, I pity the FB employees who gets assigned to this project. "Here you go, fix that button, here's 18k files to digest".
Surely they must've decoupled it into oblivion in order to have a class that manages "just that", so
1. new employee can work in an "isolated" context (although he really isn't)
2. can locate where to write and debug in this complex codebase.
apt-get install git
pacman -Sy git
emerge --ask dev-vcs/git
yum install gitThe isolation provided by Docker is not as robust as the segregation established by hypervisors for virtual machines.
As seen with CVE-2015-3629[0] for instance.
The other points: patch level and docker management isn't understood, seem to be people problems which can easily be corrected.
[0]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3629
Force-TLS and HTTP Nowhere does what you describe.
Lately I've been looking at pass[0], do any of you have experience running this (with git)?
I get that you can write a program which compiles language X to machine code, e.g. how python interpreting Go to write the assembly necessary would be technically possible.
My question is, how is the compiler generated? If it's written in c, gcc -o compiler, but what is the piece I'm missing when it comes to Go compiles a Go compiler -- or is this still done as "here's the machine code, now compile the Go runtime"?
I suppose my question is a similie to "the chicken or the egg?".
> by not fsync'ing each operation (though one can configure ES to do so).
It may not be default, but we've seen, again and again, how people are influenced by what they read about a database (e.g. MongoDB).
The lesson by now should be: always know your DB.
But, you know, salestext is useless :)
Thanks for the info.
user@host ~/tmp # npm install -g git-stats
/usr/local/bin/git-stats -> /usr/local/lib/node_modules/git-stats/bin/git-stats
git-stats@1.1.0 /usr/local/lib/node_modules/git-stats ├── ul@1.1.0
├── ansi-parser@1.4.0 ├── cli-box@2.1.1 (ansi-parser@1.3.0)
├── moment@2.9.0 ├── git-stats-colors@1.0.0 (couleurs@3.0.0)
└── bug-killer@1.0.0 (couleurs@1.1.0) user@host ~/tmp # npm install -g git-stats-importer /usr/local/bin/git-stats-importer -> /usr/local/lib/node_modules/git-stats-importer/bin/git-stats-importer
git-stats-importer@1.3.0 /usr/local/lib/node_modules/git-stats-importer ├── gry@1.0.0
├── async@0.9.0 ├── oargv@1.2.0 (ul@1.1.0)
├── bug-killer@1.0.0 (couleurs@1.1.0) └── git-stats@1.1.0 (ul@1.1.0, ansi-parser@1.4.0, git-stats-colors@1.0.0, cli-box@2.1.1, moment@2.9.0)
user@host ~/tmp # git clone https://github.com/IonicaBizau/git-stats
Cloning into 'git-stats'... remote: Counting objects: 414, done.
remote: Total 414 (delta 0), reused 0 (delta 0) Receiving objects: 100% (414/414), 47.08 KiB | 0 bytes/s, done.
Resolving deltas: 100% (189/189), done. Checking connectivity... done.
user@host ~/tmp : cd git-stats
user@host ~/tmp/git-stats # git-stats-importer
info Done.
user@host ~/tmp/git-stats # git stats
╔════════════════════════════════════════════════════════════════════════════════════════════════════════════════╗
║ Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb ║
║Sun ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ║
║Mon ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ║
║Tue ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ║
║Wed ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ║
║Thu ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ║
║Fri ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ║
║Sat ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ║
║-------------------------------------------------------------------------------------------------------------- ║
║Contributions in the last year: 0 | Longest Streak: 0 days | Current Streak: 0 days | Max a day: 0 ║
╚════════════════════════════════════════════════════════════════════════════════════════════════════════════════╝
user@host ~/tmp/git-stats # cat $HOME/.git-stats
{}On a serious note: it's nice to see ALNP being used in HTTP/2
Really sad to see it go. Now we'll have to find another solution, e.g. migrate to Neo4j, although we rely heavily on the scalability of Titan DB.
I guess now is the time to test Neo4j's cluster performance.
Any other alternatives out there?
Albeit "defeated" is a strong word considering the RSA encryption is still intact - and thus only able to decrypt files larger than, and in range starting from, 1024 bytes.
It recovers potentially large portions, but if your file format can not function without a working header, you're out of luck.