Article idea: evemu
by Alessio Ciregia
Hello, I have a confused idea about a potentially useless but funny article.
evemu is a set of command line tools (in the fedora repo) useful "to
create a virtual input device and replay an event sequence".
As opposed to the similar command xdotool, a "command-line X11
automation tool", it works also on Wayland.
evemu (and xdotool) could be used to automate keystrokes. Maybe it is
a debugging tool (it can simulate also a mouse), but with a little
imagination it can be used to achieve useful as well as pointless
usages, i.e. automating some tasks simulating keystrokes, or hitting
casual keys on the keyboard in order to create jokes.
I'm still a bit confused.
Ciao,
A.
5 years, 7 months
Joining Fedora Magazine
by Francisco Vergara
Hello everyone!
My name is Francisco Vergara, I hail from the island of Puerto Rico were
Linux is an unknown and nonexistent topic. I've been using Fedora for over
10 years, and I would like to become a Fedora Magazine Writer.
Currently I work as a Front End Software Engineer and previously I did
graphic design and transcribed legal court recordings. I can share
knowledge on technologies like C#, .Net Core, Python, HTML, CSS, JS, Shell
Scripting, Visual Studio Code and Art Design using tools like Gimp,
Inkscape or Krita.
I'm learning Security, Networking and programming in ARM devices. Software
Security and White Hat hacking have always been a fascination of mine and
as I learn I could show others what I've learned on the way. I'm also
studying on how to use ARM devices so I can build irrigation systems and
drones that can monitor crops to help local agriculture to produce more.
Quite a lot that I want to learn,but Rome wasn't build in a day.
Finally i would like to make articles with novice tutorials so the average
Jane Doe or John Doe can switch to a Linux system like Fedora which
sometimes can be overwhelming.
Hope to meet your interest!
Kind Regards
Francisco Javier Vergara
5 years, 7 months
Editorial board meeting recap 2018-Aug-08
by Paul W. Frields
Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2018-08-08/magazine.2018...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2018-08-08/magazine.2018...
Log: https://meetbot.fedoraproject.org/fedora-meeting/2018-08-08/magazine.2018...
* * *
=========================================
#fedora-meeting: Magazine editorial board
=========================================
Meeting started by stickster at 20:00:16 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2018-08-08/magazine.2018...
.
Meeting summary
---------------
* Roll call (stickster, 20:00:19)
* Last week's stats (stickster, 20:04:02)
* Week of 2018-Jul-30: > 69.3K pageviews, up from almost 66.4K the
week previous (stickster, 20:04:53)
* Drafts to review (stickster, 20:11:37)
* LINK:
https://fedoramagazine.org/wp-admin/edit.php?post_status=draft&post_type=...
(stickster, 20:11:45)
* --- PMF article --- (stickster, 20:12:44)
* LINK: https://fedoramagazine.org/?p=21916&preview=1&_ppp=2d2ce4c0ad
(stickster, 20:12:46)
* --- Building RAID array using LVM --- (stickster, 20:22:02)
* LINK: https://fedoramagazine.org/?p=22196&preview=1&_ppp=dd09e02363
(stickster, 20:22:14)
* ACTION: sub_pop edit the RAID/LVM post, aim to complete by night of
Thu 2018-08-10 (USA timezones) (stickster, 20:27:37)
* ACTION: ryanlerch image for RAID/LVM post and schedule for Fri
2018-08-11 if possible (stickster, 20:27:53)
* --- fstransform --- (stickster, 20:28:28)
* LINK: https://fedoramagazine.org/?p=22143&preview=1&_ppp=a12ba6361a
(stickster, 20:28:30)
* ACTION: ryanlerch edit fstransform article and schedule
appropriately :-) (stickster, 20:31:44)
* ACTION: stickster copy edit PMF wifi article and image, and schedule
for Wed 2018-08-15 (stickster, 20:34:05)
* Pitches to approve (stickster, 20:34:25)
* --- evemu --- (stickster, 20:34:29)
* LINK:
https://lists.fedoraproject.org/archives/list/magazine@lists.fedoraprojec...
(stickster, 20:34:54)
* AGREED: evemu pitch is good to go (stickster, 20:37:20)
* ACTION: stickster email alciregi and list with approval and go to
draft (stickster, 20:37:30)
* Publishing schedule (stickster, 20:39:50)
* LINK: http://rhea-ayase.eu/articles/2018-08/LVM-RAID-on-Fedora
(ryanlerch, 20:41:22)
* ACTION: misc do article on [N] cool terminal pagers (stickster,
20:49:33)
* ACTION: smooge do article on [N] cool music players (stickster,
20:49:50)
* ACTION: pingou do article on [N] cool text-based email apps
(stickster, 20:49:59)
* AGREED: Fri 2018-08-10: N-best article (ryanlerch) -- Mon
2018-08-13: fstransform (ryanlerch) -- Wed 2018-08-15: PMF
(stickster) -- Fri 2018-08-17: TBA (stickster, 20:52:05)
* All other business (Open floor) (stickster, 20:52:13)
* FPL mattdm called out Magazine stats big-time in his keynote this
morning (stickster, 20:52:34)
Meeting ended at 20:56:45 UTC.
Action Items
------------
* sub_pop edit the RAID/LVM post, aim to complete by night of Thu
2018-08-10 (USA timezones)
* ryanlerch image for RAID/LVM post and schedule for Fri 2018-08-11 if
possible
* ryanlerch edit fstransform article and schedule appropriately :-)
* stickster copy edit PMF wifi article and image, and schedule for Wed
2018-08-15
* stickster email alciregi and list with approval and go to draft
* misc do article on [N] cool terminal pagers
* smooge do article on [N] cool music players
* pingou do article on [N] cool text-based email apps
Action Items, by person
-----------------------
* ryanlerch
* ryanlerch image for RAID/LVM post and schedule for Fri 2018-08-11 if
possible
* ryanlerch edit fstransform article and schedule appropriately :-)
* smooge
* smooge do article on [N] cool music players
* stickster
* stickster copy edit PMF wifi article and image, and schedule for Wed
2018-08-15
* stickster email alciregi and list with approval and go to draft
* sub_pop
* sub_pop edit the RAID/LVM post, aim to complete by night of Thu
2018-08-10 (USA timezones)
* **UNASSIGNED**
* misc do article on [N] cool terminal pagers
* pingou do article on [N] cool text-based email apps
People Present (lines said)
---------------------------
* stickster (101)
* ryanlerch (57)
* sub_pop (21)
* zodbot (13)
* atolstoy (7)
* smooge (2)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
5 years, 7 months
IRC channel spam
by Paul W. Frields
Hi folks, the Magazine IRC channel has been one of many, many Freenode
channels afflicted recently with spam. To try and combat this, I set
the "-q $~a" mode which means (as I understand from Fedora sysadmins)
unregistered nicks may not be able to "speak" in the channel.
If you are on the channel and you find you're getting warnings about
this, or you're having other trouble, ping me in a private message and
I'll see what I can do.
On the other hand, it's a VERY good idea to register your nick on
Freenode anyway. This also takes care of the problem. Here's how you
register: https://freenode.net/kb/answer/registration
Once you register, you can do either of these to identify yourself to
the IRC nickserv any time you get on IRC:
/MSG NickServ identify <mypassword>
/MSG NickServ identify <nick> <mypassword>
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
5 years, 8 months
Re: Reworking article
by Paul W. Frields
On Mon, Jul 30, 2018 at 03:45:10PM +0200, Davide Caratti wrote:
> On Wed, 2018-07-18 at 17:28 -0400, Paul W. Frields wrote:
> > Hi Davide,
> >
> > The Magazine editorial board reviewed the pitch/draft you submitted to
> > the Magazine about PMF. We liked the idea that this content helps
> > users solve a problem they may run into if they upgrade to Fedora 28.
> > However, it was also very detailed in ways that will probably deter
> > readers from reading the article.
>
> (cc-ing Francesco as he reviewed the post)
>
> sorry for answering late: I was on vacation in the last two weeks.
>
> I felt the need for adding some details on how to troubleshoot PMF on
> fedora, as we are receiving many bugzilla notifications from users
> experiencing wifi connectivity troubles, and almost all of them relate to
> PMF.
>
> All users restored connectivity by disabling PMF with nmcli, like I
> suggest at the end of the second chapter. Nevertheless, PMF is a security
> improvement and users should use it if the Access Point is advertising to
> be MFP-Capable.
>
> These problems are not a bug in wpa_supplicant. Most of the times they are
> caused by bugs in wireless drivers (specially Intel), Rarely, they are
> misconfigurations / bugs in the Access Point. In both cases, a software
> upgrade containing a fix will not probably happen in a short time.
>
>
> So, I tried to do a comprehensive text trying to anticipate the "WiFi
> sucks on Fedora" rant (before we see another 'WiFi sucks' rant, like it
> happened with [1]).
>
> > Could you rework this article to be simpler, and eliminating some of
> > the unnecessary technical details? We don't assume all users are
> > stupid. But on the other hand, readers have a limited attention span
> > according to our metrics, so the Magazine aims for higher readability,
> > and articles that focus on their problem and how to solve it.
> >
> > Let us know what you think.
>
> Stupid people just don't exist. Anyway, even though I can assume all
> readers can upgrade/downgrade an rpm, and see a wireless connection
> problem apperaing/disappearing, I'm not 100% sure they know how ciphers
> are negotiated between Access Points and clients in a managed BSS.
>
> after a fresh re-read, I think I can get rid of this paragraph
>
> <<
> Like other features in the 802.11 standard, PMF is designed to be
> backwards-compatible. It is possible to configure the desired PMF
> enforcement level, both on the Access Point and on the client, depending
> on the desired trade-off between protection and interoperability:
>
> PMF Disabled: no protection present, nor required.
> PMF Optional: protect only frames sent to nodes that advertise the PMF
> capability, and keep transmitting unprotected frames to other “legacy”
> nodes.
> PMF Required: only associate/accept association if the peer node is
> PMF-capable
>
> When a client associates to an AP, and both nodes have PMF enabled (with
> ‘Optional’ or ‘Required’), they will negotiate the cipher suite that is
> going to be used for MICs. Negotiation will be successful if the two nodes
> (usually the Access Point and the client) will agree on one of the ciphers
> belonging to the BIP (Broadcast Integrity Protection) Group Management
> suite. Within wpa_supplicant it’s possible to specify the algorithm among
> a set of available cipher suites, that are made available by the NIC
> hardware, or by the kernel crypto library, or both. All these information
> can be read in the RSN Information Element (i.e. the MFP Capable and the
> MFP Required bit in the RSN Capabilities subelement, and the BIP Group
> Management Suite listing the configured ciphers).
>
> >>
>
> We can remove it, many users read the system log and attach it to
> bugzilla; almost nobody attachs EAPOL traces (and it's not trivial to
> capture auth/deauth packets).
>
> Alternatively, I can publish this post "as-is" elsewhere, and write a
> small introductive chapter for fedora magazine.
>
> WDYT?
>
> thanks!
> --
> davide
>
> [1] http://blog.cerowrt.org/post/disabling_channel_scans/
Hi Davide, thanks for the note back. I think, based on your
explanation here, your second suggestion might be a better fit for the
magazine.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
5 years, 8 months
Comment moderation -- gathering tips
by Paul W. Frields
Hi Magazine editors,
I wanted to open up this conversation to share how I personally
moderate comments. I'm not unilaterally declaring any rules here.
I'd love to hear from other editors how they make these decisions. In
the end, I hope we can come up with common guidance that helps future
editors.
Which reminds me... Hopefully everyone does know that we do moderate
comments on the Magazine. We think of the Magazine as a place where
Fedora can put its best foot forward. That doesn't mean we don't take
critical comments. We definitely do, as long as they're in the spirit
of betterment. But just like a house party -- if you routinely let
guests spill others' drinks, very soon no one will bother to attend.
So we keep an eye on the party to ensure everyone can enjoy it.
Often I go through a mental checklist to see if a comment has some
quality that makes it unsuitable to publish. If a comment gets
through those gates, typically I approve it ("If it doesn't fail, it
passes."). These are the ones that I typically think about:
* Does the comment show obvious signs of spam? (Examples: Suspicious
website or email name, often coupled with highly generic comments
that have nothing to do with the article content.)
* Does the comment engage in rude or obnoxious behavior, like name
calling, ad hominem attacks, unconstructive criticism, or insults
against Fedora, people, other Linux distros, or open source
projects? (Examples: "The maintainers of <X> project should be
ashamed." "Fedora sucks, so I use $DISTRO instead." "$DISTRO sucks
so I always use Fedora now.")
* Does the comment lack clear discussion value? (Example: "This was a
great post, I learned a lot.")
These are three big ones I can think of. How do other editors treat
comments?
Are there other rules you use?
Are there things on this list you think we should *not* use to
disqualify comments?
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
5 years, 8 months