Re: Tool to live duplicate a small area of the screen on a separate window

2022-10-14 Thread Paul Smith
On Thu, Oct 13, 2022 at 10:31 PM Felix Miata  wrote:
>
> > I am trying to find a tool that live duplicates, on a separate window,
> > a region of the screen. I have searched for that, but with no luck.
>
> KMag.

Thanks, Felix, for the suggestion. Unfortunately, KMag shows the area
where the mouse pointer is, and what I am looking for is a tool that
shows on a window a *fixed* area, as if it were a small virtual
monitor with a view confined to that fixed area.

Paul
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Tool to live duplicate a small area of the screen on a separate window

2022-10-14 Thread Felix Miata
Paul Smith composed on 2022-10-14 13:08 (UTC+0100):

> On Thu, Oct 13, 2022 at 10:31 PM Felix Miata wrote:

>> > I am trying to find a tool that live duplicates, on a separate window,
>> > a region of the screen. I have searched for that, but with no luck.

>> KMag.

> Thanks, Felix, for the suggestion. Unfortunately, KMag shows the area
> where the mouse pointer is, and what I am looking for is a tool that
> shows on a window a *fixed* area, as if it were a small virtual
> monitor with a view confined to that fixed area.

I last used it a very long time ago. I thought it could be configured to do 
that.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Request for testing: fail2ban 1.0.1 update

2022-10-14 Thread Charlie Dennett
On Mon, Oct 3, 2022 at 2:57 PM Richard Shaw  wrote:

> I have disabled auto-stable based on time for the updates: I have
> submitted updates for f36 and up and EPEL 9.
>
> https://bodhi.fedoraproject.org/updates/?search=fail2ban
>
> I would like some sort of confirmation on the update itself or by direct
> communication that everything appears to be working properly.
>
> Fail2ban is somewhat fragile by nature and this is a big update.
>
>
Updated yesterday (10/13/22) to the latest 1.0.1 release on my F36 system.
Upon startup, fail2ban-server was using 100% of a cpu.  Tried removing the
sqlite database and restarting (also restarted iptables after stopping
fail2ban to remove all the blocks)  but that did not help.  Downgraded back
to 0.11.2 and the problem went away.

I will attempt to reinstall 1.0.1 and increase its verbosity to see if I
can discover anything.  It's just my home system.  Use it as my desktop and
I also have an apache web server running on it for my genealogy research.

Charlie
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Request for testing: fail2ban 1.0.1 update

2022-10-14 Thread Charlie Dennett
On Fri, Oct 14, 2022 at 9:55 AM Charlie Dennett  wrote:

>
>
> On Mon, Oct 3, 2022 at 2:57 PM Richard Shaw  wrote:
>
>> I have disabled auto-stable based on time for the updates: I have
>> submitted updates for f36 and up and EPEL 9.
>>
>> https://bodhi.fedoraproject.org/updates/?search=fail2ban
>>
>> I would like some sort of confirmation on the update itself or by direct
>> communication that everything appears to be working properly.
>>
>> Fail2ban is somewhat fragile by nature and this is a big update.
>>
>>
> Updated yesterday (10/13/22) to the latest 1.0.1 release on my F36
> system.  Upon startup, fail2ban-server was using 100% of a cpu.  Tried
> removing the sqlite database and restarting (also restarted iptables after
> stopping fail2ban to remove all the blocks)  but that did not help.
> Downgraded back to 0.11.2 and the problem went away.
>
> I will attempt to reinstall 1.0.1 and increase its verbosity to see if I
> can discover anything.  It's just my home system.  Use it as my desktop and
> I also have an apache web server running on it for my genealogy research.
>
> Sigh.  I stopped fail2ban (the 0.11 version), restarted iptables to flush
it out, upgraded fail2ban to 1.0.1 and started it.  No issues.  It started
up, rebanned what was in the database and settled right down.  Seems to be
working fine now.
-- 
Charlie
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: mailman on Fedora

2022-10-14 Thread Sjoerd Mullender

On 25/09/2022 20.54, Kevin Fenzi wrote:

On Fri, Sep 23, 2022 at 03:55:47PM +0200, Sjoerd Mullender wrote:

What's the deal with maintaining mailing lists on Fedora these days?

For years I've used mailman (first mailman2, now mailman3) on Fedora to
administer mailing lists.  In mailman3, you also need postorius to provide a
web interface to users and hyperkitty to provide mail archive support.

