photog.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for your photos and banter. Photog first is our motto Please refer to the site rules before posting.

Administered by:

Server stats:

242
active users

#binaryblob

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><a href="https://infosec.space/tags/CXL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CXL</span></a> <a href="https://www.youtube.com/watch?v=qgv5KybY1L8" rel="nofollow noopener" target="_blank">sounds really cool</a> as a <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RAM</span></a> <a href="https://infosec.space/tags/expansion" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>expansion</span></a>. </p><ul><li>I just long for a <a href="https://infosec.space/tags/RAMdrive" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RAMdrive</span></a> like <a href="https://infosec.space/tags/HyperDrive" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HyperDrive</span></a> that can be transparently used for <a href="https://infosec.space/tags/storage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>storage</span></a>. </li></ul><p>That being said <a href="https://infosec.space/tags/Enterprise" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Enterprise</span></a> <a href="https://infosec.space/tags/Database" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Database</span></a> users that have to deal with <a href="https://infosec.space/tags/BinaryBlob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BinaryBlob</span></a> garbage like <a href="https://infosec.space/tags/SAP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SAP</span></a> or god forbid <a href="https://infosec.space/tags/Oracle" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Oracle</span></a> will love it to save <a href="https://infosec.space/tags/LicensingCosts" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LicensingCosts</span></a> as they don't need to get <a href="https://infosec.space/tags/MultiSocket" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MultiSocket</span></a> systems for that...</p><ul><li>Espechally since it doesn't count against the RAM limits of the <a href="https://infosec.space/tags/CPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CPU</span></a>!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.treehouse.systems/@valpackett" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>valpackett</span></a></span> <span class="h-card" translate="no"><a href="https://donotsta.re/users/elly" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>elly</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@CommieGIR" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>CommieGIR</span></a></span> <span class="h-card" translate="no"><a href="https://social.treehouse.systems/@marcan" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>marcan</span></a></span> and then people woubder why <a href="https://infosec.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RaspberryPi</span></a> owns the <a href="https://infosec.space/tags/ARM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARM</span></a>-<a href="https://infosec.space/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SBC</span></a> market, cuz whilst their <a href="https://infosec.space/tags/BinaryBlob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BinaryBlob</span></a> approach of <code>bootcode.bin</code> isn't cool, they at least give people proper documentation to the point that one can build i.e. <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>OS1337</span></a></span> for it and have it boot within very few attempts.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@Kensan" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Kensan</span></a></span> <span class="h-card" translate="no"><a href="https://waldvogel.family/@marcel" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>marcel</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@adfichter" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>adfichter</span></a></span> Das kommt hinzu...</p><p>Ich persönlich bin ja dafür dass <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> eine strikte <a href="https://infosec.space/tags/Produkthaftung" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Produkthaftung</span></a> befolgen müssen - inklusive <a href="https://infosec.space/tags/Versicherung" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Versicherung</span></a> für <a href="https://infosec.space/tags/Folgesch%C3%A4den" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Folgeschäden</span></a> und Schadensersatzansprüche...</p><ul><li>Bei <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a> würde ich dies nicht einsehen weil diese ja <em>kostenlos und ohne Haftung</em> angeboten wird - bei CCSS gibt es keinen rationalen Grund dies zu erlauben!</li></ul><p>Ohnehin gehört <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Govware</span></a> wie <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows</span></a> und <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Scareware</span></a> wie <a href="https://infosec.space/tags/CrowdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CrowdStrike</span></a> und der ganze andere <em>"<a href="https://infosec.space/tags/Antivirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Antivirus</span></a>"</em> - <a href="https://infosec.space/tags/Malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Malware</span></a> verboten, weil alles was <a href="https://infosec.space/tags/Binaryblob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Binaryblob</span></a>-<a href="https://infosec.space/tags/Kernelhacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kernelhacks</span></a> erzeugen ist Mist!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@Cappyjax" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Cappyjax</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.radio/@WB2EEE" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>WB2EEE</span></a></span> <span class="h-card" translate="no"><a href="https://zug.network/@Zugschlus" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Zugschlus</span></a></span> <span class="h-card" translate="no"><a href="https://donotsta.re/users/elly" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>elly</span></a></span> </p><p>I disagree with <a href="https://mastodon.social/@Cappyjax/112821333101353573" rel="nofollow noopener" target="_blank">your assessment</a> to some extent, as on <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> there's not much of a tolerace or even acceptance of <a href="https://infosec.space/tags/rootkits" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rootkits</span></a> like <a href="https://infosec.space/tags/CorwdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CorwdStrike</span></a> for all the right reasons!</p><ul><li><a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Scareware</span></a> like that has <em>no legitimate reason to exist</em> and the only place I've seen that is on <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows</span></a> because people distrusting <a href="https://infosec.space/tags/WindowsDefender" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WindowsDefender</span></a> and thus <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> are unwilling to to what is <em>evidently the correct solution</em> and yeet Windows for good.</li></ul><p>Cuz it's not about <a href="https://infosec.space/tags/Fanboyism" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fanboyism</span></a>, but a fact that most Windows - <a href="https://infosec.space/tags/Sysadmins" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sysadmins</span></a> (or rather decisionmakers for that matter) seem to be high on <a href="https://infosec.space/tags/Copium" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Copium</span></a> and refuse to take actual <a href="https://infosec.space/tags/consequences" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>consequences</span></a> but accept the <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Enshittification</span></a> as a fact of life when it's not...</p><ul><li>Or am I the only one who remembers the rightful backclash when <a href="https://infosec.space/tags/ads" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ads</span></a> were shoved into <a href="https://infosec.space/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ubuntu</span></a> whilst on <a href="https://infosec.space/tags/Windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows11</span></a> and <a href="https://infosec.space/tags/Windows10" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows10</span></a> people just seem to shrug their shoulders?</li></ul><p>It's just that this entire shitshow would not have happened on <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> because here we don't have an entire ecosystem of <a href="https://infosec.space/tags/ValueRemoving" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ValueRemoving</span></a> <em>"<a href="https://infosec.space/tags/AntiVirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AntiVirus</span></a>"</em> bs being shoved on Desktops and Servers in the form of <a href="https://infosec.space/tags/Binaryblob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Binaryblob</span></a> <a href="https://infosec.space/tags/Kernelhacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kernelhacks</span></a>!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://zug.network/@Zugschlus" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Zugschlus</span></a></span> <span class="h-card" translate="no"><a href="https://donotsta.re/users/elly" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>elly</span></a></span> I sincerely disagree because on <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> there is neither need nor demand for <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Scareware</span></a> like <a href="https://infosec.space/tags/CrowdStrike" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CrowdStrike</span></a> and even then noone should allow such garbage in their systems as a <a href="https://infosec.space/tags/rootkit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rootkit</span></a>!</p><ul><li>In fact, <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> has an <a href="https://infosec.space/tags/ABI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ABI</span></a> for <a href="https://nondeterministic.computer/@mjg59/112816011370924959" rel="nofollow noopener" target="_blank">the specific function</a> so no need to shove a <a href="https://infosec.space/tags/BinaryBlob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BinaryBlob</span></a> into the Kernel and no issues on Linux systems...</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://equestria.social/@SweetAIBelle" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>SweetAIBelle</span></a></span> thanks!</p><p>That's exactly what I was looking for - tho I've to also find the <a href="https://infosec.space/tags/WindowsXP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WindowsXP</span></a> drivers since <a href="https://infosec.space/tags/WindowsVista" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WindowsVista</span></a> really feels garbage on these machines...</p><ul><li>Sadly the <a href="https://infosec.space/tags/PPA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PPA</span></a> for the <a href="https://infosec.space/tags/Pulsbo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pulsbo</span></a> / <a href="https://infosec.space/tags/GMA500" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GMA500</span></a> driver on <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UbuntuLTS</span></a> 12.04 went down and I've yet to source that <a href="https://infosec.space/tags/binaryblob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binaryblob</span></a> and Kernel Module loader &amp; build script as this provided <a href="https://infosec.space/tags/OpenGL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenGL</span></a> ES hardware acceleration, and neither <a href="https://infosec.space/tags/Intel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Intel</span></a> nor <a href="https://infosec.space/tags/PowerVR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PowerVR</span></a> / <a href="https://infosec.space/tags/ImaginationTechnologies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ImaginationTechnologies</span></a> were willing to release it, despite it existing (there even was a <a href="https://infosec.space/tags/DellMini" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DellMini</span></a> with <a href="https://infosec.space/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ubuntu</span></a> 8.04 sold with it!)...</li></ul><p>Either way, I think that both the <a href="https://infosec.space/tags/EeePC701" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EeePC701</span></a> and <a href="https://infosec.space/tags/Vaio" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Vaio</span></a> <a href="https://infosec.space/tags/P11Z" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P11Z</span></a> would greatly benefit from being rereleased with a new, <a href="https://infosec.space/tags/IntelAtom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IntelAtom</span></a> / <a href="https://infosec.space/tags/CeleronJ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CeleronJ</span></a> / <a href="https://infosec.space/tags/N100" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>N100</span></a>-based Mainboard and other updated components that make then quieter, more power saving and way faster...</p><ul><li>Some Chinese <a href="https://infosec.space/tags/HardwareHackers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HardwareHackers</span></a> going by the group alias <a href="https://infosec.space/tags/NB51" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NB51</span></a> did make their own custom <a href="https://infosec.space/tags/Mainboard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mainboard</span></a> for the <a href="https://infosec.space/tags/ThinkPad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThinkPad</span></a> <a href="https://infosec.space/tags/X230" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>X230</span></a> but those were super rare and expensive if even available...</li></ul><p>If I had the money I would've likely completed the <a href="https://infosec.space/tags/NUCbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NUCbook</span></a> and just go with a chonky machine...<br><a href="https://github.com/kbtechnologies/NUCbook" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/kbtechnologies/NUCb</span><span class="invisible">ook</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mstdn.social/@nbloglinks" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>nbloglinks</span></a></span> <span class="h-card" translate="no"><a href="https://social.skynetcloud.site/@jos1264" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jos1264</span></a></span> <span class="h-card" translate="no"><a href="https://social.bund.de/@bsi" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bsi</span></a></span> generally you can't trust any <a href="https://infosec.space/tags/DigitalSnakeoil" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalSnakeoil</span></a> delers aka. 3rd Party <a href="https://infosec.space/tags/Antivirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Antivirus</span></a> for <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows</span></a> and <a href="https://infosec.space/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macOS</span></a>!</p><p>As both OSes are proprietary, said <em>"Antivirus"</em> are ugly <a href="https://infosec.space/tags/BinaryBlob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BinaryBlob</span></a> <a href="https://infosec.space/tags/Kernelhacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kernelhacks</span></a>!</p><p>If you don't trust <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> and <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a>.respectably to maintain their OSes and keep them secure, then <em>DON'T USE SAID OS!</em></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.linux.pizza/@Szwendacz" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Szwendacz</span></a></span> I think <a href="https://infosec.space/tags/Antivirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Antivirus</span></a> and <a href="https://infosec.space/tags/Malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Malware</span></a> protection should be the sole responsibility of the <a href="https://infosec.space/tags/maintainer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>maintainer</span></a> of said <a href="https://infosec.space/tags/OS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS</span></a> / <a href="https://infosec.space/tags/Distro" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Distro</span></a>!</p><p>And I'd happily pay for <a href="https://infosec.space/tags/support" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>support</span></a> and have that in writing for more than just <a href="https://infosec.space/tags/compliance" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compliance</span></a> reasons...</p><p>That being said <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> already dominates (<a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Android</span></a> is just a <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> + <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>musl</span></a> / <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> distro and for the vast majority of people - espechally in the global south, it is their <a href="https://infosec.space/tags/Desktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Desktop</span></a>!) and it <em>"solved"</em> the malware problem just by taking away <em>'the means to fuck up a system'</em> from <a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechIlliterate</span></a> <a href="https://infosec.space/tags/users" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>users</span></a> - <em>as any reasonable <a href="https://infosec.space/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysadmin</span></a> should do anyway</em>...</p><ul><li>Something that may not work <em>at all</em> on <a href="https://infosec.space/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macOS</span></a> and espechally on <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows</span></a> due to it not having permission managment and actual security in it's design!</li></ul><p>So yeah, 3rd party <a href="https://infosec.space/tags/AV" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AV</span></a> may seem like <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Scareware</span></a> on <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> (and <a href="https://infosec.space/tags/Mailservers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mailservers</span></a> should at least <a href="https://infosec.space/tags/ClamAV" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ClamAV</span></a> their inboxes) but on Windows they are absolutely pointless given than those are <a href="https://infosec.space/tags/BinaryBlob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BinaryBlob</span></a> - <a href="https://infosec.space/tags/Kernelhacks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kernelhacks</span></a> (none of them got Sourcecode access for Windows!) that actually lessen <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> of the System!</p><ul><li>I don't trust <a href="https://infosec.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> and thus I don't use Windows - period!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@jsrailton" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jsrailton</span></a></span> <a href="https://infosec.space/tags/Govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Govware</span></a> like <a href="https://infosec.space/tags/Pegasus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pegasus</span></a> isn't something that can be fixed outside of extensive <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ITsec</span></a>, <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoSec</span></a>, <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpSec</span></a> &amp; <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ComSec</span></a> workups.</p><p>In fact it's easier to bootstrap an entirely new identity than trying to uninstall such persistent shite!</p><p>That being said, <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VPN</span></a> providers are just the newest <a href="https://infosec.space/tags/DigitalSnakeoil" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalSnakeoil</span></a> sales reps and everything against them applies to <a href="https://infosec.space/tags/Antivirus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Antivirus</span></a> as well...</p><p>So sad that <span class="h-card" translate="no"><a href="https://mastodon.social/@tomscott" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tomscott</span></a></span> was just <a href="https://www.youtube.com/watch?v=WVDQEoe6ZWY" rel="nofollow noopener" target="_blank">naively debunking</a> them years ago...</p><p>The constant <a href="https://infosec.space/tags/disinfo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>disinfo</span></a> sown by VPN and <a href="https://infosec.space/tags/AV" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AV</span></a> providers is so rampant that I'd not be surprised if one day <em>both</em> would finally be made illegal <em>for all the right reasons</em>:</p><ul><li><p>A VPN <a href="https://mobile.twitter.com/thegrugq/status/1085614812581715968" rel="nofollow noopener" target="_blank">won't save peoples asses from getting jailed</a> !</p></li><li><p>Any 3rd party <a href="https://infosec.space/tags/Kernelhack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kernelhack</span></a>-<a href="https://infosec.space/tags/BinaryBlob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BinaryBlob</span></a> won't make one's <a href="https://infosec.space/tags/backdoored" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>backdoored</span></a> with Govware OS (regardless if <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows</span></a> or <a href="https://infosec.space/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macOS</span></a>) more secure, but rather less secure!</p></li><li><p>It should be the sole responsibility of the OS/Distro maintainers to make them secure by default, espechally on <a href="https://infosec.space/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOS</span></a> and <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Android</span></a> where users don't have administrative / <a href="https://infosec.space/tags/root" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>root</span></a> privilegues!</p></li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaos.social/@isotopp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>isotopp</span></a></span> not to mention the whole concept of paying a 3rd party that (outside of <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a>-based OSes like <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> and <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSD</span></a>'s!) won't habe Sourcecode access and accept their <a href="https://infosec.space/tags/BinaryBlob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BinaryBlob</span></a> <a href="https://infosec.space/tags/Kernelhack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kernelhack</span></a> is not only weird per concept but basically a digital <a href="https://infosec.space/tags/RacketeeringScheme" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RacketeeringScheme</span></a>!</p><p>In fact, it should be the <em>SOLE RESPONSIBILITY</em> of the <a href="https://infosec.space/tags/maontainers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>maontainers</span></a> to actually make their <a href="https://infosec.space/tags/OS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS</span></a> secure - period!</p><p>Everything else is just <a href="https://infosec.space/tags/bait" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bait</span></a> for the <a href="https://infosec.space/tags/Scareware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Scareware</span></a>-based sales pitch that fools <a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechIlliterates</span></a> into becoming victims of said racketeering scheme...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://meow.social/@odoben" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>odoben</span></a></span> Q: How would you do a <code>blobcat</code> command then?</p><p>Should it be like a <a href="https://infosec.space/tags/HexEditor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HexEditor</span></a> or what?</p><p>I mean, I know <em>why</em> you want a <a href="https://infosec.space/tags/cat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cat</span></a> for <a href="https://infosec.space/tags/BinaryBlob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BinaryBlob</span></a>|s and name it <a href="https://infosec.space/tags/blobcat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>blobcat</span></a>...</p><p>And I'd certainly add it to @OS1's <a href="http://github.com/OS-1337/pkgs" rel="nofollow noopener" target="_blank">repo</a> if it's <em>license permits it</em>...</p><p>Just let me know of it's <a href="https://infosec.space/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>git</span></a> so I can <a href="https://github.com/OS-1337/pkgs/blob/main/docs/WISHLIST.tsv" rel="nofollow noopener" target="_blank">add it to the wishlist</a>...</p>
Kevin Karhan :verified:<p><span class="h-card"><a href="https://social.stlouist.com/@nix" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>nix</span></a></span> <span class="h-card"><a href="https://mastodon.la/@pthenq1" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>pthenq1</span></a></span> <span class="h-card"><a href="https://octodon.social/@cwebber" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>cwebber</span></a></span> Personally, I think most of the demands from <a href="https://mstdn.social/tags/Guix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Guix</span></a> would be solved by using <a href="https://mstdn.social/tags/apt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>apt</span></a> or <a href="https://mstdn.social/tags/yum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>yum</span></a> and source packages as well as FLOSS-only repos.</p><p><a href="https://mstdn.social/tags/emerge" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>emerge</span></a> on <a href="https://mstdn.social/tags/Gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gentoo</span></a> basically can do the same as well...</p><p>The only issue I can see is that denying any <a href="https://mstdn.social/tags/binaryblob" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>binaryblob</span></a> will likely worsen <a href="https://mstdn.social/tags/UX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UX</span></a> since there is no system [i.e. laptop] on the market that doesn't require at least firmware for GPU and WiFi which they can't FLOSS for patent reasons and with WiFi are even forced to lock-down.</p>