Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
ioc.exchange is one of the many independent Mastodon servers you can use to participate in the fediverse.
INDICATORS OF COMPROMISE (IOC) InfoSec Community within the Fediverse. Newbies, experts, gurus - Everyone is Welcome! Instance is supposed to be fast and secure.

Administered by:

Server stats:

1.6K
active users

ioc.exchange: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#update

82 posts65 participants4 posts today
Public
Aptivi

Making Projects Better

Making our projects better than before is one of our most important things that we have planned to do. We have improved the build system across all projects by introducing the tools repository on GitHub that is used as a submodule. Our strategy for this plan is to make sure that all our projects get the highest quality possible, while aiming for more.

Announcements for new release of our flagship projects will be made every major version or a version that is worth talking about. Not only updates will be done, but projects that are new to the programming industry will be made to allow developers to have more options according to the program.

Recently, we have started improving the documentation of the Terminaux project for the upcoming release. We have currently restructured the cyclic writer documentation so that a single page is split to multiple pages by category. This helps find information more quickly.

In the second half of the year, we are planning to introduce changes to our work plans so that we’d be more open. Confirmed additions, improvements, and other updates will be added to every repository’s GitHub Projects, straight from the internal information. This is to let the users know of the roadmap of all our projects in a more transparent manner.

After the release of the upcoming Nitrocid version series, we’ll make sure that other projects get their own development time as we are striving to improve them with new features and other general improvements. Because the upcoming version of Nitrocid is currently in a stage where it needs to be adjusted for the next Terminaux version, a beta program will be introduced. This is to gain feedback from developers and users, and we listen to all feedback!

Making sure that we fulfill our promises to you, we’ll keep you informed of any new updates regarding our projects. Meanwhile, normal development for all projects will start on April 6th, and we hope that we introduce you to new, exciting features. Are you ready for the most exciting moments?

Image by freepik

#bassboom#C_#csharp
Public *
Aptivi

HP EliteBook Ultra G1q Linux support under construction

Another Copilot+ PC, HP EliteBook Ultra G1q, is getting initial support for Linux, but this support is under construction as it won’t be merged to Linux 6.15. However, a future version of Linux could have better support for this laptop as we see improvements.

An HP EliteBook Ultra G1q contains a Snapdragon X Elite SoC to ensure that you have an AI powerhouse, complete with Microsoft’s Windows 11 and Copilot+ features that utilize AI. This AI laptop has a 14-inch screen to increase productivity. Furthermore, it uses ARM64 instead of the usual AMD64, which is expected from any Copilot+ PC.

Canonical is trying to get Linux to work with this laptop, but the device tree was incomplete because there may be errors when specifying the device parameters in the DTSI file. Expect certain features, such as audio, not working with Linux at this point.

However, in a future version of the Linux kernel, we’ll see more Copilot+ PCs, such as this one, being well supported. Right now, you can’t experience the full Linux desktop because there is no support for certain features, such as audio.

#EliteBook#EliteBookUltra#HP
Public
Prof. Dr. Dennis-Kenji Kipker

Zeit für das nächste #iOS #Update: In dieser Woche warnt das #BSI vor kritischen #Cybersecurity Schwachstellen in verschiedenen #Apple-Produkten - zeitnahe System Updates sind daher geboten:

"Ein Angreifer [kann] diese Schwachstellen ausnutzen, um Daten offenzulegen, Schadcode auszuführen, Apps zum Absturz zu bringen, Schutzmaßnahmen zu umgehen, mehr Rechte zu erhalten oder Daten zu verändern. Die Ausnutzung erfordert eine Benutzeraktion"

wid.cert-bund.de/portal/wid/bu

wid.cert-bund.deWarn- und Informationsdienst
Public
not blue witch
Liebe Tech-Bubble, ich hab da mal ein Problem.

Ich besitze eine #Fritzbox 7530, die vor kurzem ein #Update auf 8.02 gemacht hat. Seitdem bricht immer die Internetverbindung zusammen, wenn ich den Desktop-Rechner einschalte. WLAN-Geräte sind ok, es sind nur die verkabelten Geräte, die das auslösen (#Nobara).
Die Fritzbox sagt dann #DSL wär verbunden, #Internet aber nicht.
Hilft nur ein Reboot via Strom-kappen.

Die Vodafone Hotline hat die Leitung gemessen, da is alles ok.

Es gibt keine offensichtliche Möglichkeit, das Update zurückzurollen.

Bevor ich jetz mit Firmwareversionen rumspiele... kennt jemand das Problem?
Public
Aptivi

Linux 6.15 Memory Management improvements

The upcoming version of Linux will incorporate many memory management improvements that will make your PC better than before. This pull request, which is already migrated to the main Linux 6.15 Git, incorporates many memory management changes that will achieve that goal of making your PC manage memory better than before. As this pull request mentions a possible Linux 6.15 RC1 release by just a title, we expect that this release candidate will be released on April 6th.

