If this paper is the one that I think it is, then I was one of the reviewers.
Their attack is neat, but it depends quite a lot on being able to
deterministically trigger deduplication. Their proof-of-concept exploit was on
Windows (and JavaScript attack was really fun) and I’m not convinced th
Hey,
Thanks for the CFT Craig.
2016-06-09 14:41 GMT+08:00 Xin Li :
>
>
> On 6/8/16 23:10, Craig Rodrigues wrote:
> > Hi,
> >
> > I have worked with Marcelo Araujo to port OpenBSD's ypldap to FreeBSD
> > current.
> >
> > In latest current, it should be possible to put in /etc/rc.conf:
> >
> > nis
Hello Adrian,
See attachments. One is with and one is without -ht option.
# 14:40:52 root@sjakie [~]
uname -a
FreeBSD sjakie.klop.ws 11.0-ALPHA1 FreeBSD 11.0-ALPHA1 #7 r300901M: Sat
May 28 16:54:00 CEST 2016
r...@sjakie.klop.ws:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64
Regards,
Ronal
Hey David,
I'm responding inline.
On Thu, Jun 09, 2016 at 09:18:40AM +0100, David Chisnall wrote:
> If this paper is the one that I think it is, then I was one of the reviewers.
> Their attack is neat, but it depends quite a lot on being able to
> deterministically trigger deduplication. Thei
Am Thu, 9 Jun 2016 09:18:40 +0100
David Chisnall schrieb:
> If this paper is the one that I think it is, then I was one of the reviewers.
> Their
> attack is neat, but it depends quite a lot on being able to deterministically
> trigger
> deduplication. Their proof-of-concept exploit was on Wi
On Wed, Jun 8, 2016 at 11:41 PM, Xin Li wrote:
>
> (I think the current implementation
> would do everything with plaintext protocol over wire, so while it
>
You are correct. This document http://puffysecurity.com/wiki/ypldap.html#2
states:
#
# ypldap cant use SSL or SASL...
# You
On 09/06/2016 18:34, Craig Rodrigues wrote:
> There is still value to ypldap as it is now, and getting feedback from
> users (especially Active Directory) would be very useful.
> If someone could document a configuration which uses IPSEC or OpenSSH
> forwarding, that would be nice.
>
> In future,
FreeBSD_HEAD_i386 - Build #3369 - Failure:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3369/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3369/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3369/console
Change summaries:
3
FreeBSD_HEAD_i386 - Build #3370 - Still Failing:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3370/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3370/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3370/console
Change summari
Hello Vitalij;
Hello.
After updating my system to 11.0-ALPHA2 #20 r301583
I'm found that at last some application is broken.
here backtrace for xterm
#0 0x0008022d48b4 in mbsrtowcs_l () from /lib/libc.so.7
[New Thread 804816000 (LWP 102346/)]
(gdb) bt
#0 0x0008022d48b4 in mbsrtowcs_
10 matches
Mail list logo