stable-point
Joined 10 years ago
Karma
123
Submissions
29
Member since
Jul 19
Recent submissions
Comment · 9 years ago
Perhaps SO could include the titles of questions marked as duplicate somewhere in the markup so that Google indexes it?
Comment · 9 years ago
I think this highlights that while there are easy solutions to the problem the OP faced, they're difficult for a newcomer to discover. (I have been using Rust for a couple of months and I'd also have reached for serde and maybe serde_derive to solve the problem).
Hopefully this is something the Libz Blitz[0] will solve with their Rust Cookbook[1]. (You could almost but not quite arrive at as simple a solution from chapters 1 and 2).
Comment · 9 years ago
I think the key part is "regardless of where they come from". For instance, Scotland has free tuition for the Scottish and other EU citizens, but not for citizens of England/Wales/NI or international students. (The fees for an English person are typically cheaper than other English universities, but still not to be sniffed at).
I am not sure about NI or Wales, but I imagine there's a similar situation.
Comment · 9 years ago
I do the same, as do others on my team. If we see an XXX in code-review, then we know someone commited something they didn't mean to.
Comment · 9 years ago
The firmware signature ensures the updates are authentic, but not that they are fresh. An attacker could force devices to stay on an older authentic but vulnerable piece of software.
The Google Omaha design docs discuss this a little bit: https://github.com/google/omaha/blob/master/doc/cup.html
I think plain HTTP is not appropriate for most update schemes Interestingly, Google Omaha actually chose not to use TLS to ensure freshness, but has something custom.
Comment · 9 years ago
Arguably someone adhering to the C++ Core Guidelines, using GSL and using the new static analysis tools (currently only in VS?) can be reasonably confident about choosing C++ for a new project in 2017.
Comment · 9 years ago
The article asks an interesting question which casts doubt on this theory: why does the UK ban affect UK airlines too?
Comment · 9 years ago
I don't imagine many start-ups buy them new. My previous employer bought a bunch of Aeron chairs second-hand (from other failed start-ups...)
Comment · 9 years ago
Fantastic. Maybe hide the word "MSDN" somewhere in the page, just for search engines. Old habits die hard. :)
Slightly off-topic, but would it be possible to reinstate the code samples on the IIS Native Module section[0]? It seemed to go walkies about a year ago and no amount of "Is this page helpful?" feedback seems to get it back. It's quite important because there is little documentation elsewhere on the internet.
[0] https://msdn.microsoft.com/en-us/library/ms693629(v=vs.90).a...
Comment · 9 years ago
Fantastic! Thanks a lot in any case.
I do find the image of "fighting the borrow checker" is quite harmful to how people view Rust. As those links state, an important aspect of teaching Rust is educating people about why the borrow checker complains, so that they might adjust their mental model.
Comment · 9 years ago
The new content looks a lot better, but I think it is a shame that this is not using the "MSDN" branding. One of the nicest things about Microsoft documentation is that I can add the term "MSDN" to any random web search and usually get the page I'm after.
Comment · 9 years ago
Could you provide an example where the borrowing would cause issues for immutable data?
I'm still learning Rust, but I thought the fact that you could have as many immutable borrows as possible would limit what errors the borrow checker could throw at you.
Comment · 9 years ago
It is not written in Python, it is written in RPython:
> So this is written in Python? > It's actually written in RPython, the same language PyPy is written in. make build_with_jit will compile Pixie using the PyPy toolchain. After some time, it will produce an executable called pixie-vm. This executable is a full blown native interpreter with a JIT, GC, etc. So yes, the guts are written in RPython, just like the guts of most lisp interpreters are written in C. At runtime the only thing that is interpreted is the Pixie bytecode, that is until the JIT kicks in...
Comment · 9 years ago
Opening it in a text editor is not sufficient. With clever use of 'sleep' you can even have the server return a malicious payload only if it thinks its getting immediately piped to sh[0].
If you're opening it in a browser to check, you've also got to worry that the server may be looking at curl's user agent to decide whether to serve up a malicious payload[1].
[0] https://www.idontplaydarts.com/2016/04/detecting-curl-pipe-b... [1] https://jordaneldredge.com/blog/one-way-curl-pipe-sh-install...
Comment · 10 years ago
No, he doesn't:
> For request, a full rewrite made sense because urllib sucked so much and we had no good alternatives.