A new command-line options, hugetlb_alloc_threads, has been added to the Linux kernel that allows you to choose how many threads are in use, with the default being a reasonable 25% to make your computer boot up faster. This is when allocating a large number of huge pages, which will see around 2.75x to 4.3x speedup on Skylake and Cascade Lake systems.

Alongside with this change, there is another interesting patch series that revolved around making the huge pages allocator more reliable than before. It reduces fragmentation to allow larger requests to be met more quickly, while making the operation cheaper.

In the pull request linked above, you can find a list of patch series that are merged to the Linux 6.15 source code.

#Computer#Computers#improvements
Public
Aptivi

One UI 7 Beta now released for Galaxy A55 series

Did you remember when an official Samsung Newsroom article had confirmed the Beta deployment month for the One UI 7 software based on the all-new Android 15 for the A55 series? Well, the time has finally come! Although the A55 beta program was overdue, One UI 7 Beta has been released for the following countries:

This means that everyone living in the above countries with their phones can now try out One UI 7 in its beta form! This is considered to be the last Beta program for the whole One UI 7 update.

To join the Beta program, open Samsung Members, find the One UI 7 banner similar to the one below, and click on the registration button.

Afterwards, follow the instructions on the screen. If everything is OK, go to Settings > Software update > Download and install. You’ll get the screen that looks similar to this:

Let it download, but it’s going to take a bit of time depending on your Internet connection. Afterwards, click on the Install button.

Remember: never interrupt the update process during the installation phase, and make sure that your phone is fully charged before proceeding. This is a precaution intended to avoid interruptions. For some markets, it’s advisable to put your device in a well-ventilated room to avoid green lines caused by heat up in some AMOLED panels.

Are you excited?

#Android#Android15#AndroidV
Public
Aptivi

Ubuntu on phones now receive initial VoLTE support

If you are using one of the supported Ubuntu Phone devices, such as a Volla 22 (contains a MediaTek Helio G85 SoC) or a Fairphone 5 (contains a Qualcomm QCM6490 SoC), you can now use VoLTE on your device.

The necessary modifications for both SoC vendors have been added to both the Noble Numbat version and the Focal Fossa version so that VoLTE works on these devices that have Ubuntu Touch installed. However, for other phones, such as Xiaomi and Google Pixel phones, it’s on the developer who created the port to modify it so that it works with VoLTE.

While they have tested the functionality with both high-quality voice calls and SMS messages, they have reported issues when working with MMS. In the status bar, if your phone shows VoLTE, this means that you can have high-quality voice calls.

In order to try out VoLTE support, you must make sure that:

  • your phone is running the latest version of Ubuntu Touch,
  • your phone supports VoLTE, and
  • your carrier and your cellular plan support VoLTE.

Image by freepik

#Fairphone#Fairphone5#news
Public
Abnormal Human Being

So, I am stuck trying to apply the current #Mastodon update. Note that there may be many good reasons why, chief among them, that I am self-taught and very much in the "trying stuff out half-blindly while learning"-stage. Thankfully, nothing broke irreversably just yet.

If anyone here feels like helping a noob out, or just loves a conundrum, details can be found here:

lemmy.abnormalbeings.space/pos