On Fedora 35, mailman2 isn't available anymore, so that's when I switched to
mailman3.  The original Fedora 35 did not have postorius, but that became
available later.  Hyperkitty on the other hand is not available on fedora
35.  I use an rpm that I built myself.

On Fedora 36, mailman3 can be installed, but both postorius and hyperkitty
(there it is in the repository) cannot.  They both depend on a too old
version of django.

On Fedora 37 (I know, not released yet, so any complaints should go to the
testing list) none of the packages can be installed since they all depend on
python 3.10 and F37 will come with 3.11.  The packages are actually the
unmodified F36 packages.

Do people use mailman3 on Fedora?  If so, how?


Sadly those packages are difficult to keep working and they have fallen
behind. :( I'm sure the maintainers would welcome help though if you can
work on them or help test fixes.


Should I invest time in getting it to work in a python virtual environment?
And how would that work with SELinux?


Well, up to you, but it would be nice to contibute to the packages and
get them working again.


This very mailing list (users@lists.fedoraproject.org) is managed with
mailman3, but does the system on which it runs run Fedora?


Nope, it's running on a RHEL7 vm. ;(

We would very much like to move it to a newer version however, and
if the Fedora version became available/working again we could look at
that.

kevin




I bit the bullet and took the challenge.

I have created RPMs for mailman3, hyperkitty, and postorius and got them 
to work on Fedora 36.  (Fedora 37 is a bridge too far at the moment 
because it uses Python 3.11.  This information is of course irrelevant 
for this list at this time ;-) ).
To get it to work, I had to update a lot of other RPMs as well.  This is 
the complete list:


hyperkitty-1.3.5.9-1.fc36.noarch.rpm
hyperkitty-doc-1.3.5.9-1.fc36.noarch.rpm
mailman3-3.3.5-0.1.fc36.noarch.rpm
postorius-1.3.6.9-1.fc36.noarch.rpm
python-django-haystack-docs-3.2.1-0.fc36.noarch.rpm
python-rjsmin-docs-1.2.0-0.fc36.x86_64.rpm
python3-django-compressor-4.1-0.fc36.noarch.rpm
python3-django-haystack-3.2.1-0.fc36.noarch.rpm
python3-django-mailman3-1.3.7.9-1.fc36.noarch.rpm
python3-flufl-bounce-4.0-0.fc36.noarch.rpm
python3-flufl-i18n-3.2-0.fc36.noarch.rpm
python3-flufl-lock-5.1-0.1.fc36.noarch.rpm
python3-mailman-hyperkitty-1.2.1-0.1.fc36.noarch.rpm
python3-mailmanclient-3.3.3-2.fc36.noarch.rpm
python3-mailmanclient-3.3.3-4.fc36.noarch.rpm
python3-mistune-2.0.4-0.fc36.noarch.rpm
python3-rcssmin-1.1.0-0.fc36.x86_64.rpm
python3-rjsmin-1.2.0-0.fc36.x86_64.rpm

All of these are based on the Fedora 36 source RPMs, but with updated 
sources and the occasional change in the patches used.  The hyperkitty 
and postorius versions are not based on official releases but just the 
latest sources.


I think perhaps the most problematic change is the update to the 
python3-mistune package.  F36 comes with 0.8.4 but mailman requires 2.0, 
and that's an incompatible rewrite if I understand correctly.


Since I have done minimal testing (one system, a single mailing list 
with one subscriber) it may not be ready for prime time yet.


Question is, how to proceed?  Since there are so many updated packages, 
who can I contact?


--
Sjoerd Mullender
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Request for testing: fail2ban 1.0.1 update

2022-10-14 Thread crow
I saw a similar problem in my f36 system.  100% CPU usage for the 
fail2ban-server process after upgrading to 1.0.1-1.  I also tried removing the 
sqlite database with no impact.  fail2ban-server was so busy it would not 
receive connections from fail2ban-client.  I enabled DEBUG logging, but that 
just showed that the process was so busy that everything was moving slower 
(e.g. jails that normally start immediately when the server starts did not 
start for minutes or longer).

I downgraded to 0.11.2-11 and all is good again.

Given the success of moving forward again reported here, I'll try the upgrade 
again this afternoon.

I'm all ears for advice on how to determine what the server is doing.  I didn't 
see any child processes and didn't immediately see any hints from open files 
that the process had.

David
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Request for testing: fail2ban 1.0.1 update

2022-10-14 Thread Richard Shaw
Interestingly, I did not have any issues, but I'm only running a sshd jail,
which is one of the reasons I wanted wider testing.

I verified that fail2ban was restarted (systemctl status fail2ban) and then
checked the status (fail2ban-client status sshd) and everything was fine.

