mastouille.fr est l'un des nombreux serveurs Mastodon indépendants que vous pouvez utiliser pour participer au fédiverse.
Mastouille est une instance Mastodon durable, ouverte, et hébergée en France.

Administré par :

Statistiques du serveur :

595
comptes actifs

#rubygems

0 message0 participant0 message aujourd’hui
Rad Web Hosting<p>How to Host Your Own <a href="https://mastodon.social/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mastodon</span></a> Server on a <a href="https://mastodon.social/tags/VPS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VPS</span></a> (5 Minute Quick-Start Guide) </p><p>This article provides a guide for how to host your own Mastodon server on a VPS.</p><p>Running your own Mastodon server on a VPS is an excellent way to enjoy an efficient and secure Mastodon experience.<br>What is Mastodon?<br>Mastodon is a <a href="https://mastodon.social/tags/decentralized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>decentralized</span></a> social media platform that enables users to post ...<br>Continued 👉 <a href="https://blog.radwebhosting.com/how-to-host-your-own-mastodon-server-on-a-vps/?utm_source=mastodon&amp;utm_medium=social&amp;utm_campaign=mastodon.social" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.radwebhosting.com/how-to-</span><span class="invisible">host-your-own-mastodon-server-on-a-vps/?utm_source=mastodon&amp;utm_medium=social&amp;utm_campaign=mastodon.social</span></a> <a href="https://mastodon.social/tags/rubyonrails" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rubyonrails</span></a> <a href="https://mastodon.social/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>selfhosting</span></a> <a href="https://mastodon.social/tags/activitypub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>activitypub</span></a> <a href="https://mastodon.social/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>selfhosted</span></a> <a href="https://mastodon.social/tags/rubygems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rubygems</span></a> <a href="https://mastodon.social/tags/installguide" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>installguide</span></a></p>
The New Oil<p>Malicious <a href="https://mastodon.thenewoil.org/tags/RubyGems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RubyGems</span></a> pose as <a href="https://mastodon.thenewoil.org/tags/Fastlane" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Fastlane</span></a> to steal 3Telegram API data</p><p><a href="https://www.bleepingcomputer.com/news/security/malicious-rubygems-pose-as-fastlane-to-steal-telegram-api-data/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">bleepingcomputer.com/news/secu</span><span class="invisible">rity/malicious-rubygems-pose-as-fastlane-to-steal-telegram-api-data/</span></a></p><p><a href="https://mastodon.thenewoil.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a></p>
alexanderadam<p>Do everybody a favour and block ruby-doc-dot-org wherever you can.</p><p><a href="https://mastodon.social/@jamesbritt/114378671981343723" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mastodon.social/@jamesbritt/11</span><span class="invisible">4378671981343723</span></a></p><p>Use any other <a href="https://ruby.social/tags/Ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ruby</span></a> documentation site that you like.</p><p><a href="https://ruby.social/tags/rubygems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rubygems</span></a> <a href="https://ruby.social/tags/ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ruby</span></a> <a href="https://ruby.social/tags/rubygem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rubygem</span></a> <a href="https://ruby.social/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a> <a href="https://ruby.social/tags/rubydoc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rubydoc</span></a></p>
Denis Defreyne<p>RubyGems is down :(</p><p><a href="https://ruby.social/tags/Ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ruby</span></a> <a href="https://ruby.social/tags/RubyGems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RubyGems</span></a></p>
postmodern<p>Is there a better way to determine if a gem is installed *and* it's C extensions are properly built? Currently I can only think of `ruby -r nokogiri -e ''`.<br><a href="https://ruby.social/tags/rubygems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rubygems</span></a></p>
postmodern<p>Is there any difference between `gem update already-installed-gem` and `gem install already-installed-gem`? Wondering if I can streamline this installation script that checks if a gem is installed and updates it, or installs it if not.<br><a href="https://ruby.social/tags/rubygems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rubygems</span></a></p>
Phylum<p>We have identified a nascent <a href="https://infosec.exchange/tags/malware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>malware</span></a> campaign targeting <a href="https://infosec.exchange/tags/ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ruby</span></a>, <a href="https://infosec.exchange/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>python</span></a> and <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>javascript</span></a> <a href="https://infosec.exchange/tags/developers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>developers</span></a>.</p><p>Packages collect information about the host machine before shipping details off to a remote server at `81.70.191.194`.</p><p>Read below for additional details!</p><p><a href="https://blog.phylum.io/malware-campaign-targets-npm-pypi-and-rubygems-developers/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.phylum.io/malware-campaig</span><span class="invisible">n-targets-npm-pypi-and-rubygems-developers/</span></a></p><p><a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>opensource</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/npm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>npm</span></a> <a href="https://infosec.exchange/tags/pypi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pypi</span></a> <a href="https://infosec.exchange/tags/rubygems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rubygems</span></a></p>
Caitlin Condon<p>Hey <a href="https://infosec.exchange/tags/RubyGems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RubyGems</span></a> users, we hear the frustration you've expressed to the site maintainers about the persistent <a href="https://infosec.exchange/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Google</span></a> <a href="https://infosec.exchange/tags/SafeBrowsing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SafeBrowsing</span></a> browser warnings on the metasploit-payloads gem page on rubygems.org. Unfortunately Google hasn't responded to the RubyGems team's plea to talk to a human, despite the fact that Metasploit payloads are basically the textbook definition of security research. <span class="h-card"><a href="https://fiasco.social/@indirect" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>indirect</span></a></span> and the <a href="https://infosec.exchange/tags/Metasploit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Metasploit</span></a> team have an issue open here to provide a forum for community discussion — please feel free to comment: <a href="https://github.com/rapid7/metasploit-payloads/issues/650" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/rapid7/metasploit-p</span><span class="invisible">ayloads/issues/650</span></a></p>
postmodern<p>Oh wow, I wasn't too far off! Some clown flagged the <a href="https://rubygems.org/gems/metasploit-payloads" rel="nofollow noopener noreferrer" target="_blank">metasploit-payloads gem</a> (which has been available on rubygems.org for <em>ages</em> without issue) and got <em>all of</em> <a href="https://rubygems.org" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="">rubygems.org</span><span class="invisible"></span></a> flagged by the Google Safe Browsing List!<br><a href="https://ruby.social/@indirect@fiasco.social/110351998871595312" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ruby.social/@indirect@fiasco.s</span><span class="invisible">ocial/110351998871595312</span></a></p><p>Granted the metasploit-payloads gem has far more exotic payloads which might trigger code scanners, but payloads are useless without an exploit. Absolutely no reason why payloads should be flagged as malicious.<br><a href="https://infosec.exchange/tags/metasploit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>metasploit</span></a> <a href="https://infosec.exchange/tags/rubygems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rubygems</span></a></p>
postmodern<p>Grumble. Somehow <a href="https://rubygems.org/" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="">rubygems.org/</span><span class="invisible"></span></a> got flagged by the Google Safe Browsing List. Yet <a href="https://nmpjs.com" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="">nmpjs.com</span><span class="invisible"></span></a> is somehow perfectly fine, despite constantly hosting typo-squated malware packages.<br><a href="https://transparencyreport.google.com/safe-browsing/search?url=https:%2F%2Frubygems.org%2F&amp;hl=en-US" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">transparencyreport.google.com/</span><span class="invisible">safe-browsing/search?url=https:%2F%2Frubygems.org%2F&amp;hl=en-US</span></a><br><a href="https://infosec.exchange/tags/googlesafebrowsing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>googlesafebrowsing</span></a> <a href="https://infosec.exchange/tags/rubygems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rubygems</span></a></p>
Hans-Christoph Steiner<p><a href="https://social.librem.one/tags/Decentralized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Decentralized</span></a> <a href="https://social.librem.one/tags/software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>software</span></a> repository systems like <a href="https://social.librem.one/tags/npm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>npm</span></a> <a href="https://social.librem.one/tags/maven" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>maven</span></a> <a href="https://social.librem.one/tags/rubygems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>rubygems</span></a> <a href="https://social.librem.one/tags/pypi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pypi</span></a> etc have key issues that make them hard to decentralize properly: solid verification is optional, one repo can override packages from another, and the tooling makes it hard to see which repo was actually used. <a href="https://social.librem.one/tags/MavenCentral" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MavenCentral</span></a> has additional measures which make it more trustworthy, but if devs add repos, those can still override it. <a href="https://social.librem.one/tags/Gradle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Gradle</span></a> verification helps a lot when using Maven repos but does not solve everything 1/2</p>
ITSec News deutschMit der Umstellung auf Multifaktor-Authentifizierung für die Top-Downloads folgt der Ruby-Paketmanger den Vorbildern npm und PyPI. <br><a href="https://www.heise.de/news/Paketmanager-RubyGems-org-Multifaktor-Authentifzierung-Pflicht-fuer-Top-Pakete-7222593.html" rel="nofollow noopener noreferrer" target="_blank">Paketmanager RubyGems.org: Multifaktor-Authentifzierung Pflicht für Top-Pakete</a><br>