acidictadpole

> The CVE has been discovered by a security researcher/firm, rather than being found in the wild.

The researcher/firm was the one that disclosed it, but I don't feel like you could conclusively say that the exploit isn't in the wild.

It's less controversial but also not really relevant. Those kinds of reminders shouldn't be using cookies, and don't need to.

One of my university courses offered an opportunity for a project like this and I did it with some classmates.

We started by altering the ssh daemon to disallow all logins over this ssh daemon and to log all the usernames and passwords attempted. After a week we gathered thousands of attempts to brute force into the honeypot. Interestingly enough, the passwords used were a combination of the very commonly used ones but also ones that were clearly from other popped boxes.

After a week or so of this we altered the ssh daemon again. This time it would log all attempts but also grant access on the 3rd attempt no matter what the credentials were. The few bots that managed to get in all tried to install various rootkits on the machine, all of which where targeted at a different distro of Linux than we were using so it mostly just busted up our shells output.

It was a long time ago but a great experience.

Something that I do:

`set -o vi` and then hit `<ESC>`. You now have vim motion-like controls to navigate on the command line:

- `b` goes back a word.

- `w` goes forward a word.

- `0` goes to the beginning of the line.

- `$` goes to the end of the line.

etc.

I put `set -o vi` in my rc file so I have it on by default.

Second this. ITerm2 is the only console emulator that I actually enjoy using. I've been flip-flopping on terminals on windows and linux constantly.

Is `match` a reserved word in C#? I don't use it that much, but have used scala and F# pattern matching and they all use the term `match`, which seems more intuitive.

It depends what you want to do. FS2020 is not going to likely have any kind of combat in it.

I fly both FS2020 alpha and DCS World fairly regularly, obviously the former a lot more in the past little bit. If you'd like help with anything DCS world I'd be more than happy to help out.

The author does seem to concede that hitting all the checkmarks in an attack on git would be pretty tricky:

> An attacker would not just have to do that, though; this new version would have to contain the desired hostile code, still function as a working floppy driver, and not look like an obfuscated C code contest entry

The whole idea is that they want to switch away before these things become likely. They are unlikely now, but SHA-1 is only getting weaker as time goes by and more research is done.

Does this actually save much time? I thought it was the throw mechanic that was slow, rather than just creating the exception?

You could, but that's technically against the law (circumventing DRM).

You shouldn't have to break the law to protect your privacy.

I'm wondering if this person on twitter had any kind of usage-data opt-out that was on their kindle and they just hadn't opted out. I haven't looked at my kindle's settings in a long while, but I'll take a look when I get home tonight.

You're absolutely right. I didn't think about it like that, thanks.

Ah. The old classic Rudy.

That's really cool. Though it does seem to remove almost 50% of the benefits listed in this entry, but those seem to be focused on fuel-consuming vehicles rather than bikes.

What does the EFF have to do with this? Are they related to the FSF somehow?

Because it turns from "Microsoft has nothing to lose by doing this" to "Microsoft is going to lose a bunch of money spending time negotiating with and paying third parties to be allowed to release their libraries with windows' source code".

People's time isn't free.

If you know there'll only be one concrete implementation, then yeah don't bother.

What people sometimes forget though is that any implementations of this in your tests are also concrete.

Some things like a DB accessor, will use a mocked/lite implementation in testing for code that doesn't need access to the db (but still needs to be provided data) to test it's functionality.

I've been in the workforce for nearly 10 years and I still have this issue when starting a new project.

It takes a conscious effort to just move forward, and it still leaves a lingering thought in my mind about what I'm doing wrong while building exactly what I need.

From someone interested in learning more functional programming, could you provide a bit more detail about what each book provides?