search for: icx

when check java process lock statistics, plockstat failed, please see below: # prstat -mLp 21162 PID USERNAME USR SYS TRP TFL DFL LCK SLP LAT VCX ICX SCL SIG PROCESS/LWPID 21162 7677 0.9 0.1 0.0 0.0 0.0 99 0.0 0.3 83 89 215 0 java/81 21162 7677 0.3 0.1 0.0 0.0 0.0 0.0 99 0.2 106 33 305 0 java/35 21162 7677 0.1 0.0 0.0 0.0 0.0 100 0.0 0.1 79 6 85 0 java/59 21162 7677 0.1 0.0 0.0 0.0 0.0 100 0.0 0.0 51 2 63...

[Just starting out with DTrace and was hoping to get some guidance.] I have a "benchmark" program that I monitored with both prstat (prstat -mL -P <PID>) and pfilestat (from the DTrace toolkit). Prstat reports LAT values in the 0.1-0.2% range, but pfilestat reports "waitcpu" values in the 6-10%. Since those two numbers supposedly represent time waiting for the CPU,

...ecast issue: > >For those who have a burning need to 'patch < patch', or just don't >want to type three lines into client.c, I've attached a small >patch to client.c (Icecast 1.3.11). >Simplicity is thy name. >(More specific: It's the suggested patch in the icx.c exploit, with > an added logging flag.) > >Thanks to Diz for making this public. > >.Neeko Oni -------------- next part -------------- LS0tIGNsaWVudC5jICAgIFdlZCBBdWcgIDEgMTY6MDY6NTMgMjAwMQorKysgc3JjL2NsaWVudC5j ICAgICAgV2VkIEFwciAgMyAxMjozNjoyMyAyMDAyCkBAIC0xMDMsNiArMTAzLDExIEBA...

...and if people want to test their local systems against this bug..you can aquire the exploit at: (it should be noted that this version of the exploit is just meant for linux x86 targets. This does not mean this bug is not exploitable on other platforms) http://www.packetstormsecurity.nl/filedesc/icx.c.html <p>ltr, diz -------------- next part -------------- A non-text attachment was scrubbed... Name: icecast.txt Type: application/octet-stream Size: 4808 bytes Desc: icecast.txt Url : http://lists.xiph.org/pipermail/icecast/attachments/20020406/885b462f/icecast.obj

Note that 'intel 2022' is a bit vague. The current version is 2023.1.0, and that has both the 'classic' (icc/icpc/ifort which it seems you used) and new (icx/ixpx/ifx) compilers -- the former are said to be going to be discontinued later this year. R did not know about ifx so did not build with the new set. The parts of the manual Tomas referred to were about the old compilers: the manual has now been re-written in R-devel and R-patched to major on...

...t and just run it as root. Hence the designation remote shell/root. If not running with uid 0 it will yield a shell with the uid/gid of the icecast user. The vendor has been notified via a cc of this mail. Fixing is easy so I expect they will release patches shortly. See the attached exploit (icx.c) for further details. diz -- #temp eww..so that's what full disclosure feels like... <p>----- End forwarded message ----- --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to &...

Ok, the Zhone sucks and the Adtran 750/850 seems to be a little too expensive. Can anyone recommend a decent channelbank that won't break the bank? TIA, -- Troy Settle Pulaski Networks http://www.psknet.com 540.994.4254 ~ 866.477.5638 Pulaski Chamber 2002 Small Business Of The Year

...ion of iconv()). * tiff(type = "quartz") (the default on macOS) now warns if compression is specified: it continues to be ignored. INSTALLATION on a UNIX-ALIKE: * There is some support for building with Intel's LLVM-based compilers on x86_64 Linux, such as (C) icx, (C++) ipcx and (Fortran) ifx from oneAPI 2023.x.y. * There is support for using LLVM's flang-new as the Fortran compiler from LLVM 16.0.x (preferably 17.0.0 or later). UTILITIES: * R CMD check reports the use of the Fortran 90 random number generator RANDOM_NUMBE...

...ion of iconv()). * tiff(type = "quartz") (the default on macOS) now warns if compression is specified: it continues to be ignored. INSTALLATION on a UNIX-ALIKE: * There is some support for building with Intel's LLVM-based compilers on x86_64 Linux, such as (C) icx, (C++) ipcx and (Fortran) ifx from oneAPI 2023.x.y. * There is support for using LLVM's flang-new as the Fortran compiler from LLVM 16.0.x (preferably 17.0.0 or later). UTILITIES: * R CMD check reports the use of the Fortran 90 random number generator RANDOM_NUMBE...

...ion of iconv()). * tiff(type = "quartz") (the default on macOS) now warns if compression is specified: it continues to be ignored. INSTALLATION on a UNIX-ALIKE: * There is some support for building with Intel's LLVM-based compilers on x86_64 Linux, such as (C) icx, (C++) ipcx and (Fortran) ifx from oneAPI 2023.x.y. * There is support for using LLVM's flang-new as the Fortran compiler from LLVM 16.0.x (preferably 17.0.0 or later). UTILITIES: * R CMD check reports the use of the Fortran 90 random number generator RANDOM_NUMBE...

...com (Jack Moffitt) To: cvs@icecast.org Subject: cvs commit: icecast/src avl_functions.c source.c X-Spam-Status: No, hits=-3.2 required=10.0 tests=UNIFIED_PATCH,NO_MX_FOR_FROM version=2.11 jack 02/04/10 14:36:27 Modified: src avl_functions.c source.c Log: Fix security exploit (icx.c) that exploited a buffer overflow in the alias logic. Revision Changes Path 1.9 +4 -4 icecast/src/avl_functions.c Index: avl_functions.c =================================================================== RCS file: /cvsroot/icecast/src/avl_functions.c,v retrieving revision 1.8...

...com (Jack Moffitt) To: cvs@icecast.org Subject: cvs commit: icecast/src avl_functions.c source.c X-Spam-Status: No, hits=-3.2 required=10.0 tests=UNIFIED_PATCH,NO_MX_FOR_FROM version=2.11 jack 02/04/10 14:36:27 Modified: src avl_functions.c source.c Log: Fix security exploit (icx.c) that exploited a buffer overflow in the alias logic. Revision Changes Path 1.9 +4 -4 icecast/src/avl_functions.c Index: avl_functions.c =================================================================== RCS file: /cvsroot/icecast/src/avl_functions.c,v retrieving revision 1.8...

...% z7;%lu8oyJ>gM at Wkv`n{_sp52FwXRVBG|wgV0($G#QZImX6b(|3lcXNPtsxu~645uH zGQMe)4B<+A2q)c8>>W)yTStYiXz!v-I$B|wAaaXGq|d)3l99NNCL{6HUSg=5L%2kV zGLZUev^CEzbh%b<XWc5bDj8d;R;6MqsPg)0KLX~ydJExuxmm;Ms86x^iCS#FiRWsg z7_()uIb195rib_P&;f3)LD*WrI>36s2EazZCcsxnw;9hZfR6!HfCL~3NCCD2ssS~C zTEI5ICxGpM9e|yHT}E-YE5iqPXg4=M#rJN&9>Dv6y?}jy{RZ)~n}_!QE1dm2w1=Aq z4ElG_C}QRzqfMP;er9xRZXPx|wlI$v9j`Et8Xd1Rj~N|Xnx7jTo0-Rrj#rr{jE+~E zUl?uTl6lhT*vkCU=y;9!mC^B9^OVuC(EQryc%6Bg-p<h5H%7<n&9g?w*5)~*W0Co- z(Xmap7U4Z&qm1V2l>2O*a-YyC_i=pFm4q4z7FtN!K=N#Z8mgjal^UvbPc+AB)liB8 zQ)*}jJ$I<~)b...

I have linux kernel 2.4.0, openssl 0.95a installed to /usr/local/ssl. ./configure errors with: ./configure --with-openssl=/usr/local/ssl --with-openssl-include=/usr/local/ ssl/include --with-openssl-lib=/usr/local/ssl/lib ....... checking for SHA1_version in -lcrypto... no configure: error: It seems like OpenSSL is not installed on this system. Tried setting vars OPENSSL_DIR and SSL_BASE, still