mastodon.online is one of the many independent Mastodon servers you can use to participate in the fediverse.
A newer server operated by the Mastodon gGmbH non-profit

Server stats:

11K
active users

#WPA

1 post1 participant0 posts today

By WPA-era artist Albert Pels (1910-1998), Carnival Scene, oil on canvas, 29¾x39¾ inches (756x1010 mm), private collection. Photo: Swann Galleries, New York. #arthistory #WPA #oilpainting

From Wolfs Gallery, Cleveland: "Albert Pels was an art educator and painter of figures, genre scenes, urban and rural images, and illustration. He also did murals and worked in the mediums of oil, fresco, and watercolor."

Turn off WEP on your Galaxy S25 to increase security

One of the new features introduced in the brand new Samsung flagship, the Galaxy S25, allows you to determine whether your phone is allowed to connect to Wired Equivalent Privacy (WEP) Wi-Fi networks. Unfortunately, it’s turned on by default, despite the option that says that WEP is “an older security protocol that’s less secure.”

Over the years, people and security experts have constantly discouraged using WEP as a security protocol for Wi-Fi access points as it can be hijacked very easily due to weaknesses related to RC4 that were disclosed back in 2001. This document explained how such cipher, along with the initialization vector (IV), were exploited that resulted in a passive attack that could recover the RC4 key.

In general, WEP is insecure. Luckily, on your Galaxy S25, you can configure your smartphone to forbid connections to WEP-protected access points using this new configuration switch in the below menu:

Follow the steps to disallow connections to WEP networks:

  1. Open the Settings app
  2. Navigate to Connections > Wi-Fi > three dotted menu button > Advanced settings
  3. Toggle the Allow WEP networks entry off

Upon turning it off, your phone will no longer be able to connect to such networks. You’ll then be only able to connect to WPA-protected networks, especially those protected with WPA3. We recommend doing this after either obtaining the Galaxy S25 or updating your eligible device to One UI 7.

The best solution to those relying on those networks is to either switch to WPA3 protection if you’re managing them yourself, or contact your network administrator for more info. You can consult your router manual for more info about changing the network protection method.

Stone Steps in the Rock Garden

Stone steps wind upward, nestled between large, layered rock formations surrounded by lush trees and fallen leaves. Sunlight filters through the branches, creating a warm and inviting atmosphere amid the natural landscape.

Eagle Point Park
Dubuque, Iowa

#TravelPhotography #DubuqueIowa #EaglePointPark #GreatRiverRoad #WPA #rockgarden #stonesteps #photooftheday #fediverse #fediart

fineartamerica.com/featured/st

Ok HOW HARD CAN IT BE? 🤬

Currently trying to allow the #Windows machine I got from work (domain member, very much locked up, no local admin for me) in my private #wifi network (using 802.11x #authentication for #WPA with #freeradius and #PEAP using my own #samba based AD).

I don't strictly *need* it, the machine connects to my open guest wifi (mapped to a VLAN with access *only* to the internet), but it would be really nice being able to also access my local services while working at home.

What I tried:

- Just login (PEAP/MSCHAPv2), obviously. After lots of fiddling and reading logs (freeradius as well as windows events), I found some docs suggesting Windows doesn't support that any more unless you fiddle with something in HKLM, so, no dice, need something else...
- Allow EAP-TLS as well and issue a client certificate for my user, install that on windows. Doesn't work, the machine insists on using the machine cert from the machine store.
- Create a client cert with the UPN of my user in my home network in SAN ... same issue
- Create a client cert with the UPN of my *work* user in SAN ...
- Ok screw that, get freeradius to accept that stupid machine certificate: Allow the internal CA of my workplace and *only* the CN of exactly the machine certificate.

Now, it still won't work and I really don't get it, seeing stuff like:

(13) eap_tls: (TLS) TLS - recv TLS 1.3 Handshake, ClientHello
(13) eap_tls: (TLS) TLS - send TLS 1.1 Alert, fatal protocol_version
(13) eap_tls: ERROR: (TLS) TLS - Alert write:fatal:protocol version
(13) eap_tls: ERROR: (TLS) TLS - Server : Error in SSLv3 read client hello B

It makes little sense and all fiddling with TLS options so far didn't make it work. For other clients using PEAP, it just works with both TLS1.2 and TLS1.3. WTF is going on here?

Amongst #Federal bldgs that Team #DJT are offloading as surplus property is a #courthouse built in GA during the late 30's #WPA era. Renamed the J Roy Rowland Federal Courthouse in 1997, it currently houses U.S. District Court proceedings, the #FBI, the largely dormant and defanged Natural Resources Conservation Service and some #GSA offices . The building was named after a deceased six term #Democrat Rep, one of the rare medical doctor congressmen who passed in 2022, and during his career advocated for #Medicaid patients and the uninsured, creating a network of community health centers.

Dec 1, 1912: Jeanne Taylor was born on this date in St Paul, MN. She served in the Office of Strategic Services during WW2. An artist & leader of the Regionalist movement in MN, she painted scenes of the Midwest during the Great Depression & worked for the Works Progress Administration. Taylor was the lesbian partner of anthropologist and fellow OSS operative Cora Du Bois. She died Dec 2, 1992 at the age of 80.

en.wikipedia.org/wiki/Jeanne_T