Check /etc/pam.d/sshd and see what's being loaded. Then, look for the
documentation on each of the PAM modules, and you should (if it's
properly documented, which almost all PAM modules seem to be) be able
to figure out which is doing the name check.
You haven't stated why you're averse to this c
Your server certificate isn't getting verified against the client's trust
store(myca.pem). This could be the case where the CA that signed the server
cert isn't present in the client's trust store. You can use Openssl's verify
command to check why this is happening.
-Sandeep
On Thu, Apr 29, 2010
wolfoftheair wrote:
>
> The question that I'd ask, though, is "do you know which component
> would do it? Is it perhaps a PAM in your system that is queried by
> the sshd to perform host-based blocking?"
>
I don't know which component do it exactly. Is there a way other than strace
to know it
On Wed, Apr 28, 2010 at 1:26 PM, Moshe, Kfir wrote:
> Since I’m working under Windows and have Visual Studio installed, the
> easiest way to do so will be by creating a visual studio project with the
> source code
>
> Has anyone ever did something like that, is there by a chance a prepared
> visu
Tank you Steve. so I will try that list. Strange this basic thing and no one
fixing this so far
Luis
> Date: Thu, 29 Apr 2010 13:20:59 +0200
> From: st...@openssl.org
> To: openssl-users@openssl.org
> Subject: Re: bad characters encoded on ssl logs coming from x509 cert
>
> On Thu, Apr 29,
* Modem Man wrote on Wed, Apr 28, 2010 at 17:49 +0200:
> > Since I'm working under Windows and have Visual Studio installed, the
> > easiest way to do so will be by creating a visual studio project with
> > the source code
>
> I tried it and stopped after ~4 hours.
[...]
> Next, split makefile int
On Thu, Apr 29, 2010, Luis Neves wrote:
>
> Please Steve,
>
> Can you give me any clue on were can I fix this '\x' translation? Should I
> post on Apache lists instead?.
> is openssl/mod_ssl utf8 aware? Im frustated!
It's Apache that is making the calls to deprecated functions so you shou
Please Steve,
Can you give me any clue on were can I fix this '\x' translation? Should I post
on Apache lists instead?.
is openssl/mod_ssl utf8 aware? Im frustated!
Should I quit and think on another solution... I never thought It was so hard
to deal with some certificates :(
regards,
Lui
Im stucked with this, and still no solution
I am reading client certificates and all utf8 characters are treated with '\x'
where in apache or openssl I can disable this? please.
Luis
From: luisne...@hotmail.com
To: openssl-users@openssl.org
Subject: RE: bad characters encoded on ssl log
hi:
Actually I got some error when connect ssl server by this way . I've created
a self-signed certificate
# openssl s_client -ssl3 -connect 127.0.0.1: -verify 10 -showcerts -cert
/home/myCA/certs/client.pem -key /home/myCA/private/client.pem -CAfile
/home/myCA/certs/myca.pem -msg -debug
>
10 matches
Mail list logo