Bug 457368 - Suggestion for adding the feature of panic firewall mode on
Summary: Suggestion for adding the feature of panic firewall mode on
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Vaults widget (show other bugs)
Version: 6.0.0
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-01 11:15 UTC by Emanuele Spirito
Modified: 2025-01-16 19:16 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
signature.asc (833 bytes, application/pgp-signature)
2022-08-01 15:25 UTC, David
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Emanuele Spirito 2022-08-01 11:15:21 UTC
SUMMARY
I saw that while creating a new kvault one can choose to disable WiFi and Bluetooth connection during the period the kvault is open. I want to suggest a possible secure boost feature, that is adding the possibility to run the firewall in panic mode while the kvault is open. This should only require to run in Konsole a command similar to:
sudo firewall-cmd panic-on
Comment 1 Ivan Čukić 2022-08-01 11:56:36 UTC
Can you explain the difference to killing all the connections? (I've never used firewalld)
Comment 2 David 2022-08-01 15:25:09 UTC
Created attachment 151050 [details]
signature.asc

Ora me ne occupo!
Anche se francamente, mi sento un po' in imbarazzo... 🤣

On lunedì 1 agosto 2022 13:16:37 CEST you wrote:
> https://bugs.kde.org/show_bug.cgi?id=457368
> 
> Nicolas Fella <nicolas.fella@gmx.de> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |nicolas.fella@gmx.de
>             Product|kgpg                        |Plasma Vault
>            Assignee|kde@opensource.sf-tec.de    |ivan.cukic@kde.org
>           Component|general                     |general
> 
>
Comment 3 David 2022-08-01 17:52:52 UTC
(In reply to David from comment #2)
> Created attachment 151050 [details]
> signature.asc
> 
> Ora me ne occupo!
> Anche se francamente, mi sento un po' in imbarazzo... 🤣
> 


I do apologize, this reply was not meant for this thread
Comment 4 Emanuele Spirito 2022-08-02 06:06:26 UTC
(In reply to Ivan Čukić from comment #1)
> Can you explain the difference to killing all the connections? (I've never
> used firewalld)

There are many possible scenarios, for example one can have connections that are not included by the kill switch. Also one can have loopback or other internal connections..
Firewall panic ensures no packets go anywhere, either inbound or outbound
Comment 5 Emanuele Spirito 2022-08-02 06:06:51 UTC
(In reply to David from comment #3)
> (In reply to David from comment #2)
> > Created attachment 151050 [details]
> > signature.asc
> > 
> > Ora me ne occupo!
> > Anche se francamente, mi sento un po' in imbarazzo... 🤣
> > 
> 
> 
> I do apologize, this reply was not meant for this thread

No problem at all
Comment 6 Ivan Čukić 2022-08-02 07:34:30 UTC
@Emanuele Ok, cool. Will see what we can do here :)