I also did a tail -f on both the ssh log and the fail2ban log for a couple
of days and everything seemed fine.


Thanks,
Richard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: mailman on Fedora

2022-10-14 Thread Samuel Sieb

On 10/14/22 08:48, Sjoerd Mullender wrote:
Question is, how to proceed?  Since there are so many updated packages, 
who can I contact?


I suggest bringing this up on the devel list instead.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Tool to live duplicate a small area of the screen on a separate window

2022-10-14 Thread Tim via users
On Fri, 2022-10-14 at 13:08 +0100, Paul Smith wrote:
> Thanks, Felix, for the suggestion. Unfortunately, KMag shows the area
> where the mouse pointer is, and what I am looking for is a tool that
> shows on a window a *fixed* area, as if it were a small virtual
> monitor with a view confined to that fixed area.

Is it configurable, though?

Have you explored accessibility options?  Screen magnifiers?

Supposedly Gnome has something built-in, too, with an option about
following the mouse (the implication being you can do the opposite).

Likewise, Mate with Compiz has something.



 
-- 
 
uname -rsvp
Linux 5.19.14-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Oct 5 21:31:17
UTC 2022 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically
deleted.
I will only get to see the messages that are posted to the mailing
list.
 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: mailman on Fedora

2022-10-14 Thread Kevin Fenzi
On Fri, Oct 14, 2022 at 05:48:01PM +0200, Sjoerd Mullender wrote:
...snip...
> 
> Question is, how to proceed?  Since there are so many updated packages, who
> can I contact?

You might drop an email to Michel Alexandre Salim, Email: mic...@michel-slm.name
He's been working lately on bringing the mailman3 stack back and
working. I am sure he would appreciate the help. 

kevin


signature.asc
Description: PGP signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Tool to live duplicate a small area of the screen on a separate window

2022-10-14 Thread Roger Heflin
It might be overkill for this but obs-studio will do it.  You have to
create/add a screen grab and pick a window or do screen capture and
once picked and working in the preview window right click on the
preview and click windowed preview and size and place it.

On Fri, Oct 14, 2022 at 7:09 AM Paul Smith  wrote:
>
> On Thu, Oct 13, 2022 at 10:31 PM Felix Miata  wrote:
> >
> > > I am trying to find a tool that live duplicates, on a separate window,
> > > a region of the screen. I have searched for that, but with no luck.
> >
> > KMag.
>
> Thanks, Felix, for the suggestion. Unfortunately, KMag shows the area
> where the mouse pointer is, and what I am looking for is a tool that
> shows on a window a *fixed* area, as if it were a small virtual
> monitor with a view confined to that fixed area.
>
> Paul
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: VDQ : Ffx updates

2022-10-14 Thread stan via users
On Fri, 14 Oct 2022 05:04:04 +1030
Tim via users  wrote:

> Tim:
> >> And I can confirm the same thing on my PC using Fedora 36 (which is
> >> usually kept up to date every other day or so).  
> 
> Beartooth:
> > So it isn't me. That's some slight consolation. But how do
> > I know what repo it's getting all these mandatory instant updates
> > from?  
> 
> Are you sure it's Firefox, itself, that's updating?

This.  If firefox is coming from the fedora package, and you just
updated, then there should be no updates to firefox, as it will be
fully up to date.  If there is some kind of churn, it must be something
else.

It is good practice to shut down firefox before updating, and restart
it after the updates are done.  That way, if a library it depends on
has changed, it will get the new version.  Weird things can happen if
you run a program that was started with an older version of a library,
if you run it with a newer version, and it has changed.  Not always
crashes.  Gnome has mandated shutdown after update (reboot) to be sure
that this problem doesn't occur.  I just update from a console with
some programs closed, and haven't had any issues, but they have a valid
point.

Try creating a new user, and running a generic firefox after an
update. That is, without any addons or customization.  Does it still
have the same behavior?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: VDQ : Ffx updates

2022-10-14 Thread stan via users
On Fri, 14 Oct 2022 13:01:07 -0700
stan  wrote:

