similar to: ANNOUNCE: GSSLib support for OpenSSH (patch)

I?m working on an implementation of ?gssapi-with-mic? authentication for my AsyncSSH package and trying to get it to interoperate with OpenSSH. I?ve gotten it working, but there seems to be a discrepancy between the OpenSSH implementation and RFC 4462. Specifically, RFC 4462 says the following in section 3.4: Since the user authentication process by its nature authenticates only the client,

On Jan 17, 2017, at 9:57 AM, Douglas E Engert <deengert at gmail.com> wrote: > On 1/16/2017 2:09 PM, Ron Frederick wrote: >> I?m working on an implementation of ?gssapi-with-mic? authentication for my AsyncSSH package and trying to get it to interoperate with OpenSSH. I?ve gotten it working, but there seems to be a discrepancy between the OpenSSH implementation and RFC 4462.

(I hope this message is appropriate for these lists. If not, please tell me and I won't do it again.) Hi All. There will be a new release of OpenSSH in a couple of weeks. This release contains Kerberos and GSSAPI related changes that we would like to get some feedback about (and hopefully address any issues with) before the release. I encourage anyone with an interest in

https://bugzilla.mindrot.org/show_bug.cgi?id=1654 Simon Josefsson <simon at josefsson.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon at josefsson.org --- Comment #3 from Simon Josefsson <simon at josefsson.org> --- Another idea is

http://bugzilla.mindrot.org/show_bug.cgi?id=357 Summary: SSH does not handle "Protocol" option in ~/.ssh/options properly Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo:

Hi! I’m running glmer (lme4) models with biodiversity data and I’m having trouble with understanding/finding information on how the offset() option is implemented. Explicitly, I’m wondering if the offset is only implemented on the dependent variable (as I think it is), or does it also affect independent variables in the model (was told this by a stat guy at our department)? My data is

--3Y2Mr1SP1gWKl0+e Content-Type: multipart/mixed; boundary="j9XQ5cF5hebrmXqw" Content-Disposition: inline --j9XQ5cF5hebrmXqw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! The netfilter coreteam proudly presents: iptables version 1.2.10 1.2.10 is (like most other 1.2.x releases) a maintainance release,

Hi, the IETF drafts had to be removed from the Debian package recently because IETF RFCs/drafts are (per default) not conformant to the Debian Free Software Guidelines, see <URL:http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390665>. It would be nice if Phil and Luca could dual-license the drafts under a DFSG-free license also ... most straight-forward would be libtheora's own

I think we're going to check in the autoconf-generated files on the release branches instead. On Wed, 17 Apr 2024, Simon Josefsson wrote: > Hi > > What do you think about publishing PGP signed tarballs without the > generated files such as the ./configure script? > > What I'm looking for is for some private key holder of the OpenSSH > portable release key to run

--5uhzMJlTksuFv+PE Content-Type: multipart/mixed; boundary="9A1A73/U17WN0PFw" Content-Disposition: inline --9A1A73/U17WN0PFw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! The netfilter coreteam proudly presents: iptables version 1.2.9 1.2.9 is (like most other 1.2.x releases) a maintainance release,

--va9XEZk9/dJ5GUjX Content-Type: multipart/mixed; boundary="vM12nk/63StVgfqY" Content-Disposition: inline --vM12nk/63StVgfqY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! The netfilter coreteam proudly presents: iptables version 1.2.9rc1 Version 1.2.9rc1 is the first release candidate of the upcoming 1.2.9

http://bugzilla.mindrot.org/show_bug.cgi?id=357 ------- Additional Comments From dfs at roaringpenguin.com 2002-07-18 00:56 ------- Sorry; my illustrated output for the second case was wrong. It should look like this: $ ssh -v -2 shevy OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f debug1: Reading configuration data /home/dfs/.ssh/config debug1: Applying options for * debug1:

this is the proposed gssapi diff against OpenSSH-current (non-portable). note: if this goes in, the old krb5 auth (ssh.com compatible) will be removed. please comment. jakob Index: auth.h =================================================================== RCS file: /home/hack/jakob/mycvs/sshgss/auth.h,v retrieving revision 1.1.1.2 retrieving revision 1.3 diff -u -r1.1.1.2 -r1.3 --- auth.h

On Apr 18 08:50, Simon Josefsson wrote: > Damien Miller <djm at mindrot.org> writes: > > > I think we're going to check in the autoconf-generated files on the > > release branches instead. > > Ok that may also achieve the same goal of reproducible release tarballs > built from source code. > > With that approach, the tarball depends on which autoconf

On 2024/04/18 10:06, Damien Miller wrote: > I think we're going to check in the autoconf-generated files on the > release branches instead. That seems a sane approach. > On Wed, 17 Apr 2024, Simon Josefsson wrote: > > and then publish the resulting openssh-9.7p1-src.tar.gz and > > openssh-9.7p1-src.tar.gz.asc files, preferably using a version of git > > that

Hi What do you think about publishing PGP signed tarballs without the generated files such as the ./configure script? What I'm looking for is for some private key holder of the OpenSSH portable release key to run git checkout V_9_7_P1 git archive --prefix=openssh-portable-V_9_7_P1/ -o openssh-9.7p1-src.tar.gz HEAD gpg --detach-sign --armor openssh-9.7p1-src.tar.gz and then publish the

Thomas Calderon <calderon.thomas at gmail.com> writes: > Hi, > > There is no need to add new mechanism identifiers to use specific curves. > > This can be done already using the CKM_ECDSA mechanism parameters (see > CKA_ECDSA_PARAMS > in the standard). > Given that the underlying HW or SW tokens supports Ed25519 curves, then you > could leverage it even with

On 10/8/2015 4:49 AM, Simon Josefsson wrote: > Mathias Brossard <mathias at brossard.org> writes: > >> Hi, >> >> I have made a patch for enabling the use of ECDSA keys in the PKCS#11 >> support of ssh-agent which will be of interest to other users. > > Nice! What would it take to add support for Ed25519 too? Do we need to > allocate any new PKCS#11

I was just wondering if anyone knows what could be the problem with my exporting of plots. Below is the error messages I get when trying to export my plots (all error messages at the same time). I do get a file produced which works but I don't know why these messages appear. Doesn't matter if it is a pdf or a png or any other format I export to. Also, when exporting to png I get

Hi! After bugzilla.netfilter.org went down on October 24 due to mysql database corruption during a system update, I have now finally found some spare time to investigate and fix the problem. I'm deeply sorry that it has taken that long, but my time to spend on netfilter is close to zero at this point (will increase in Q1/2007!) I'd like to also use this opportunity to thank the active