Microsoft patents Sudo


Recommended Posts

Lordy, lordy, lordy. They have no shame. It appears that Microsoft has just patented sudo, a personalized version of it.

Here it is, patent number 7617530. Thanks, USPTO, for giving Microsoft, which is already a monopoly, a monopoly on something that's been in use since 1980 and wasn't invented by Microsoft. Here's Wikipedia's description of sudo, which you can meaningfully compare to Microsoft's description of its "invention".

This is why what the US Supreme Court does about software patents means so much. Hopefully they will address the topic in their decision on Bilski. Sudo is an integral part of the functioning of GNU/Linux systems, and you use it in Mac OSX also. Maybe the Supreme Court doesn't know that, and maybe the USPTO didn't realize it. But do you believe Microsoft knows it?

Perhaps Microsoft would like everyone in the world to pay them a toll at least, even if they don't want to use Microsoft's software? Like SCO, but with more muscle behind the request? Or maybe it might be used as a barrier to competition? What do you personally believe Microsoft wants patents on things like sudo for? To make sure innovative new companies can compete on an even playing field with Microsoft?

Source: Groklaw

Woah, what? :no:

Link to comment
https://www.neowin.net/forum/topic/844776-microsoft-patents-sudo/
Share on other sites

"Systems and/or methods are described that enable a user to elevate his or her rights. In one embodiment, these systems and/or methods present a user interface identifying an account having a right to permit a task in response to the task being prohibited based on a user's current account not having that right."

Nope, sounds like straight up sudo to me.

It says they've patented a personalized version of sudo, and not the actual command in of itself. Isn't there a difference?

They've basically patented the concept of rights elevation. The patent is even titled "Rights elevator" and the abstract describes something that's exactly like Sudo.

I don't think sudo is graphical or automated, is it? The patent specifies:

cause the computing device to perform acts comprising: determining multiple accounts capable of permitting a task not permitted by an account of a current user wherein the determining is based on criteria comprising: frequency of use; association with the current user; and indication of sufficient but not unlimited rights; receiving indicators for the multiple accounts capable of permitting the task; presenting a graphical user interface, the graphical user interface having: multiple account regions, each account region identifying one of the multiple accounts capable of permitting the task; an authenticator region capable of receiving an authenticator for one of the multiple accounts capable of permitting the task; receiving, through the graphical user interface, the authenticator for one of the multiple accounts capable of permitting the task; and responsive to receiving the authenticator for one of the accounts capable of permitting the task, packaging, into a computer-readable package, the received authenticator and the account capable of permitting the task associated with the authenticator, the package effective to enable authentication of the account capable of permitting the task.

While it's similar to other authentication, this patent specifies automatically finding accounts that have the appropriate privileges to use and presenting them as options.

I thought the people who write Groklaw could read, but apparently not. This is a knee-jerk anti-Microsoft reaction. The patent is not for sudo, it is for a GUI that automatically presents a list of users that have the required rights so that the user doesn't have to remember and type it manually (something you need to do with sudo, which isn't a GUI, although it's sometimes configured to automatically substitute only root and given a graphical frontend). In fact, the patent application makes a large amount of references to sudo.

As for whether Microsoft intends to sue the entire world, like the article believes, I doubt it. All big companies have thousands upon thousands of patents like this, and they are intended primarily to prevent other people from suing them. Microsoft is a major target, and thus are going to use the patent system this way and attempt to patent anything they can think of. Business as usual. If this came as a shock to anyone, then sorry, but you are completely clueless as to how the world works.

I thought the people who write Groklaw could read, but apparently not. This is a knee-jerk anti-Microsoft reaction. The patent is not for sudo, it is for a GUI that automatically presents a list of users that have the required rights so that the user doesn't have to remember and type it manually (something you need to do with sudo, which isn't a GUI, although it's sometimes configured to automatically substitute only root and given a graphical frontend). In fact, the patent application makes a large amount of references to sudo.

As for whether Microsoft intends to sue the entire world, like the article believes, I doubt it. All big companies have thousands upon thousands of patents like this, and they are intended primarily to prevent other people from suing them. Microsoft is a major target, and thus are going to use the patent system this way and attempt to patent anything they can think of. Business as usual. If this came as a shock to anyone, then sorry, but you are completely clueless as to how the world works.

This comes to a surprise? Groklaw is trash and appeals to asinine zealots.

I don't think sudo is graphical or automated, is it?
gksudo is graphical, and comes up when necessary for elevation.
The patent specifies:

