Could you please provide more info on this topic, e.g. a link? I intended to buy EV code signing certificate as a sole proprietor to fix long-standing problem with my software when Windows Defender pops up every time I release a new version. Is EV code signing certificate no longer a viable solution to this problem? Is there no longer a difference between EV and non-EV code signing certificate?
After Microsoft's March 2024 update, EV Code signing certs don't offer instant Microsoft Defender reputation. Now, OV and EV both code signing certificates can be installed and stored on FIPS 140 Level 2 or Common Criteria EAL 4+ certified HSM, tokens, or cloud HSMs. So, you can consider EV Code Signing as higher security and higher validation with no more difference. If u want to buy code signing at affordable cost, I recommend: https://signmycode.com/cheap-code-signing-certificates
This remind me of when everybody and his dog was shoehorning blockchain into everything. Blockchain-based pet platforms, pet owners earning tokens for participating in community, pet care services fueled by smart contracts, and the like.
Both GNU assembler and LLVM integrate assembler parse and match instructions only once.
hey then store an internal representation in memory and perform fixed-point iteration.
The section/fragment representation gives a lot of flexibility.
In contrast, nasm parses and matches instructions multiple times depending on the optimization level. It also assigns addresses during parsing and uses an ad-hoc method for JMP/JCC instructions. The end conditions of the fixed-point iteration algorithm (global_offset_changed and stall_count) seem unconventional.
-O0 does not "relax all" short jumps to near jumps.
My idea of getting one step ahead of similar backdoors is to wrap sshd traffic into a spiped tunnel. Spiped is compiled from source and linked statically (last stable version from 2021).
I still want sshd updated by my OS package manager. Statically linked spiped, which is out of scope of my OS package manager, is just a second line of defense.
There's no Win 9x phase in Win XP setup, of course. :) There's optional DOS phase, then text-mode phase (running NT kernel under the hood, but UI is in VGA text mode), and then finally GUI phase of the setup.
Problem 5 has a simpler geometric solution, it's enough to plot circle of radius sqrt(2) on the Oab plane and a few lines b=-a, b=-a+1, b=-a+2, b=-a-1, b=-a-2 to observe the intersections. The rest of the lines are too far from this circle to intersect with it.
Did Mozilla really came from Godzilla? I've always thought it was short form of 'Mosaic killa' (Mosaic killer). Original code of NSCA Mosaic was licensed by Microsoft Corp from Spyglass, Inc. (and so become a part of first version of Internet Explorer); while team which had written this code (Marc Andreessen et al) got venture funding from James Clark et al in 1994 to form Netscape Communications Corp and basically rewrite the browser from scratch. I.e. initial goal of that team was to kill NSCA Mosaic, their previous creation, hence the name.
> Mozilla Foundation – from the name of the web browser that preceded Netscape Navigator. When Marc Andreessen, co-founder of Netscape, created a browser to replace the Mosaic browser, it was internally named Mozilla (Mosaic-Killer, Godzilla) by Jamie Zawinski.[110]
Does GDI/non-GDI distinction really matter if the only job for GDI is to blit already rendered framebuffer after Skia library (up-to-date part of browser) to the hardware? I.e. when GDI is actually not exposed to the fonts and vector graphics downloaded from the web, just pixels? To me it seems highly unlikely that GDI can be exploited via colors of pixels.
An interesting compilation of buzzwords of that time. Ultimately, almost none of them stuck to the walls. I wonder if today's AI hype will look the same in 27 years?
> I wonder if today's AI hype will look the same in 27 years?
If the AI hype from 37 years ago is any indication (fuzzy logic on lisp machines, anyone?): Yeah. 99% of the buzzwords will be dropped because they're empty, and the remaining 1% useful ideas will vanish into the background and see continued use under new names, because they won't be sexy enough any more to be called AI.
My first year of computer science (or any university course) was in 1997. I had used a Commodore 64, Sinclair ZX81, etc in the 80s, then a break in Junior High and High School, and for several years after that, and gotten back into computers as a hobby in the mid-90s. For health reasons, I could no longer work as a cook, had been learning C from K&R's book to make it easier to build ray tracing animations, and decided to go to university for it (I had some money saved up by virtue of having no free time or social life).
I sat down a to a Sun workstation that was described as a "thin client". This was slicker than my Linux system at home (which I mostly ran as a terminal using Lynx or something to browse the web) and featured the Sun browser and blinding fast Internet. Since I was using dial up at home, this was pretty intense.
Yes, I believed the future was thin clients, web browsers for everything, and that hyper-connected devices were just around the corner. It seemed totally reasonable to me that every system would be like a Chromebook. You sit down, login, and your "system" is waiting for you just as you left it the last time you used it whether it was here, or across the world. I also imagined this experience working on your watch (I imagined a bigger watch - we had watches that you could watch TV on in the 80's - a kid in my school had one) or on what I imagined were inevitable table-top and wall sized monitors that I assumed would be ubiquitous in 10 years (surface hub comes to mind).
So this was a popular vision and one that is kind of realized today although not all the way and not quite in the way "we" (people I was reading, talking to, and hoping to become) imagined.
So today we have Google accounts suspended by corporate bots (on the grounds mostly based on output of /dev/urandom), and I wonder (looking at the sales pitch of these ideas in 1997): are we NUI yet? And if yes, can we have our GUI back please?
Frankly, idea of mainframe is much older, and never really appealed to me. I prefer a kind PCs where P is for 'personal'.
> I sat down a to a Sun workstation that was described as a "thin client". This was slicker than my Linux system at home (which I mostly ran as a terminal using Lynx or something to browse the web) and featured the Sun browser
I don't think so, that thing was dog slow due to its Java based OS and I can't associate it in any way with the word 'slick' ;)
Sun workstations without disks were also often used as thin clients. It was quite simple to boot them from the network and use an NFS root or use them as a graphical terminal.
I've switched away from FastSpring in 2021, when they outsourced their payouts to Hyperwallet (for me this change meant double currency exchange USD -> EUR -> USD with associated double exchange fees). It looks like FastSpring rolled further downhill since then. This reminds me of Plimus/Bluesnap collapse: when this kind of company runs of cash, its tends to establish various funny fees before finally flipping up.
