January 2024 - users - lists.freelock.com

pay someone to take my online exam
by Thomasadam4561＠gmail.com 04 Apr '24

04 Apr '24

can anyone do my exam online, if you are facing your online exam problems then you contact our professional experts in usa our experts ready to do your online exam as well as guarantee your good marks, our team will help your college Assignments, Financial Assignments, Programming Assignments and all types of business related assignments have the capacity to finish within the time limit, do my assignment online, you speak to us sitting at your home pay someone to do my homework, write my assignment, we are ready for you 24*7 hours. All you have to do is one click. take my online exam.https://www.allassignmenthelp.com/pay-someone-to-take-my-online-exam-f…

7 7

Can't connect to port 5762 (starman) to ledgersmb
by fherman＠inferential.com 01 Apr '24

01 Apr '24

I am a new user. This installation is on a local machine running linuxmint. I installed the latest ledgersmb image for docker via a pull. I have been able to get the PostgreSQL and the ledgersmb containers running. The container name for ledgersmb is myledger. The ps command shows both PostgreSQL and starman running. When I try to browse to http://localhost:5762/setup.pl, I get connection refused. I also tried to telnet to the port but got refused error. When I look for listening ports, port 5762 doesn't show. Apparently I am missing something in my installation. TIA

2 2

LedgerSMB 1.11.7 released
by Erik Huelsmann 28 Mar '24

