Bug 13066 - OpenVPN N2N - After import the Client Package file the warning “Expired” appears
Summary: OpenVPN N2N - After import the Client Package file the warning “Expired” appears
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - Aesthetic Issue
Assignee: Peter Müller
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-21 16:31 UTC by iptom
Modified: 2023-04-18 16:39 UTC (History)
4 users (show)

See Also:

Attachments
The warning “Expired” appears (18.03 KB, image/png)
2023-03-21 16:32 UTC, iptom 		Details
No reaction after clicking “Show file” (17.69 KB, image/png)
2023-03-21 16:32 UTC, iptom 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description iptom 2023-03-21 16:31:16 UTC 
CU174 Development Build: master/11f4726b

Client side
after importing the Client Package file of the n2n connection:

- The warning “Expired” appears
- Only the .p12 file appears in the /var/ipfire/ovpn/certs/ folder
- No reaction after clicking “Show file”

For more information, see the link below
https://community.ipfire.org/t/test-ipfire-cu174/9474/60?u=tphz
Comment 1 iptom 2023-03-21 16:32:01 UTC 
Created attachment 1142 [details]
The warning “Expired” appears
Comment 2 iptom 2023-03-21 16:32:25 UTC 
Created attachment 1143 [details]
No reaction after clicking “Show file”
Comment 3 Adolf Belka 2023-03-21 21:29:34 UTC 
Specific components should only be selected for IPFire 3.x
Comment 4 Erik Kapfer 2023-03-23 13:48:49 UTC 
There is also an already existing bug id for this --> https://bugzilla.ipfire.org/show_bug.cgi?id=13035 .

Best,

Erik
Comment 5 Adolf Belka 2023-03-23 14:38:54 UTC 
(In reply to Erik Kapfer from comment #4)
> There is also an already existing bug id for this -->
> https://bugzilla.ipfire.org/show_bug.cgi?id=13035 .
> 
> Best,
> 
> Erik

That bug is unrelated to this bug.

This bug is about n2n certificates being flagged up as expired when they are not linked to a patch that was only merged into CU174 Testing.

Bug13035 is about a person having problems with making a connection WITHOUT 2FA in CU172.
The 2FA was released into CU169.

I have not had any problems with existing or new connections without any 2FA since the 2FA code was introduced.

So that bug has nothing to do with the expired flagging of certificates.
Comment 6 Erik Kapfer 2023-03-23 15:04:05 UTC 
(In reply to Adolf Belka from comment #5)
> (In reply to Erik Kapfer from comment #4)
> > There is also an already existing bug id for this -->
> > https://bugzilla.ipfire.org/show_bug.cgi?id=13035 .
> > 
> > Best,
> > 
> > Erik
> 
> That bug is unrelated to this bug.
> 
> This bug is about n2n certificates being flagged up as expired when they are
> not linked to a patch that was only merged into CU174 Testing.
> 
> Bug13035 is about a person having problems with making a connection WITHOUT
> 2FA in CU172.
> The 2FA was released into CU169.
> 
> I have not had any problems with existing or new connections without any 2FA
> since the 2FA code was introduced.
> 
> So that bug has nothing to do with the expired flagging of certificates.

Sorry this was the wrong link, meant this one --> https://bugzilla.ipfire.org/show_bug.cgi?id=11742 .
Comment 8 Michael Tremer 2023-04-11 12:46:59 UTC 
This looks good to me.