search for: ctr

Hi, Is cipher "3des-ctr" supported by openssh? It is not mentioned in the list of supported ciphers in the man page of ssh_config: Thanks, Sunil Ciphers Specifies the ciphers allowed for protocol version 2 in order of preference. Multiple ciphers must be comma-separated. The supported ciphers are ''3des-c...

...more meaningful. Here are two examples using data(zelazo) from library(ISwR): > library(ISwR) > data(zelazo) > attach(zelazo) > zelazo $active [1] 9.00 9.50 9.75 10.00 13.00 9.50 $passive [1] 11.00 10.00 10.00 11.75 10.50 15.00 $none [1] 11.50 12.00 9.00 11.50 13.25 13.00 $ctr.8w [1] 13.25 11.50 12.00 13.50 11.50 > walk <- stack(list("active"=active, "passive"=passive, "none"=none, "ctr.8w"=ctr.8w)) > walk values ind 1 9.00 active [...rows deleted...] 23 11.50 ctr.8w I want to name the first column "...

Hello there, This series exposes NVIDIA's global performance counters for Tesla through the Gallium's HUD and the GL_AMD_performance_monitor extension. This adds support for 24 hardware events which have been reverse engineered with PerfKit (Windows) and CUPTI (Linux). These hardware events will allow developers to profile OpenGL applications. To reduce latency and to improve accuracy,

...w. Thanks in advance! Samuel Pitoiset (20): pm: prevent freeing the wrong engine context pm: fix a potential race condition when creating an engine context pm: remove pmu signals pm: remove unused nvkm_perfsig_wrap() function pm: reorganize the nvif interface pm: prevent creating a perfctr object when signals are not found pm: implement NVIF_PERFMON_V0_QUERY_DOMAIN method pm: allow to query signals by domain pm: change signal iter to u16 pm: use hardware signals indexes instead of user-readable names pm: allow to monitor hardware signal index 0x00 pm: add concept of sourc...

OpenSSH uses its own CTR mode implementation, correct? ?I seem to recall some discussion about why it hasn't/won't switch over to using OpenSSL's implementation, but I can't find the thread anymore. So... why doesn't OpenSSH use OpenSSL's CTR mode implementation? Thanks.

I have been using lme from nlme to do a 3-way anova with all the effects treated as random. I was wondering if someone could direct me to an example of how to do this using lmer from lme4. I have 3 main effects, tim, trt, ctr, and all the interaction effects tim*trt*ctr. The response variable is ge. Here is my lme code: dat <- data.frame(ge=ge,trt=factor(trt),tim=factor(tim),ctr=factor(ctr)) dat$grp = as.factor(rep(1, nrow(dat))) # dim(dat) = 216x5 w <- lme(ge ~ 1,data=dat, random = list( grp...

...aching package: 'ISwR' The following object(s) are masked from package:survival : lung > data(zelazo) > head(zelazo) $active [1] 9.00 9.50 9.75 10.00 13.00 9.50 $passive [1] 11.00 10.00 10.00 11.75 10.50 15.00 $none [1] 11.50 12.00 9.00 11.50 13.25 13.00 $ctr.8w [1] 13.25 11.50 12.00 13.50 11.50 > walk <- unlist(zelazo) > walk active1 active2 active3 active4 active5 active6 passive1 passive2 9.00 9.50 9.75 10.00 13.00 9.50 11.00 10.00 passive3 passive4 passive5 passive6 none1 none2 none3 none4...

If I have data: dat<-data.frame(a=rnorm(20),b=rnorm(20),c=rnorm(20),d=rnorm(20),site=rep(letters[5:8],each=5)) And want to plot like this: ctr<-1 for(i in c('a','b','c','d')){ png(file=paste('/tmp/plot_number_',ctr,'.png',sep=''),height=8.5, width=11,units='in',pointsize=9,res=300) print(ggplot(dat[,names(dat) %in% c('site',i)],aes(x=factor(site),y=dat[,i])...

..._INHERIT_REQ SEC_DESC_SACL_PROTECTED SEC_DESC_RM_CONTROL_VALID SACL Segmentation fault (core dumped) I did a little poking and it seems that the issue is here: source3/rpcclient/cmd_srvsvc.c: 384 case 502: 385 for (i = 0; i < totalentries;i++) 386 display_share_info_502(&info_ctr.ctr.ctr502->array[i]); 387 break; Sorry for the formatting. But the NDR code yanks out 35 SHARE_INFO_502* * entries* *but the array size NDR code calculates only 34. Since "totalentries" is one entry too big, it causes rpcclient to go past the end of the ctr502 array and SEGV....

...hd.pid debug3: /etc/ssh/sshd_config:13 setting TCPKeepAlive yes debug3: /etc/ssh/sshd_config:14 setting ClientAliveInterval 600 debug3: /etc/ssh/sshd_config:15 setting ClientAliveCountMax 3 debug3: /etc/ssh/sshd_config:16 setting MaxStartups 25 debug3: /etc/ssh/sshd_config:17 setting Ciphers aes256-ctr,aes192-ctr,aes128-ctr,chacha20-poly1305 at openssh.com,aes128-gcm at openssh.com,aes256-gcm at openssh.com debug3: ciphers ok: [aes256-ctr,aes192-ctr,aes128-ctr,chacha20-poly1305 at openssh.com,aes128-gcm at openssh.com,aes256-gcm at openssh.com] debug3: /etc/ssh/sshd_config:18 setting MACs hmac-sh...

When testing chacha20-poly1305, I noticed that aes-gcm is significantly faster than aes-ctr or aes-cbs with umac. Even on systems w/o aes-ni or other recent instruction set additions. And there seems to be consensus in the crypto community that AEAD ciphers are the way forward. As such, it promoting the AEAD ciphers to the head of the preference list looks like a good idea. That would...

Hi everyone, new to the list. My apologies if this issue has already been covered, but I am having the following problem with Samba: Using Windows XP as a client, I am trying to see a Solaris system as a server. Solaris is running Samba 2.4.2, and Windows 2000 sees it as a server without any problems. Windows XP, however, generates the error "The network name is no longer

...ds to cluster the 30 chips. However, I don't know how to run prcomp, and I don't know how to interpret it's output. If there are 30 data points in 1,000 dimensions each, do I have to provide the data in a 1,000x30 matrix or data frame (i.e. 1000 columns)? > data[1:5,1:5] x.HU.04h.Ctr.118.01.4.ctrl x.HU.04h.010.118.04.4.0.1 1 21 45 2 24 35 3 109 173 4 86 99 5 130...

On multiple core systems OpenSSH is limited to using a single core for all operations. On these systems this can result in a transfer being processor bound even though additional CPU resources exist. In order to open up this bottleneck we've developed a multi-threaded version of the AES-CTR cipher. Unlike CBC mode, since there is no dependency between cipher blocks in CTR mode we parallelize cipher block operations among multiple threads. Furthermore, since the AES_encrypt operations do not depend on the data to be ciphered we pre-generate the effective keystream. The main thread...

Hi OpenSSH team, I find a url http://www.gossamer-threads.com/lists/openssh/dev/42808?do=post_view_threaded#42808, which provides unofficial patch for FIPS Capable OpenSSH. I try it and it seems working for some cases. (BTW, I also find that aes128-ctr, aes192-ctr and aes256-ctr ciphers can't work in FIPS mode properly. The fips mode sshd debug info is as following. *************************** debug2: set_newkeys: mode 1 cipher_init: EVP_CipherInit: set key failed for aes128-ctr debug1: do_cleanup ?? debug3: PAM: sshpam_thread_cleanup e...

...-v01 at openssh.com,ssh-ed25519,ss h-rsa,ecdsa-sha2-nistp256-cert-v01 at openssh.com,ecdsa-sha2-nistp384-cert-v01@ openssh.com,ecdsa-sha2-nistp521-cert-v01 at openssh.com,ecdsa-sha2-nistp256,ecd sa-sha2-nistp384,ecdsa-sha2-nistp521 debug2: kex_parse_kexinit: chacha20-poly1305 at openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm at op enssh.com,aes256-gcm at openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,b lowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.l iu.se debug2: kex_parse_kexinit: chacha20-poly1305 at openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,...

...uot;/tmp/foo/libexec/sftp-server\" -D_PATH_SSH_KEY_SIGN=\"/tmp/foo/libexec/ssh-keysign\" -D_PATH_SSH_PKCS11_HELPER=\"/tmp/foo/libexec/ssh-pkcs11-helper\" -D_PATH_SSH_PIDDIR=\"/var/run\" -D_PATH_PRIVSEP_CHROOT_DIR=\"/var/empty\" -DHAVE_CONFIG_H -c cipher-ctr.c cipher-ctr.c:38: error: conflicting types for ?ssh_aes_ctr_iv? openbsd-compat/openssl-compat.h:71: note: previous declaration of ?ssh_aes_ctr_iv? was here cipher-ctr.c:117: error: conflicting types for ?ssh_aes_ctr_iv? openbsd-compat/openssl-compat.h:71: note: previous declaration of ?ssh_aes_ctr...

...debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc at lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc at lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md...

Attached is the very verbose ssh output. Just to be perverse, this time two nodes lost connectivity. The only thing I see is lines saying that the two connections are lost, although being honest I have no idea what everything else means. For reference, 8 ssh cinnections were being made at the same time for a 8x8mpi task. N.B., since the OS I am using does not have rsh, I am currently using the

...it: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc at lysator.liu.se,aes12 8-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc at lysator.liu.se,aes12 8-ctr,aes192-ctr,aes256-ctr debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160 at openssh.c...