hi,
after we upgrade our servers and client to 2.4.1 we detect many regressions.
- first was that with this the server no longer works and the server
restart fail after upgrade. imho it's not a safe behavior. but it was
easy to fix at least.
script-security 2 system
- then the new systemd unit
hi,
what is the current prefered way to report bug in openvpn?
trac? eg is there any chance to this will be fixed?
https://community.openvpn.net/openvpn/ticket/225
regards.
--
Levente "Si vis pacem para bellum!"
On 12/02/2010 12:10 PM, Matthias Andree wrote:
> Am 02.12.2010 10:46, schrieb Farkas Levente:
>> On 12/02/2010 10:05 AM, Adriaan de Jong wrote:
>>> Hi List,
>>>
>>> We've been working on OpenVPN in preparation for a security evaluation.
>>> This enta
On 12/02/2010 10:05 AM, Adriaan de Jong wrote:
> Hi List,
>
> We've been working on OpenVPN in preparation for a security evaluation. This
> entailed documenting OpenVPN at a relatively high level, removing the
> dependencies on OpenSSL, and adding support for a simpler, easier to evaluate
>
hi,
if i set in my server's config:
tls-server
and on the client's conf:
remote-cert-tls server
ns-cert-type server
then if i generate a new cert for the server and forget to set it to
server, then it's very hard to find out the problem. ie. neither from
the server nor the client's log file
any change to megre it into upstream openvpn?
On 09/26/2009 04:05 PM, Bernhard Schmidt wrote:
JuanJo Ciarlante wrote:
Hello JuanJo,
I'm(back) working on openvpn/ipv6 endpoint support, aka udp6/tcp6,
please refer to README.ipv6[1] and TODO.ipv6[2] for more details.
All
Carsten Krüger wrote:
> Hello,
>
>> wouldn't be it better to release the current version as 2.1 and all
>> upcoming bugfix can be put into post 2.1?
>
> +1
> But kick OpenVPN GUI from installer, it is unmaintained old crap (needs
> adminrights, didn't use management interface)
>
> Please set a
hi,
it's about 3 years since openvpn-2.1 is beta and almost everyone useing
the beta version since there is no final release.
wouldn't be it better to release the current version as 2.1 and all
upcoming bugfix can be put into post 2.1?
--
Levente "Si vis pacem
James Yonan wrote:
> Farkas Levente wrote:
>> James Yonan wrote:
>>
>>> 2006.09.12 -- Version 2.0.8
>>>
>>> * Windows installer updated with OpenSSL 0.9.7k DLLs to fix
>>> RSA Signature Forgery (CVE-2006-4339).
>>>
>
James Yonan wrote:
> 2006.09.12 -- Version 2.0.8
>
> * Windows installer updated with OpenSSL 0.9.7k DLLs to fix
> RSA Signature Forgery (CVE-2006-4339).
>
> * No changes to OpenVPN source code between 2.0.7 and 2.0.8.
>
> 2006.09.12 -- Version 2.1-beta15
hi,
is there any
hi,
is there any know bug in the current 2.1 beta tree? if not can we wait a
final release of 2.1 in the near future?
yours.
--
Levente "Si vis pacem para bellum!"
hi,
we now try to migrate from openvpn 1.x to 2.1 topology and we's a few
problems and comments about the new versions and a few questions.
we would like to give each client a fixed ip addresses and some of them
have an own subnet behind it. the server use the
server 192.168.254.0 255.255.255.0
James Yonan wrote:
OpenVPN Addressing Topology
---
However, now I've put together a brand new topology, called "topology
subnet". This topology is very intuitive, like the "dev tap" topology
where each client gets a single IP address from a pool, the server gets
the .1
hi,
i search the archive and see there are a few people who'd like to run
openvpn in his pocket pc. i just like to know is there any plan to port
openvpn to pocket pc too? this can be one of the main usage of openvpn
in the near future. since more and more people has some kind of pda
hi,
here is my small patch for the spec.in file in order not to overwrite
the old config files.
--- openvpn.spec.in.lfarkas 2004-03-31 18:11:14.0 +0200
+++ openvpn.spec.in 2004-03-31 18:13:25.0 +0200
@@ -34,9 +34,9 @@
%__install -c -m 755 %{name}.8
James Yonan wrote:
Farkas Levente <lfar...@bppiac.hu> said:
first of all THANKS!
James Yonan wrote:
* Add an internal routing capability to the OpenVPN server to allow
client-to-client communication, without going through the tun interface on the
server.
why this is needed? an
hi,
a few mounth ago I requested the redirect-gateway feature and James was
so kind to implement that feature. we use it but have to face another
problem. our windows 2000/xp road-warrior clinets are not so "road
warrior". this means that the clinets has a DSL connection over which
we use
hi,
a few mounth ago I requested the redirect-gateway feature and James was
so kind to implement that feature. we use it but have to face another
problem. our windows 2000/xp road-warrior clinets are not so "road
warrior". this means that the clinets has a DSL connection over which
we use
James Yonan wrote:
Farkas Levente <lfar...@bnap.hu> said:
Mathias Sundman wrote:
Hi!
> we use our linux vpn gateway and some win2000 road warrior clients with
> openvpn. I would like to route all internet traffic trough our firewall
> from the windows clients.
I´ve been
Mathias Sundman wrote:
Hi!
> we use our linux vpn gateway and some win2000 road warrior clients with
> openvpn. I would like to route all internet traffic trough our firewall
> from the windows clients.
I´ve been thinking about doing this too, but never accually tried it.
What you
20 matches
Mail list logo