28 Mar '24

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.11.7 * Fix creating an invoice from an order (#7855) * Retain partsgroup selection on Update in parts screen (#7848) * Fix missing columns on trial balance 'Ending' report type (#7870) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.11.7/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.11.7 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.11.7 Docker images have been published for ARMv7 (32-bit, e.g. Raspberry Pi (RPi) 3 and 400), ARM64 (e.g. RPi 4) and AMD64. These can be pulled from the GitHub Container Registry $ docker pull ghcr.io/ledgersmb/ledgersmb:1.11.7 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.11.7 These are the sha256 checksums of the uploaded files: d8086fff0340440ff022f455af8ee9486590a6c0b3db2262c4752bd1cc0384c0 ledgersmb-1.11.7.tar.gz df75cb6e6eb80843bf7c933581e72f28db86343817de743be62b4651b4c6227e ledgersmb-1.11.7.tar.gz.asc

6 6

technology write for us
by techpostinweb143＠gmail.com 25 Mar '24

25 Mar '24

One of the best guest blogging site with high quality content and domain authority. Write For US- Business, Tech News, Social media, Cloud Computing, Gadgets, Computers, Hardware, Apps / Reviews, SEO & Search Marketing and Operating Systems etc. We work hard to bring about best content that add value to them. https://www.techpostinweb.com/write-for-us/

2 2

LedgerSMB 1.6.33 released
by Erik Huelsmann 25 Mar '24

25 Mar '24

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.6.33 * Follow-up (fix) to upgrades blocked by files attached to transactions (Erik H) Erik H is Erik Huelsmann For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.6.33/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.6.33 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.6.33 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.6.33 These are the sha256 checksums of the uploaded files: ece4c7f63e725eea5dc2cbebbef0622b8426e24e1742daf98b1bc95fa292f6a9 ledgersmb-1.6.33.tar.gz 16d22e4c2a06a63d90ee5aca2a4e132f8e94b2eef252608da52ae0da7401c69e ledgersmb-1.6.33.tar.gz.asc

2 1

Fwd: [CRITICAL ALERT: ACT NOW] Critical vulnerabilities in GitLab Products
by Howard Lowndes 12 Feb '24

12 Feb '24

Is this security alert of any interest. ---------- Forwarded message --------- From: ACSC Alerts <alerts.acsc(a)contact.cyber.gov.au> Date: Mon, 15 Jan 2024, 18:16 Subject: [CRITICAL ALERT: ACT NOW] Critical vulnerabilities in GitLab Products To: <howard.lowndes(a)gmail.com> [image: High Alert - Act Quickly] 15 January 2024 Dear ASD's ACSC Alert Service subscriber This Alert is relevant to Australians who use GitLab on any platform. These vulnerabilities impact the versions listed below: - 16.1 to 16.1.5 - 16.2 to 16.2.8 - 16.3 to 16.3.6 - 16.4 to 16.4.4 - 16.5 to 16.5.5 - 16.6 to 16.6.3 - 16.7 to 16.7.1 This alert is intended to be understood by all users. Customers are encouraged to patch to the latest version using the GitLab upgrade path and to enforce multi-factor authentication for all GitLab accounts*.* *Background / What’s happened?* - GitLab has posted a security advisory and patch to address several vulnerabilities, the most severe of which is CVE-2023-7028. - CVE-2023-7028 allows an account take over via the ability to have password reset emails delivered to an unauthenticated email address. - Multi-factor authentication should be enabled immediately for all GitLabs users, and self-managed instances should be upgraded to the latest version as soon as possible. - Users with multi-factor authentication already enabled may be impacted by a password reset, however an attacker would not be able to take over their account using this vulnerability. - GitLab is not aware of any active exploitation of this vulnerability which was discovered via their Bug Bounty program. *Affected versions / applications:* - CVE-2023-7028: This vulnerability impacts all versions of GitLab CC/EE from 16.1 to 16.1.6, 16.2 prior to 16.2.9, 16.3 prior to 16.3.7, 16.4 prior to 16.4.5, 16.5 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7 prior to 16.7.2 - The security release also addresses CVE-2023-5356, CVE-2023-4812, CVE2023-6955 and CVE-2023-2030. *Mitigation / How do I stay secure?* - Multi-factor authentication should be enabled immediately for all GitLabs users. - Self-managed instances should be upgraded to the latest version as soon as possible. GitLab advises managed instances have now all had the patch applied. - Further information and details to investigate potential compromise can be found in the GitLab Security release linked below: https://about.gitlab.com/releases/2024/01/11/critical-security-release-gitl… *Assistance / Where can I go for help?* Organisations or individuals that have been impacted or require assistance can contact us via 1300 CYBER1 (1300 292 371) <%201300%20292%20371>. *Read this alert on the website: https://www.cyber.gov.au/about-us/view-all-content/alerts-and-advisories/cr… <https://www.cyber.gov.au/about-us/view-all-content/alerts-and-advisories/cr…> <https://www.cyber.gov.au/about-us/view-all-content/alerts-and-advisories/ci…>* *Are you a victim of cybercrime? Visit ReportCyber <https://www.cyber.gov.au/report-and-recover/report> to take your next steps.* *We use hyperlinks to give you more information. If you don't want to click hyperlinks, you can search for the information on ASD's ACSC Website.* *CONTACT US* Web: https://www.cyber.gov.au <https://www.cyber.gov.au/about-us/about-acsc/contact-us> X (Twitter): https://twitter.com/CyberGovAU Facebook: https://www.facebook.com/cybergovau LinkedIn: https://www.linkedin.com/company/australian-cyber-security-centre [image: Facebook] <https://www.facebook.com/cybergovau> [image: Twitter] <https://twitter.com/cybergovau> [image: YouTube] <https://www.youtube.com/channel/UChO_bPg4QOWxSOzH4OYw3Tg/featured> [image: LinkedIn] <https://www.linkedin.com/company/australian-cyber-security-centre> Was this alert helpful? * Yes <https://www.cyber.gov.au/asf?alert_subject=Critical%20vulnerabilities%20in%…>* | *No <https://www.cyber.gov.au/asf?alert_subject=Critical%20vulnerabilities%20in%…>* You are receiving this message at the address howard.lowndes(a)gmail.com If you no longer wish to receive this information, you can unsubscribe <https://p-2581519.secure.force.com/dc/t/gobal-email-opt-out/cgndc6moogvrzyn…>

3 3

LedgerSMB Community overview 2023
by Erik Huelsmann 10 Feb '24

10 Feb '24

As the year-end approaches, it's time to provide an overview of what our community has achieved over the past year. At the end of last year, I wished everybody a healthy and prosperous 2023 and now is a time to look back and see how we did. == Community interest == After years of decline in the number of hits on our website, last year saw an unexpected upswing in hits. Unfortunately, it didn't last long: this year hits dropped again. The increase in number of Stars and Forks on GitHub (Stars went up from 304 on 16 January 2022 to 348 today - in line with the increase last year), we can conclude that there is still interest in the project. This is supported by the fact that we see new people attend the ledgersmb chat channel on Matrix, with many contributing their bugs and experience. == Releases == With the release of 1.11.0 on 03 October 2023, we realized our goal to release 1.11 in the second half of the year, close to a year after 1.10. With releases in the third quarter, we aim to provide mature software before year-end -- when most companies close their books. Despite the short release cycle, we were able to include a sizeable list of new functionalities, changes and (code) cleanups through 806 commits, 711 files changed, 234,664 added lines and 162,575 removed lines of code (and comments) between 1.10.0 and 1.11.0. With 34 releases across 3 maintenance branches in 2023, the project was able to increase the pace of 2022 (which had 37 releases across *4* branches): 1.9 (8): 1.9.23 - 1.9.30 1.10 (19): 1.10.9 - 1.10.27 1.11 (7): 1.11.0 - 1.11.6 Which excludes the alpha, beta and release candidate releases. == Development progress == This year saw lower numbers of commits than last year. Although the number of commits was lower, the number of pull requests (720) is higher than last year (620) but still lower than the year before (827). The number of active developers - derived from accepted commits - went was lower than last year (7) by 1 (6 this year). This year, too, we were able to close a number of long-standing bugs/issues, continuing last year's focus to close as many issues as possible in the 7-year-and-older range: * #1346: Barcode entry on the invoice screen broken (regressed in 2016) * #2657: Upgrades may fail for 1.3."not latest" to 1.5+ * #2661: Empty inventory reports not showing in search results All from 2017 and 2016, just to name a few. Project commits on all branches (excluding merges): 672 Erik Huelsmann 72 Yves Lavoie 15 Aung Zaw Win 6 Christian Eriksson 6 Neil Tiffin 1 John Locke By comparison, these are the figures for 2022: 927 Erik Huelsmann* 132 Yves Lavoie* 10 Aung Zaw Win* 6 Neil Tiffin* 5 Jeff Shelley* 3 Hugh Esco 2 Chris Travers Please note that the number of commits is in no way a measure of time spent on the project. Also note that these numbers don't include the time spent by those taking the effort to report their problems and taking the time to respond to developer questions as well as helping to test solutions when developers think they solved the problem. Similarly, there was a lot of activity with respect to issues: Number of open issues at 2023-01-01: 148 of which remain open today: 99 Issues closed: 114 of which created before 2023-01-01: 49 Issues created: 85 of which still open: 20 Number of open issues today: 119 This amount of development activity triggers many CI/CD jobs. To run our test workloads, we have been using GitHub Actions as well as CircleCI, each set up to test different aspects. The main thing in the 1.12 Changelog that we spent time on which hasn't been released as part of 1.11 is the migration experience from 1.3 through 1.7 to 1.12. Areas that we're currently spending time on, include: * Implementation of an API to create orders along the same lines as the invoices API * Documentation of the status quo of the code base in Architecture Decision Records (ADRs) The 148 issues that are open today summarize into these statistics: * 5 bite-sized: issue ideal to start with our code base * 5 help-wanted: these are issues we need someone to get involved * 5 sponor-wanted: these will be developed when someone helps out by footing bills * 61 type:enhancement: generally requests for new or improved features (Note that an issue may fall into more than one category or none at all.) == New functionality and improvements == 1.11 improves on 1.10's use of workflows to manage invoices and orders, moving GL transactions to the same infrastructure. At the same time, it's banking on the new functionality to consistently and predictably show buttons for available actions on orders, invoices and transactions. The same functionality is what enables the higher granularity document action history that 1.11 features. == Looking forward to 2024 == In 2024, we'll likely release 1.12 around the third quarter; again in a release cycle a bit shorter than a year. This year the 1.10 release branch will reach End-Of-Life status on 08 October. And last but not least, I'm hoping for 1 or 2 new contributors (not necessarily developers; translators, testers, documentation writers or UI artists are all greatly appreciated!). If you want to contribute, but don't know where to start, please contact me. == In closing == Thanks to everybody who contributed to any of the above in any way, especially to Neil Tiffin for taking the time to discuss (and thereby sharpen) planned changes Computerisms.ca for hosting our DNS Freelock.com for hosting our website and mailing lists Efficito.com for hosting our mailing list archive, apt repository, release and download server GitHub.com, CircleCI and coveralls.io for hosting our development workflow My special personal thanks go to my GitHub Sponsors for supporting me for time, efforts and (financial) resources dedicated to the project! Leaves me only to wish everybody in our community - and their loved ones - happy holidays and a safe and productive 2024! -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

3 3

LedgerSMB 1.10.29 released
by Erik Huelsmann 06 Feb '24

06 Feb '24

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.10.29 * Fix formatting of amounts in AR/AP search results (#7896) * Explicitly set foreground color on dark backgrounds in blue theme (#7875) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.10.29/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.10.29 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.10.29 Docker images have been published for ARMv7 (32-bit), ARM64 (also known as ARMv8, e.g. RPi 3+) and AMD64. These can be pulled from the GitHub Container Registry $ docker pull ghcr.io/ledgersmb/ledgersmb:1.10.29 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.10.29 These are the sha256 checksums of the uploaded files: 16ea9b92f180fa6be32b9c64e33506322582bfb64352d5cde73675ae91a61ec9 ledgersmb-1.10.29.tar.gz b179b2468fafdeb3127a440e281c0515788973321f031f89105ce30cfebbbb23 ledgersmb-1.10.29.tar.gz.asc

4 3

LedgerSMB 1.11.8 released
by Erik Huelsmann 29 Jan '24

29 Jan '24

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.11.8 * Fix changing Taxform checkmark after posting AR/AP transactions (#7894) * Restore customer/vendor name on PNL drilldown after GL column change (#7895) * Fix formatting of amounts on AR/AP search results (#7896) * Fix import of CoA csv with non-empty 'links' field (#7912) * Explicitly set foreground color on dark backgrounds in blue theme (#7875) * Fix screens, e.g. contacts, impacted by rename of 'action' parameter (#7918) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.11.8/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.11.8 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.11.8 Docker images have been published for ARMv7 (32-bit), ARM64 (also known as ARMv8, e.g. RPi 3+) and AMD64. These can be pulled from the GitHub Container Registry $ docker pull ghcr.io/ledgersmb/ledgersmb:1.11.8 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.11.8 These are the sha256 checksums of the uploaded files: 3a89187095ea6909c55d546776c25dacdbf63b980c43832c17031ac6dfea9c37 ledgersmb-1.11.8.tar.gz d832600caebe88b5dc39d4220e10e25ad912c037d7305d486ffa2e37f0e3d9a6 ledgersmb-1.11.8.tar.gz.asc

3 2

Fwd: "Create new work flow"
by Howard Lowndes 25 Jan '24

25 Jan '24

---------- Forwarded message --------- From: Howard Lowndes <howard.lowndes(a)gmail.com> Date: Wed, 13 Dec 2023, 21:45 Subject: "Create new work flow" To: LedgerSMB <users(a)lists.ledgersmb.org> Version 1.11.4 On Sales Invoice, Credit Invoice, Vendor Invoice, Debit Invoice, in the lower part of the screen there is a small section "Create new workflow". One of the preset items is the date and time. I notice that it is putting in the UTC date and time and not the locale date and time. Is there a system setting that I have missed or should I be reporting this as a bug along with Issue #7801? Regards, -- Howard. -- When you want a computer system that works, just choose Linux; When you want a computer system that works, just, choose Microsoft.

4 3