<snipped quote>

While it's similar to other authentication, this patent specifies automatically finding accounts that have the appropriate privileges to use and presenting them as options.

Yes, that is the difference here. Microsoft is providing a list of people that have the authorization to elevate.

Not sure if that is a small security liability, as any unprivileged user can now get a list of account names with elevated privileges. But it does sound convenient. I guess trading a bit of security for convenience is what's going on with this.

But I agree that it is an "enhancement" that is getting the patent, not the sudo concept.

They've basically patented the concept of rights elevation. The patent is even titled "Rights elevator" and the abstract describes something that's exactly like Sudo.

You can't patent a concept, Microsoft just patented one possible implementation of a "sudo" like utility. Nothing wrong with that.

Microsoft at its best. Let's just hope the US patents law doesn't back this one up. Shame on these people. :no:

I don't see a problem with this one. The patent is only for a specific type of elevation, one that also lists the users with the required permissions.

As for whether Microsoft intends to sue the entire world, like the article believes, I doubt it. All big companies have thousands upon thousands of patents like this, and they are intended primarily to prevent other people from suing them. Microsoft is a major target, and thus are going to use the patent system this way and attempt to patent anything they can think of. Business as usual. If this came as a shock to anyone, then sorry, but you are completely clueless as to how the world works.

True, until they sell those same patents to patent trolls to create problems in the open source community. Wouldn't be anything new coming from Microsoft, the company that is holding back software development and the progress of societies.

True, until they sell those same patents to patent trolls to create problems in the open source community. Wouldn't be anything new coming from Microsoft, the company that is holding back software development and the progress of societies.

Overreacting much?

Hasnt microsoft had the runas command for a while?

Also why must people search for things to attack microsoft on. They are not patenting the general elevating a users rights. They are patenting their way of doing it.

I am getting tired of these microsoft witch hunts. Especially when they have no real basis.

I don't see a problem with this one. The patent is only for a specific type of elevation, one that also lists the users with the required permissions.

There's no significant difference between what Microsoft is trying to patent and the sudo authentication. We're not talking about the command that is used in UNIX here, nor the graphical interface for it, but the process and method that is used. Microsoft is trying to patent all of that and justifies it by including a graphical interface that lists a number of users.

How many times have we seen this? Copy something then develop and add new features. Finally patent it.

ICQ/AIM - MSN messenger

Netscape - Internet Explorer

(...)

There's no significant difference between what Microsoft is trying to patent and the sudo authentication. We're not talking about the command that is used in UNIX here, nor the graphical interface for it, but the process and method that is used. Microsoft is trying to patent all of that and justifies it by including a graphical interface that lists a number of users.

How many times have we seen this? Copy something then develop and add new features. Finally patent it.

ICQ/AIM - MSN messenger

Netscape - Internet Explorer

(...)

Microsoft is patenting their way of doing it . If we go by what you just said then linux shouldnt have any patents on say anything that resembles a window because xerox would hold all the patents. If we go buy what you say then any OS should not be able to patent anything resembling a mouse and pointer also since xerox would hold alll the patents.

Considering windows works differently then linux whats wrong with them patenting how to do it inside windows? Since windows and linux are different in their code and how they do things why is this bad?

Hasnt microsoft had the runas command for a while?

Run as isn't quite the same, as I understand it (not a big Windows user here, so I may be wrong). But a user can try to run a program as a normal user, and get a gksudo graphical prompt to elevate. I think run as can only be initiated ahead of program execution.

There's no significant difference between what Microsoft is trying to patent and the sudo authentication.

The way patents work, is on a specific implementation of a process. When they specified the alternate user listing, then that entirety is what is patented. Any implementation that does not show that listing as described is non-infringing.

Sudo was first conceived and implemented by Bob Coggeshall and Cliff Spencer around 1980 at the Department of Computer Science at SUNY/Buffalo. It ran on a VAX-11/750 running 4.1BSD. An updated version, credited to Phil Betchel, Cliff Spencer, Gretchen Phillips, John LoVerso and Don Gworek, was posted to the net.sources Usenet newsgroup in December of 1985.

In the Summer of 1986, Garth Snyder released an enhanced version of sudo. For the next 5 years, sudo was fed and watered by a handful of folks at CU-Boulder, including Bob Coggeshall, Bob Manchek, and Trent Hein.

In 1991, Dave Hieb and Jeff Nieusma wrote a new version of sudo with an enhanced sudoers format under contract to a consulting firm called "The Root Group". This version was later released under the GNU public license.