> On Fri, 14 Oct 2022 05:04:04 +1030
> Tim via users  wrote:
> 
> > Tim:  
> > >> And I can confirm the same thing on my PC using Fedora 36 (which
> > >> is usually kept up to date every other day or so).
> > 
> > Beartooth:  
> > > So it isn't me. That's some slight consolation. But how do
> > > I know what repo it's getting all these mandatory instant updates
> > > from?
> > 
> > Are you sure it's Firefox, itself, that's updating?  
> 
> This.  If firefox is coming from the fedora package, and you just
> updated, then there should be no updates to firefox, as it will be
> fully up to date.  If there is some kind of churn, it must be
> something else.
> 
> It is good practice to shut down firefox before updating, and restart
> it after the updates are done.  That way, if a library it depends on
> has changed, it will get the new version.  Weird things can happen if
> you run a program that was started with an older version of a library,
> if you run it with a newer version, and it has changed.  Not always
> crashes.  Gnome has mandated shutdown after update (reboot) to be sure
> that this problem doesn't occur.  I just update from a console with
> some programs closed, and haven't had any issues, but they have a
> valid point.
> 
> Try creating a new user, and running a generic firefox after an
> update. That is, without any addons or customization.  Does it still
> have the same behavior?

Before you go to the trouble of creating a new user (see man useradd),
you could try starting in safe mode.
/usr/bin/firefox -safe-mode
in a terminal.

There are more suggestions here:
https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Request for testing: fail2ban 1.0.1 update

2022-10-14 Thread Charles Dennett



On 10/14/22 13:07, Richard Shaw wrote:
Interestingly, I did not have any issues, but I'm only running a sshd 
jail, which is one of the reasons I wanted wider testing.


I verified that fail2ban was restarted (systemctl status fail2ban) and 
then checked the status (fail2ban-client status sshd) and everything was 
fine.


I also did a tail -f on both the ssh log and the fail2ban log for a 
couple of days and everything seemed fine.


I just checked fail2ban and it was once again pegged at 100% cpu and had 
missed several things I look for in the apache logs.  systemctl stop 
does not work and I have to manually kill the process.  FWIW, I ran an 
strace on the fail2ban-server process and it produces the following 
output that goes on until I stop the strace:


futex(0x7f819854cac8, FUTEX_WAIT_BITSET_PRIVATE, 0, {tv_sec=105267, 
tv_nsec=807769996}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection 
timed out)


futex(0x7f819854cad0, FUTEX_WAKE_PRIVATE, 1) = 0

futex(0x7f819854cac8, FUTEX_WAIT_BITSET_PRIVATE, 0, {tv_sec=105267, 
tv_nsec=812963592}, FUTEX_BITSET_MATCH_ANY) = -1 ETIMEDOUT (Connection 
timed out)


futex(0x7f819854cad0, FUTEX_WAKE_PRIVATE, 1) = 0

After this I disabled all jails and restarted fail2ban.  Then one by one 
I enabled them in jail.local.  After enabling a jail I did a 
fail2ban-client add, then a fail2ban-client start and a fail2ban-cleint 
restart.  The latter is what allowed it reban past events.  Everything 
went fine as I reenabled my sshd and all the various apache jails. 
Finally, I did my dovecot jail.  Bang!  As soon as I did the fail2ban 
restart on it the fail2ban server process went to 100%.  Right now I 
assume something is wrong with the dovecot jail.


I then stopped fail2ban.  I disabled just the dovecot jail and restarted 
fail2ban.  It seems to be working as expected.  I'll let it run 
overnight and check in in the morning.  Then I'll see if I can figure it 
out.  At first glance the latest fail2ban  dovecot.conf has a new macro 
called _auth_worker_info.  There may be more but I'll check that more 
thoroughly tomorrow.  Maybe just restore the older doveconf.conf from a 
backup and see if it works.


Charlie
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


How do I build a custom kernel with modules signed.

2022-10-14 Thread Sharpened Blade via users
I am building a kernel from the fedora `kernel.spec` file and SRPM. It works as 
good as the official kernel, but nothing in it is signed. I know that I can 
sign the kernel RPM package, but what about the kernel itself (for secure 
boot). The Fedora kernel is signed on a separate system, but I can not find any 
docs for it. I know that I cant use Fedora's keys, but what about signing it 
with my keys, then adding those keys to the shim.

I am trying to make it so that a user starting on a fresh install can use the 
kernel by adding the public keys to the shim, then installing the kernel RPM. I 
also want the modules to be signed with my key (I don't care if it is the same 
key that used for the rest of the kernel). I do not mean signing the RPM 
packages, but the binaries that are installed from the RPM package. I also do 
not want to have to signed the installed binaries with a per install key 
locally. 

tl;dr: I want to make kernel RPM package that is exactly the same as the Fedora 
package, but I compile it, and it uses my signing keys. I also want to be able 
to distribute this in the same way as the Fedora package, but with the user 
adding the key to the shim.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue