search for: exhcange

...ranks[@nexts_number] @user.send(@next_type) += 1 @user.send(type) @user.save_with_validation(false) flash[:notice] = "Exchange complete." else flash[:notice] = "Exchange not met." end redirect_to :action => "upgrade" end Here is usage: <%= link_to ''exhcange strong for super strong'', :action => "exch_link", :type => "s" %> # s is for strong. -- Posted via http://www.ruby-forum.com/.

Can we disable diffie-hellman-group14-sha1 too? On Thu, Feb 14, 2019 at 10:23 PM Mark D. Baushke <mdb at juniper.net> wrote: > > Hi John, > > The short answer is YES. > > Jon DeVree <nuxi at vault24.org> writes: > > > I ask because the removal of diffie-hellman-group-exchange-sha1 happened > > accidently in 7.8 due to a mistake in a change to

I wrote two scripts, which you can use with the stats plugin enabled to get a better "doveadm stats top" than it currently is: http://dovecot.org/tools/stats-top.pl http://dovecot.org/tools/stats.pl

Its not for us. We migrated from our nt4 pdc to samba pdc last night with good outcomes as far as our clients but our exchange server no longer works. It failed initially as we did not have the" log on as a service user" (not strictly true, we had administrator but it didn't work for some reason) After we got a working service user then got "service specific error

...<koops1997 at gmail.com> writes: > > > Can we disable diffie-hellman-group14-sha1 too? > > It is possible to disable the diffie-hellman-group14-sha1 key exchange, > but I personally recommend you just put it at the end of the list, so it > is not normally used for the key exhcange unless that is the ONLY thing > that your client has in common with the server (or vice versa). > > I know of a number of devices out there which want one of the MTI key > exchange methods to be used. > > -- Mark