In 1994, after maintaining sudo informally within CU-Boulder for some time, Todd Miller made a public release of "CU sudo" (version 1.3) with bug fixes and support for more operating systems. The "CU" was added to differentiate it from the "official" version from "The Root Group".

In 1995, a new parser for the sudoers file was contributed by Chris Jepeway. The new parser was a proper grammar (unlike the old one) and could work with both sudo and visudo (previously they had slightly different parsers).

In 1996, Todd, who had been maintaining sudo for several years in his spare time, moved distribution of sudo from a CU-Boulder ftp site to his domain, courtesan.com.

In 1999, the "CU" prefix was dropped from the name since there has been no formal release of sudo from "The Root Group" since 1991 (the original authors now work elsewhere). As of version 1.6, Sudo no longer contains any of the original "Root Group" code and is available under an ISC-style license.

In 2001, the sudo web site, ftp site and mailing lists were moved from courtesan.com to the sudo.ws domain (sudo.org was already taken).

In 2005, Todd rewrote the sudoers parser to better support the features that had been added in the past ten years. This new parser removes some limitations of the previous one, removes ordering constraints and adds support for including multiple sudoers files.

sudo, in its current form, is maintained by:

Todd Miller

Todd continues to enhance sudo and fix bugs.

Maybe one of these guys should have gotten a patent on it. The whole thing is much ado about nothing.

True, until they sell those same patents to patent trolls to create problems in the open source community. Wouldn't be anything new coming from Microsoft, the company that is holding back software development and the progress of societies.

Seeing as millions of businesses turning over trillions of dollars every year use Microsoft software, I don't think somehow that it is holding back the development of society :laugh: but it is a source of amusement to me how you FOSS guys always cry foul over things like this and go on your inane rants about how evil Microsoft are, even though this patent is no real threat to free software due to how specific it is. It wouldn't be possible for them to patent use of the command sudo, or other elevation designs because they have been in use in OSX and Linux for years.

More of you guys should listen to Markjensen, he is one of the few Linux users on here that uses his brain instead of spreading Microsoft FUD everywhere he can go, he appears to understand the issues at play here, it confuses me that you do not.

That's just the default config on most distros, but you can customize the behaviour far beyond that.

As far as I know there is no way to configure sudo to present the user with a list of users with the appropriate rights. Sudo only lets you manually substitute from a pre-defined list of users.

Microsoft at its best. Let's just hope the US patents law doesn't back this one up. Shame on these people. :no:

<insert random company> at its best. The patent has already been granted, and is actually extremely tame compared to other patents out there (including ones owned by both Microsoft and Apple). It's business as usual.

There's no significant difference between what Microsoft is trying to patent and the sudo authentication. We're not talking about the command that is used in UNIX here, nor the graphical interface for it, but the process and method that is used. Microsoft is trying to patent all of that and justifies it by including a graphical interface that lists a number of users.

No, they are patenting only their version that automatically looks up users with the appropriate rights. As far as I know Sudo cannot do this, nor can any frontends for it.

mmmmm why bother patenting it at all? Is it going to damage their buissness model if they don't?

To quote a younger Bill Gates:

"If people had understood how patents would be granted when most of today's ideas were invented, and had taken out patents, the industry would be at a complete standstill today. I feel certain that some large company will patent some obvious thing related to interface, object orientation, algorithm, application extension or other crucial technique. If we assume this company has no need of any of our patents then they have a 17-year right to take as much of our profits as they want. The solution to this is patent exchanges with large companies and patenting as much as we can. "

Maybe one of these guys should have gotten a patent on it. The whole thing is much ado about nothing.

