Does anybody know how this was done and what the secret was?
755 karma · joined October 30, 2011
Does anybody know how this was done and what the secret was?
http://help.fogcreek.com/10706/future-of-for-your-server-faq
Very sad
http://help.fogcreek.com/fogbugz-release-notes
And now just recently there was a little bit of activity, like that they now offer a VM of some kind with the new version. But I think we can't use that because it is the expensive, unlimited user license and they must install it somehow and plugins would still be gone, which we depend on.
And for all of this there is little to no communication.
The stop of "Kiln for your Server" was also done extremely quitely.
Am I the only one who uses and likes click to play for flash? Great way to block clipboard hijacks. And now there is no click to play for html5-clipboard API.
There must be a user prompt before a website captures a hover, mousover or EVEN CLICK and decides to overwrite the current code, mail or whatever valuable thing I currently have in my clipboard with advertising links!
If multiple processes load the same DLL and the default location happens to be chosen well and there is virtual address space in every process, then the linker can simply share the DLL.
That's how I think it was before ASLR came around.
I think Windows removes the writeable-flag again after relocating.
For the area I described (Mono's JIT vs. Mono's ahead of time compilation as PIC .so-file) I personally don't care that much for ASLR, because it's a managed language and because of specific circumstances of that project.
It looks really terrible to lose one precious register and have all this PIC overhead.
I don't use mono's ahead of time compilation because it also creates PIC. The JIT has one register more available. But I haven't measured it yet
"First of all, I do not feel good about a form on the FSA that you have to sign assuring that you can’t even discuss the test with your parents. I am not comfortable signing something like this. I have the right to talk to my parents about any and everything related to school and my education."
He presents the code in the style of a tool assisted run, typing it in in high speed. I never saw templates used like that to create the unrolled CPU dispatcher
Nowadays I use my Thinkpad without Synaptics or trackpoint drivers and the middle button works perfectly: Either using it open links in new tabs, or pressing it to start scroll mode. Now the mouse pointer changes and moving it scrolls. Unfortunately some software breaks this, probably WPF
And I agree 100% with you!
It seems to me that the focus on security by isolating every webpage from each other went to far recently. When I started with Chrome I think they used to limit the maximum amount of render processes much more. Of course if there was a serious security hole in e.g. webkit/blink then one tab could have stolen data from another tab more easily. But it consumed much less memory
Currently they inject the header with an ID which changes e.g. daily and charge third parties to associate the ID with a profile. They can only inject in HTTP.
If instead the third party (e.g. an adserver) contacts a Verizon server with the IP (and port number in case of carrier grade NAT) on every request and that server gives back the profile and Verizon charges the adserver for this, then nobody would ever know and there would be not much protection against it (without a third party proxy or vpn to hide the IP).
Therefore it is a bad idea to not provide a fallback. It's good if every login over the internet is proteceted by HTTPS and weak fallbacks are not used. But there are places where security is just irrelevant (like my localhost scenario, or legacy hardware in a trusted local network), where I'd rather have a way of doing a connection with any way possible, no matter how insecure. Old ciphers, old SSL, compatibility hacks etc.
I wish they would keep that code arount and make it possible to connect anyway
We use FogBugz, hosted in house (can't have our data out in the open for several reasons) and with some custom plugins to integrate with other in house systems like serial number lookup. I recently learnt that they most likely kind of cancelled that codebase too, but did not tell anybody. They just stopped to provide updates and also removed the excellent and powerful ability for plugins with the "performance update" enabled (instead they but popular plugins directly in their code):
http://help.fogcreek.com/fogbugz-release-notes http://help.fogcreek.com/7562/fogbugz-plugins
The only info I can find on the future of FogBugz is here:
http://stackoverflow.com/questions/19543512/is-kiln-for-your...
A VM is not really a solution for me for several reasons, especially if plugins are gone and our own will not work. I can only speculate, but it really looks that way. (They send newsletters to customers and announced the "performance update", but never talked about how and when this would come to "FogBugz for your Server")
I wish they were able keep the version for your server with plugins and without VM around.