Can I drop back to core 182

Networking
1

Where might I find core 182 ISO. Need to work around the “openssl producted error 256” when generating server certificate, but don’t understand the workaround I found posted online. Easier to just drop back to core 182 for time being

2

Or someone can explain what I am supposed to do with the following workaround (ie what am I actually supposed to type on the console):

$  diff ovpnmain.cgi ovpnmain.cgi.bak
1866,1870d1865
<             open(REQCNF, ">", "${General::swroot}/ovpn/openssl/ovpn.cnf.req");
<             my $lines = `cat "${General::swroot}/ovpn/openssl/ovpn.cnf"`;
<             $lines =~ s/authorityKeyIdentifier.*//g;
<             print REQCNF $lines;
<             close(REQCNF);
1876c1871
<                       '-config', "${General::swroot}/ovpn/openssl/ovpn.cnf.req" )) {
---
>
3

Have you read this post?

Best.

4

I found the older core 182 ISO in my downloads folder and re-installed. The article you reference is the one that originally led me down the path to wanting to re-install core 182. For anybody that has the same problem, dropping back to core 182 DOES work.

The workaround instructions (image included in my 2nd post) is greek to me and THAT is what I was asking if I could get some clarification/better instructions on.

5

Edit /var/ipfire/ovpn/openssl/ovpn.cnf
and remove the red marked lines from the [server] section.

https://git.ipfire.org/?p=ipfire-2.x.git;a=blobdiff;f=config/ovpn/openssl/ovpn.cnf;h=bfa7ad744c086aa54d83240c1b8fd23f3945f985;hp=96c3dcb09dbbe99354ee24370c9844f4570bd72a;hb=16d664b2bd4cb546cc2f1d5b7f36b2983f93f5d3;hpb=0c051ce27903e9d18c8ee247d92535c633ef93a2

3 Likes
6

The command,

diff ovpnmain.cgi ovpnmain.cgi.bak

only displays the differences between the left file ovpnmain.cgi and the right file ovpnmain.cgi.bak.

The results (see the < character) are telling the user those lines exist in the right file ovpnmain.cgi.bak and are missing from the left file ovpnmain.cgi

This command does not fix it only provides info for what might be the issue.

EDIT: Just got to Arne’s response and looks like he has the fix!

1 Like
7

I originally understood the diff command part, but didn’t remember that it displays the lines that differ between < … >. Am going to try Arne’s fix when I get onsite. I DO appreciate your response though. " It takes a community to raise a Linux programmer" kind of feeling.

1 Like