Sudo is referenced several times in the patent papers, so clearly whoever approved the patent is absolutely aware of Sudo's existence, but doesn't consider the two to be the same.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft brings Claude to its own Azure infrastructure, powered by Nvidia GB300 Blackwell by Karthik Mudaliar Anthropic's Claude models are now generally available in Microsoft Foundry on Azure and are running on Nvidia's GB300 Blackwell Ultra systems. Nvidia wrote in its announcement that the models are hosted on Microsoft Azure and accelerated by GB300 Blackwell Ultra GPUs, with Quantum-X800 InfiniBand networking used to support larger agentic systems and specialized sub-agents that can operate across business domains. This is great for customers and enterprises that want to build autonomous and domain-specific AI agents using Claude without moving outside Microsoft’s cloud platform. Microsoft currently offers Claude models in Foundry in two forms: “Hosted on Azure,” which runs end-to-end on Azure infrastructure and is generally available, and “Hosted on Anthropic infrastructure,” which remains in preview. This separation is quite important for organizations that have procurement, compliance, data processing, or internal governance requirements tied to Azure. Anthropic currently has 11 Claude models listed in Microsoft Foundry, including Opus 4.8, Sonnet 4.6, and even the unavailable Mythos and Fable models. Billing is handled through Claude Consumption Units (CCUs). Microsoft says CCU is an invoicing unit for Claude models in Foundry, with token usage converted using Anthropic’s published per-model token rates. The usage is billed through Azure Marketplace just like models from other distributors and appears on the customer's Azure invoice, while eligible spend can count against a Microsoft Azure Consumption Commitment. For starters, GB300 NVL72 is a rack-scale, fully liquid-cooled system that combines 72 Blackwell Ultra GPUs and 36 Grace CPUs. Nvidia has listed 37TB of fast memory, 130TB/s of NVLink bandwidth, and FP4 Tensor Core performance of up to 1,440 petaflops with sparsity. The deal is also part of a three-way partnership between Microsoft, Nvidia, and Anthropic. Under the deal, Anthropic has committed to buying $30 billion in Azure compute capacity and contracting additional capacity up to one gigawatt. Nvidia and Microsoft also said they would invest up to $10 billion and $5 billion in Anthropic, respectively.
    • WhatsApp is getting usernames, and you can reserve your preferred one now by Fiza Ali Sharing your phone number isn't always something you want to do, especially with people you've just met. Whether it's someone from a class, a local community group, or a sports team chat, handing over your number can feel like giving away more personal information than necessary. That's exactly the problem WhatsApp is trying to solve with its upcoming usernames feature. The company has announced that users can now reserve a unique WhatsApp username ahead of the feature's wider rollout later this year. Once usernames become available, they'll let people connect without revealing their phone numbers. It's a change that makes a lot of sense for group chats. Right now, everyone in the group can see your phone number. With usernames enabled, that won't necessarily be the case when someone contacts you for the first time. WhatsApp says it's opening username reservations early because more than three billion people use the app, meaning plenty of people are likely to want the same usernames. Reserving one now gives users a better chance of securing the name they actually want before the feature launches more broadly. If your preferred username is already taken, WhatsApp will also offer a built-in username generator to suggest available alternatives. The feature isn't only aimed at individual users. Creators, businesses, and organisations will be able to claim the same username they already use on Instagram or Facebook, making it easier to keep a consistent identity across Meta's apps. Furthermore, privacy is a big part of how WhatsApp is introducing usernames. There won't be a public directory where people can browse or search for usernames. Instead, people will need to know your exact username before they can start a conversation with you. Additionally, users can also choose to enable a username key, which adds another layer of control by requiring people to enter that key before sending a message. Once the feature rolls out, people who choose to use a username will no longer have their phone number shown when messaging a person or business for the first time. If you want to reserve a username, make sure you're running the latest version of WhatsApp, then head to Settings > Account > Username. The tech giant says usernames will roll out gradually over the coming months, and users will receive an in-app notification when the feature becomes available in their country.
    • When I think about a network, there are really two aspects, the hardware and the wiring. So here is what I would do for both. Wiring: Use Cat6A for the patch panel, outlets, and all structured cables (cables installed in walls). Run plenty of Wireless Access Point (WAP) cables, as a general rule, assume a signal can only pass through 2-3 walls and can't pass through a floor (that is conservative, but trust me on this if you want strong WiFi)  Cat6 patch cables are fine for now if you don't plan to run 10gig, those are easy to replace later if needed. Run OS2 single-mode fiber to anywhere you think you may have a server or sub-switch. (yes, single-mode for everything on a small network, don't mess with multimode unless you are at a scale where that minor cost and power savings will matter). If you really want to future proof, also run fiber to any high density WAP locations, it is likely that WiFi 8 and beyond WAPs will push the limits of 10g. Run 6-12 pairs of single-mode fiber between your MDF and the building's MDF, even if you only need 1 or 2 pairs now, those extra pairs will pay off down the road. Hardware: (its easy to say "get all the features incase you need them", so instead of futureproofing, I am going to take approach of suggesting areas worth investing in, and areas you can save money). Don't overspend thinking you need every feature on every port. You don't need 10g on every port, you don't need PoE on every port. Don't overspend on redundancy either, unless you are ready to buy two of everything, don't waste money buying two of some things and not others. Dual power supplies are worthwhile, but probably not HA or multi-path redundancy.  Get 1 "distribution layer" switch that your router/firewall will connect to as well as all your access layer switches below. This should be a fully managed 10g+ switch with a combination of copper and SPF ports, a few 25g uplink ports are nice for this switch. Given that you said it is a small network, I suggest also using that distribution layer switch for servers and WAPs, meaning it will need PoE. Speaking of wireless, get good professional tri-band WAPs, and either turn on the band stirring options, or limit 2.4 to an IoT only SSID. This will provide a solid WiFi capable nearly everything but the highest of bandwidth clients...you could even consider skipping wiring workstations depending on usage. Access layer switch for workstations and printers can be cheaper switches, 2.5g is a good sweet spot between price and future proofing, but even 1g is fine for most individual clients (the kind that could probably be fine on WiFi). You can consider saving a little on access layer switches by only getting 1 PoE switch for whatever needs it (remember your WAPs are connecting to the distribution switch, not here), and non-PoE for your workstations, because desk phones are falling out of favor. You can also save money here by not buying managed switches if you don't need them--but really do some soul searching there, if you go this route, then anything that isn't on your workstation VLAN would either need to be connected to the distribution switch, or its own access layer switch. Also, don't feel like you need a fancy fabric stacking switches for your access layer, that is the point of the higher-end distribution layer, to remove the need for things like that at this level. Home Hardware: I'm realizing the above assumed an office setting, if this if for your house and home lab then the above still applies, but you'll probably want everything managed and PoE, just because, but you probably also don't need multiple access layer switches. If your total port count is below 24, just skip separating distribution layer and access layer and just get one nice switch with the features you want. If you are at the point of considering a 48-port switch, I would instead get a nice high-end distribution switch for things that need it, and cheaper access layer switches with specs based on the needs of connected devices. For home use, don't worry about home running every device to the main switch, there is nothing wrong with running sub-switches for your media areas and office, those essentially become your access layer, just look for sub-switches with a 10g uplink so sharing bandwidth isn't an issue. Just make sure you always connect them to your distribution/main switch, don't daisy chain, the path should never have more steps than Client>Access>Distribution>Firewall>Internet or Client>Access>Distribution>Server if it is local.
    • Google Meet brings Gemini note-taking to AI Pro and Ultra subscribers by Karthik Mudaliar Google's Gemini-powered "Take notes for me" feature inside Google Meet is now available to Google AI Pro and Ultra subscribers. The features work on Google Meet for web as well as on mobile, and Google says that subscribers can use it for meetings they host in many supported languages. As the name suggests, "Take notes for me" allows Gemini to listen to a meeting, generate a summary, identify action items, and save the notes as a Google Doc in the user’s Drive. After the meeting, the organizer receives an email recap with the summary and action items, while the notes can also be attached to the related Calendar event depending on the meeting setup and sharing settings. The feature isn't automatically turned on for everyone, though. Google says that all meeting participants are notified when note-taking is turned on, and users can start it from the pencil icon in Meet or enable it for future calls through Meet’s meeting records settings. For work or school accounts, administrators can also control whether the feature is available and may require explicit participant consent for note-taking, recording, or transcription features. The feature first launched back in 2024, when it was available just for selected Workspace users. Over the years, Google added refinements and more options, including the ability to enable it when scheduling meetings via Google Calendar. Google's support docs say that the feature currently supports English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish, but only one language at a time. Meetings with multiple spoken languages are not currently supported, and Google recommends using the tool for meetings between 15 minutes and eight hours. The new feature makes Google Meet closer to its rivals that have AI tools already built in. Microsoft Teams has recently started offering Copilot and intelligent recap features that summarize meetings, surface highlights, and help with follow-ups, while Zoom’s AI Companion can also generate meeting summaries from desktop and mobile meetings.
    • GnuCash 5.16 by Razvan Serea GnuCash is a personal and small business finance application, freely licensed under the GNU GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows. It’s designed to be easy to use, yet powerful and flexible. GnuCash allows you to track your income and expenses, reconcile bank accounts, monitor stock portfolios and manage your small business finances. It is based on professional accounting principles to ensure balanced books and accurate reports. GnuCash can keep track of your personal finances in as much detail as you prefer. If you are just starting out, use GnuCash to keep track of your checkbook. You may then decide to track cash as well as credit card purchases to better determine where your money is being spent. When you start investing, you can use GnuCash to help monitor your portfolio. Buying a vehicle or a home? GnuCash will help you plan the investment and track loan payments. If your financial records span the globe, GnuCash provides all the multiple-currency support you need. Between 5.15 and 5.16, the following bugfixes were accomplished: Bug 421610 - RFE: Include logical dates for View->Filter by "date range"The Select Range section of the Date tab of the register's Filter By dialog box is changed to provide relative, specific date, or days ago options for the start and end of the filter range. The Show number of days item label is changed to Show from days ago to better reflect what it does. Bug 436105 - esc key not working as expected in register: Enable the escape key to cancel a field edit. Bug 797384 - Gnucash doesn't handle commodity prices with big numerator/denominator properly. Bug 798004 - Next gen UI for stock transactions Bug 799314 - Add "enter now" option in scheduled transaction editor. tab to allow users to select the scheduled transactions to be included in a “Since Last Run…” window. If there are no instances of a selected transaction triggered by today’s date, the next instance is triggered. Bug 799751 - autocomplete crash Bug 799759 - Users can't Enable entries via Checkboxes on Scheduled Transactions PageAllow the Enabled box in the list of scheduled transactions to be operated instead of having to open the transaction editor dialog and change the Enabled checkbox. Also added use of the Name column as the secondary column sort for all the other columns. Bug 799762 - Poor handling of cases where hidden/placeholder accounts are used in the account register Bug 799766 - Double line preference not respected in search register Bug 799767 - POST /accounts in bindings/python/example_scripts/rest-api is broken Bug 799777 - `xaccSplitSetParent`: reparenting a committed split silently drops its KVP slots (online_id, cap-gains links) Other changes & improvements: Numeric values may now be selected to copy in the Accounts page. Add new Finance::Quote source Finnhub.io: Free API key (personal/non-professional use) available at https://finnhub.io. Set FINNHUB_API_KEY environment variable to API key to use this source. As of June 2026, free tier API limit is 60 API calls/minute. The Investment Lots report has new optional columns for Computed Annual Growth Rate. Python Bindings: Improved translation of primary object (Account, Transaction, Split, etc.) so that they can be treated as normal Python objects. This is accomplished with SWIG magic so no existing code is obsoleted. Python Bindings: Better conversion of GLists to Python lists. Python Bindings: Destroy the QofSession in the Python Session dtor to prevent leaving the database locked. [engine] Add first-class online_id accessors for Split and Account and make them available to Python bindings, removing the unused Transaction online_id property. Improve C++ implementation of QofBook. Correct the Doxygen doc for qof_instance_get/set_kvp. [gnc-log-replay.cpp] fix incorrect guid dump Add some Boost library requirements needed by libgnucash-guile to CMakeLists.txt so that missing feature will fail at configure time. Use Compile-time Regular Expressions instead of std::regex in gnc-filepath-utils.cpp and instead of boost::regex in the CSV importer, with the CTRE v3.11.1 header added to borrowed [gnc-filepath-utils.cpp] null check char* arguments Add ChartJS licenses. Removed AEX from list of commodities. euronext.com is now using JS based anti-webscraping. [report-core] always offer options summary in reports. This is useful to debug reports. The Add options summary option is removed because it's no longer optional. Remove remaining obsolete IMContext from sheet Fix blurry text in HiDPI offscreen-rendered widgets Add port field to database connection dialog: The convention of appending the port number after the host isn't obvious. When editing a split in the register treat the account as being changed only if it isn't the one selected before editing instead of if the user performed an edit Return immediately from qof_book_destroy if hash_of_collections is null. If qof_book_destroy is called on a QofBook* freshly created with qof_book_new (usually because it was used to create a session that now must be destroyed) it would try to empty the non-existent hash tables, crashing. Clean up Flathub metadata to solve warnings at flatpak build time. Be consistent in naming GncPluginPage and GncPluginPageRegister HTML: Remove unimplemented function declarations. [gnc-html.cpp] remove unused buggy string conversion functions Convert libgnc-html to C++ Apply -Wall -Werr -Wmissing-prototypes to C++ compilation on Windows and fix the resulting errors. New and Updated Translations: Arabic, Croatian, Danish, Dutch, German, Finnish, Hungarian, Korean, Norwegian-Bokmal, Spanish Download: GnuCash 5.16 | 176.0 MB (Open Source) Links: GnuCash Home page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      536
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!