Displaying 8 results from an estimated 8 matches for "sisal".
Did you mean:
nisal
2016 Feb 11
2
inconsistency in treatment of USE.NAMES argument
...earch.r:230
/rgbif/R/zzz.r:120
/rjstat/R/rjstat.R:75
/rlist/R/internal.R:155
/rnoaa/R/homr.R:140
/rnoaa/R/storm_shp.R:42
/roxygen2/R/template.R:27
/rplos/R/fulltext.R:29
/rplos/R/fulltext.R:82
/shiny/inst/tests/test-bootstrap.r:12
/shinyjs/inst/examples/demo/helpers.R:49
/simcausal/R/network.R:319
/sisal/R/sisalTable.R:806
/sisal/R/sisalTable.R:829
/sisal/R/sisalTable.R:853
/sisal/R/sisalTable.R:915
/sisal/R/sisalTable.R:924
/sisal/R/sisalTable.R:933
/stringdist/R/seqdist.R:130
/stringdist/R/stringdist.R:286
/surveillance/R/calibration_null.R:25
/surveillance/R/calibration_null.R:185
/surveillance/...
2016 Feb 08
2
inconsistency in treatment of USE.NAMES argument
Hi,
Both vapply() and sapply() support the 'USE.NAMES' argument. According
to the man page:
USE.NAMES: logical; if ?TRUE? and if ?X? is character, use ?X? as
?names? for the result unless it had names already.
But if 'X' has names already and 'USE.NAMES' is FALSE, it's not clear
what will happen to the names. Are they going to propagate to the
result
2007 May 19
2
PAM exec patch to allow PAM_AUTHTOK to be exported.
I figure some one here may find this interesting. I just begun work
on allowing a smb home directory to be automounted upon login.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pam_exec.c.diff
Type: text/x-patch
Size: 213 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-security/attachments/20070519/19e6bd01/pam_exec.c.bin
2006 Jun 18
7
memory pages nulling when releasing
Hello everyone!
Could you tell me if FreeBSD supports memory page nulling when
releasing it to prevent unauthorized access to data left in the page
after it's allocated again.
If it does, what sys calls etc provide that?
IMHO this is an important issue when operating data with different
sensivity levels.
Thanks in advance.
Nick
2006 Nov 11
5
src/etc/rc.firewall simple ${fw_pass} tcp from any to any established
Hi security@ list,
In my self written, large ipfw rule set, I had something that passed
http to allow me to browse most but not all remote sites. For years
I assumed the few sites I had difficulty with were cases pppoed MTU
!= 1500, from not having installed tcpmssd on my 4.*-RELEASE, but
then running 6.1-RELEASE I realised that wasn't the problem.
http://www.web.de Still failed, &
2006 Oct 11
2
[fbsd] HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon
> ----- Original Message -----
> From: sthaug@nethelp.no
> To: freebsd-security@dfmm.org
> Subject: Re: [fbsd] HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon
> Date: Wed, 11 Oct 2006 18:20:18 +0200 (CEST)
>
>
> > I realize that resources to keep chasing this stuff are in
> > limited supply, but if you solicit the opinion of the community,
> > I'd
2007 Jan 30
1
What about BIND 9.3.4 in FreeBSD in base system ?
http://www.isc.org/sw/bind/view/?release=9.3.4
SECURITY ADVISORIES
* CVE-2006-4095
CERT Vulnerability Note VU#915404
NISCC 172003
* CVE-2006-4096
CERT Vulnerability Note VU#697164
NISCC 172003
* CAN-2005-0034
NISCC-UNIRAS 20050125-00059
CERT Vulnerability Note VU#938617
[ODiP] == Dmitry Grigorovich
2006 Oct 01
4
HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Everyone,
On October 31st, FreeBSD 5.3 and FreeBSD 5.4 will have reached their
End of Life and will no longer be supported by the FreeBSD Security
Team. Users of either of those FreeBSD releases are strongly encouraged
to upgrade to FreeBSD 5.5 or FreeBSD 6.1 before that date.
In addition, the FreeBSD 6.0 End of Life is presently scheduled