lemmy.abnormalbeings.space[SUPPORT][Mastodon] Getting stuck on trying to apply the latest update - AbnormalLemmingscross-posted from: https://lemmy.abnormalbeings.space/post/804932 [https://lemmy.abnormalbeings.space/post/804932] I have searched around for answers to this, but so far, the solutions I found and tried have not been working for me. Thankfully, the update isn’t that critical, so time is not of the essence as of now. But I fear, the problem will only persist. So, bit of a headscratcher: I am following the guide to upgrade (no Docker) from here. [https://github.com/mastodon/mastodon/releases/tag/v4.3.7] Simple enough, right? Sadly, I keep getting: ~/live$ RAILS_ENV=production bundle exec rails assets:precompile I, [2025-04-03T20:30:30.072648 #981372] INFO -- : [dotenv] Loaded .env.production Mastodon and Webpacker requires Yarn ">=4 <5" and you are using 1.22.22 Exiting! So, the proposed solution? Using corepack as intended. That, at first, upon entering “corpack prepare” and “corepack enable” in succession, seemed to run silently and without errors/warnings. But it changed nothing at all for the error message. Prompting me to search around, haphazardly try to apply fixes, trying to remove and reinstall yarn, “the usual”. My last attempt was to globally remove yarn and corepack with npm and then re-install both. Since then, a new, exciting error is happening: ~/live$ corepack enable Internal Error: EACCES: permission denied, symlink '../lib/node_modules/corepack/dist/pnpm.js' -'/usr/bin/pnpm' at async Object.symlink (node:internal/fs/promises:1005:10) at async EnableCommand.generatePosixLink (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23156:5) at async Promise.all (index 0) at async EnableCommand.execute (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23143:5) at async EnableCommand.validateAndExecute (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:20258:22) at async _Cli.run (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:21195:18) at async Object.runMain (/usr/lib/node_modules/corepack/dist/lib/corepack.cjs:23642:19) Oh, and when trying to install yarn and corepack, now, I get: ~/live$ npm install yarn npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch npm error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log ~/live$ npm install corepack npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch npm error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log ::: spoiler the logs in question: $ cat /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log 0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@11.2.0 2 info using node@v22.14.0 3 silly config load:file:/usr/lib/node_modules/npm/npmrc 4 silly config load:file:/home/mastodon/live/.npmrc 5 silly config load:file:/home/mastodon/.npmrc 6 silly config load:file:/usr/etc/npmrc 7 verbose title npm install yarn 8 verbose argv "install" "yarn" 9 verbose logfile logs-max:10 dir:/home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z- 10 verbose logfile /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log 11 silly logfile start cleaning logs, removing 1 files 12 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368 13 silly logfile done cleaning log files 14 silly idealTree buildDeps 15 verbose stack Error: Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 15 verbose stack at unsupportedURLType (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:369:15) 15 verbose stack at fromURL (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:428:13) 15 verbose stack at Function.resolve (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:110:12) 15 verbose stack at #nodeFromEdge (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1039:22) 15 verbose stack at #buildDepStep (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:904:35) 15 verbose stack at async Arborist.buildIdealTree (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:181:7) 15 verbose stack at async Promise.all (index 1) 15 verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5) 15 verbose stack at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:149:5) 15 verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:208:9) 16 error code EUNSUPPORTEDPROTOCOL 17 error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 18 silly unfinished npm timer reify 1743710053061 19 silly unfinished npm timer reify:loadTrees 1743710053064 20 silly unfinished npm timer idealTree:buildDeps 1743710057205 21 silly unfinished npm timer idealTree:#root 1743710057206 22 verbose cwd /home/mastodon/live 23 verbose os Linux 6.1.0-31-amd64 24 verbose node v22.14.0 25 verbose npm v11.2.0 26 verbose exit 1 27 verbose code 1 28 error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_12_827Z-debug-0.log ~/live$ cat /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log 0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@11.2.0 2 info using node@v22.14.0 3 silly config load:file:/usr/lib/node_modules/npm/npmrc 4 silly config load:file:/home/mastodon/live/.npmrc 5 silly config load:file:/home/mastodon/.npmrc 6 silly config load:file:/usr/etc/npmrc 7 verbose title npm install corepack 8 verbose argv "install" "corepack" 9 verbose logfile logs-max:10 dir:/home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z- 10 verbose logfile /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log 11 silly logfile start cleaning logs, removing 1 files 12 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368 13 silly logfile done cleaning log files 14 silly idealTree buildDeps 15 verbose stack Error: Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 15 verbose stack at unsupportedURLType (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:369:15) 15 verbose stack at fromURL (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:428:13) 15 verbose stack at Function.resolve (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:110:12) 15 verbose stack at #nodeFromEdge (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1039:22) 15 verbose stack at #buildDepStep (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:904:35) 15 verbose stack at async Arborist.buildIdealTree (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:181:7) 15 verbose stack at async Promise.all (index 1) 15 verbose stack at async Arborist.reify (/usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:131:5) 15 verbose stack at async Install.exec (/usr/lib/node_modules/npm/lib/commands/install.js:149:5) 15 verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:208:9) 16 error code EUNSUPPORTEDPROTOCOL 17 error Unsupported URL Type "patch:": patch:babel-plugin-lodash@npm%3A3.3.4#~/.yarn/patches/babel-plugin-lodash-npm-3.3.4-c7161075b6.patch 18 silly unfinished npm timer reify 1743710065916 19 silly unfinished npm timer reify:loadTrees 1743710065919 20 silly unfinished npm timer idealTree:buildDeps 1743710070343 21 silly unfinished npm timer idealTree:#root 1743710070344 22 verbose cwd /home/mastodon/live 23 verbose os Linux 6.1.0-31-amd64 24 verbose node v22.14.0 25 verbose npm v11.2.0 26 verbose exit 1 27 verbose code 1 28 error A complete log of this run can be found in: /home/mastodon/.npm/_logs/2025-04-03T19_54_25_678Z-debug-0.log ::: Thankfully, mastodon is still working, no database issues, nothing indicating I fucked up beyond repair yet. I am a bit at a loss, unfortunately, but eager to use my fuckup as a learning experience - am glad to hear any and all more experienced folk chiming in!
#sysadmin#techsupport#update
Continued thread
Public
Russia-Ukraine Daily News

#UPDATE

🇺🇸 #Trump has moved to fire several senior White House National Security Council officials taking action soon after he was urged by far-right activist Laura Loomer to purge staffers she deemed insufficiently committed to his Make America Great Again agenda.

apnews.com/article/trump-waltz

President Donald Trump speaks during an event to announce new tariffs in the Rose Garden at the White House, Wednesday, April 2, 2025, in Washington. (AP Photo/Mark Schiefelbein)
AP News · Trump moves to fire several national security officials over loyalty concernsBy Matthew Lee
#usa
ExploreLive feeds
About