My +1
- built from git and from packages
- signature checked
I insist that the packages should be pushed into
https://dist.apache.org/repos/dist/dev/mina/sshd/ with SHA256 and SHA512
signatures, as Maven only creates MD5 and SHA1 signatures that are not
anymore valid for The ASF.
Thanks
+1
>> I've staged a release candidate:
* Repo:
https://repository.apache.org/content/repositories/orgapachemina-1049
* Distributions:
https://repository.apache.org/content/repositories/orgapachemina-1049/org/apache/sshd/apache-sshd/2.5.0/
* Git Tag:
>> Days sounds good to me.
>> I can actually start the process today / tomorrow to get it out next
week if that's ok for everyone.
Fine by me...
On Wed, Jun 10, 2020 at 8:55 AM Guillaume Nodet wrote:
> Days sounds good to me.
> I can actually start the process today / tomorrow to get it out next week
> if that's ok for everyone.
>
That would be great, thanks a lot!
>
> Guillaume
>
> Le mar. 9 juin 2020 à 17:54, Lyor Goldstein a
>
Days sounds good to me.
I can actually start the process today / tomorrow to get it out next week
if that's ok for everyone.
Guillaume
Le mar. 9 juin 2020 à 17:54, Lyor Goldstein a
écrit :
> >> what's the expected timeframe to release 2.5.0? Is it a matter of days
> or weeks?
>
> Hopefully
The code has been changed a bit:
https://github.com/apache/mina-sshd/commit/aa551bc0ed07430ee768e98a57b75cd56f3927e0#diff-945f416b7cba28d68dc577da4f2b186eR217-R237
You need to use setForwardingFilter / setForwarderFactory instead.
Le ven. 18 mai 2018 à 13:11, pratap kumar raju
a écrit :
> Hi,
>> what's the expected timeframe to release 2.5.0? Is it a matter of days
or weeks?
Hopefully days (at least for me) - Guillaume, can you weigh in your opinion
on this ?
On Thu, Jun 4, 2020 at 5:27 PM Lyor Goldstein wrote:
> >> A bunch of new features / enhancements have been fixed in master since
> the last release a few months ago (end of january), so I think we should
> get 2.5.0 out.
>
> I am 100% in favor - as a matter of fact I was considering suggesting
>> A bunch of new features / enhancements have been fixed in master since
the last release a few months ago (end of january), so I think we should
get 2.5.0 out.
I am 100% in favor - as a matter of fact I was considering suggesting it
myself soon...
Using crypto in J11 and removing bouncycastle requires code changes. Not
sure how to do that other than branching.
On Mon, May 25, 2020 at 11:14 AM Matt Sicker wrote:
> By far the easiest way to do it is via a separate maven module. It just
> adds another jar dependency. Alternatively, you can
By far the easiest way to do it is via a separate maven module. It just
adds another jar dependency. Alternatively, you can use the maven
dependencies plugin to copy in code from another module to make an
aggregate one (how we package a multi version jar in log4j2 at least).
On Mon, May 25, 2020
Hi Matt,
we could modify the build to generate distinguish packages for the
various JAVA version (at least for the LTS supported versions, like
Java 11 and Java 14).
The thing is that we added some Jenkins tasks for Java 11 and 14n, and
MINA tests fail with those versions, so there are thing we
It appears that I assumed a ticket existed for this particular issue,
but it doesn't. This is about SSHD in particular. In order to support
the following:
https://issues.apache.org/jira/browse/SSHD-594
https://issues.apache.org/jira/browse/SSHD-811
https://issues.apache.org/jira/browse/SSHD-704
I’m not sure what Mina project or specific problem you’re referring to.
On Sun, May 24, 2020 at 12:22 PM Matt Sicker wrote:
> In order to support ChaCha20-Poly1305, Java 11 is required, or a backport
> of the cipher and mac to Java 8 like in Bouncycastle (whose java
> implementation is based on
>> Now our requirement is once we use SCP from this filezila,
winscp,putty then also we need to call same class and same method as above
for SFTP.
Why would you want to do that ? SSHD supports SCP no need to go through
SFTP...
SshServer server = SshServer.setupDefaultServer();
...more
If they do something like deferring the blocking operation on to a real
thread and use an async callback then the wasted cpu cycles is going to
shoot through the roof but that might be a trade off acceptable to some.
Uring was doing something similar using their worker thread model for AIO
and
I expected they would have to change the IO API in some way to hack that
together. It will be interesting to see what they actually had to change.
The IO API is already hugely inefficient as-is compared to calling the
native functions directly via JNI.
On Tue, May 19, 2020 at 11:49 AM Emmanuel
On 19/05/2020 17:25, Jonathan Valliere wrote:
Right, I’m not sure how loom is going to make any difference other than
being able to resource limit certain groups of threads. The problem With
virtual threads is pausing the thread during io; I’m not sure it is even
possible to do.
"The
Right, I’m not sure how loom is going to make any difference other than
being able to resource limit certain groups of threads. The problem With
virtual threads is pausing the thread during io; I’m not sure it is even
possible to do.
The cool idea of virtual threads would be that I could make a
On 19/05/2020 16:01, Jonathan Valliere wrote:
I’ll have to look at it but generally speaking virtual threads are not for
us because they cannot be paused during blocking operations within the
kernel space so you can’t have ten virtual threads blocked on a kernel
action on a single process
I’ll have to look at it but generally speaking virtual threads are not for
us because they cannot be paused during blocking operations within the
kernel space so you can’t have ten virtual threads blocked on a kernel
action on a single process thread.
Java once had “green” threads back in version
>> I have one requirement where I have to fetch public key from given
remote host and port, Can you please help me for that, Please point me for
any document, code snippet.
There is class that I believe already does this: see SshKeyScanMain
I think we should hold off on releasing 2.1.4 until these issues are
resolved.
On Sat, May 9, 2020 at 10:38 AM Emmanuel Lécharny
wrote:
> FTR it would be cool to create a pipeline for each branch, where we
> build in // the various JDK versions, like what we do for directory :
>
>
>
>
FTR it would be cool to create a pipeline for each branch, where we
build in // the various JDK versions, like what we do for directory :
https://builds.apache.org/blue/organizations/jenkins/dir-ldap-api-pipeline/detail/dir-ldap-api-pipeline/208/pipeline
We have defined docker images for
On 09/05/2020 14:53, Jonathan Valliere wrote:
This is consistent with what I’ve been experiencing. These issues do
not happen all the time.
Thanks for getting the tests running again. How do I access this
information normally without going through you?
You should be able to log in
This is consistent with what I’ve been experiencing. These issues do not
happen all the time.
Thanks for getting the tests running again. How do I access this
information normally without going through you?
On Sat, May 9, 2020 at 1:32 AM Emmanuel Lécharny
wrote:
> On 09/05/2020 01:04,
On 09/05/2020 01:04, Jonathan Valliere wrote:
I tried 2.1.2 earlier and that was intermittently failing on one or another
SSL test also. I’m going to have to look at it again. Either a socket bind
test or ssl test fails or hangs randomly on my side.
FTR, the build with Java 11 hanged on the
I tried 2.1.2 earlier and that was intermittently failing on one or another
SSL test also. I’m going to have to look at it again. Either a socket bind
test or ssl test fails or hangs randomly on my side.
On Fri, May 8, 2020 at 6:31 PM Emmanuel Lécharny
wrote:
> I'm also adding CI instances for
I'm also adding CI instances for Java 11 and 14, on both windows and linux.
On 09/05/2020 00:20, Emmanuel Lécharny wrote:
FTR, the latest 2.1.X build was successful :
https://builds.apache.org/view/M-R/view/MINA/job/MINA-2.1.X-jdk1.8-ubuntu/8/console
On 09/05/2020 00:07, Emmanuel
FTR, the latest 2.1.X build was successful :
https://builds.apache.org/view/M-R/view/MINA/job/MINA-2.1.X-jdk1.8-ubuntu/8/console
On 09/05/2020 00:07, Emmanuel Lécharny wrote:
On 08/05/2020 18:39, Jonathan Valliere wrote:
Do we have CI running for Mina on the primary branches? If so where
On 08/05/2020 18:39, Jonathan Valliere wrote:
Do we have CI running for Mina on the primary branches? If so where is the
daily reports?
We don't have daily builds, we have builds triggered on commits. Now,
the CI was badly configured, due to a change in the branches names : it
was
Well, I did some testing and GitHub _does_ have templates for pull requests
[1]. However, multiple
templates can only be accessed by adding the ?template parameter to the url
(which is not
something anyone wants to do). However, a pull_request_template.md template
created inside the
.github
It looks like issues tab is disabled but github marks pull requests as
issues so it was confusing. It also seems that github does not have
templates for pull requests like it does for issues otherwise we could note
in the template to link the request in JIRA.
On Thu, Apr 23, 2020 at 10:26 AM Roy
*Me not having read the completely thread and jumping in*
There is a possibility to disable GitHub repository features by using the
.asf.yaml.
It can be used to enable/disable the issues tab on GitHub:
We will need to figure out what changes should be backported to 2.0.X and
create a single ticket in jira (backport x,y) so we have that work logged
adequately comes time when something is accidentally broken we will know
where the change came from.
As you can see from the commit log I’m trying to
On 23/04/2020 15:42, jon-valliere wrote:
Is there any way to disable issues on github and force everyone to use
JIRA?
I don't think so.
The best is to kindly ask people to fill a JIRA pointing to the GH PR.
-
To
On 23/04/2020 10:44, Anna Kukliansky wrote:
You are right, this is exactly our goal. It's just that the new
NioAcceptor we implemented is a pretty simple extension over the
existing NioSocketAcceptor (which I'm changing here to support
inheritance), and it's a shame to duplicate all of the
Merge yours, I'll try another ackk (remove / add back) tomorrow.
Le mar. 21 avr. 2020 à 19:44, Lyor Goldstein a
écrit :
> >> >> Could you try with https://github.com/gnodet/mina-sshd/tree/SSHD-978
> and see if it's stable for you
>
> Works for me - except BCrypt.java seems to still require
>> >> Could you try with https://github.com/gnodet/mina-sshd/tree/SSHD-978
and see if it's stable for you
Works for me - except BCrypt.java seems to still require CRLF changes
somehow
I guess it will keep doing that every time we "ping pong" commits for it.
I therefore think since it is the
>> I can still see mixed lf / crlf in the BCrypt.java file, so I'll push
another commit to get rid of those.
I saw the same and tried to get rid of them - no success either
>> Could you try with https://github.com/gnodet/mina-sshd/tree/SSHD-978 and
see if it's stable for you
Will do - but if
>> When working on an existing repo and modifying the .gitattributes, you
may need to use the --renormalize option as indicated in
https://help.github.com/en/github/using-git/configuring-git-to-handle-line-endings#refreshing-a-repository-after-changing-line-endings
to
fix the line endings.
>>
ete the whole repo and re-clone it? I have no idea, I don’t use
> Windows for anything relating to work.
>
> On Mon, Apr 20, 2020 at 1:49 PM Lyor Goldstein
> wrote:
>
> > >> >>
> > https://stackoverflow.com/questions/21822650/disable-git-eol-conversions
&g
Did you delete the whole repo and re-clone it? I have no idea, I don’t use
Windows for anything relating to work.
On Mon, Apr 20, 2020 at 1:49 PM Lyor Goldstein
wrote:
> >> >>
> https://stackoverflow.com/questions/21822650/disable-git-eol-conversions
> >> >> Y
>> >>
https://stackoverflow.com/questions/21822650/disable-git-eol-conversions
>> >> You will probably have to checkout the repo again.
>> Thx - I'll give it a try...
No good - tried all sort of combinations for .gitconfig and .gitattributes
but none worked quite frustrating - makes no
>> https://stackoverflow.com/questions/21822650/disable-git-eol-conversions
>> You will probably have to checkout the repo again.
Thx - I'll give it a try...
https://stackoverflow.com/questions/21822650/disable-git-eol-conversions
You will probably have to checkout the repo again.
On Mon, Apr 20, 2020 at 1:23 PM Lyor Goldstein
wrote:
> >> Maven auto format might be converting it back to LF then GIT gets
> confused? Maybe just disable the
>> Maven auto format might be converting it back to LF then GIT gets
confused? Maybe just disable the conversion to CRLF?
How do I do that ?
Maven auto format might be converting it back to LF then GIT gets
confused? Maybe just disable the conversion to CRLF?
On Mon, Apr 20, 2020 at 11:03 AM Lyor Goldstein
wrote:
> >> I thought GIT does this automatically on Windows.
>
> Not entirely - there are some core settings that control it,
>> I thought GIT does this automatically on Windows.
Not entirely - there are some core settings that control it, but it is not
clear how they affect the behavior. My current setup in .gitconfig is shown
below:
[core]
autocrlf = input
filemode = false
I have been using it so far
I thought GIT does this automatically on Windows.
On Mon, Apr 20, 2020 at 10:30 AM Lyor Goldstein
wrote:
> I have just fetched the latest master branch and built it on my Windows
> machine and am getting as if all files have been changed - the change has
> to do with LF -> CRLF change in all
Yes, sorry for the noise. I must have used a not clean repo before
building or maybe not rebuild from root, not sure. Anyway, I can confirm
that it's working for me too.
Le lun. 20 avr. 2020 à 15:37, Lyor Goldstein a
écrit :
> >> I think your forgot to commit the changes to a few files:
>> I think your forgot to commit the changes to a few files: KeyUtils,
KeyPairProvider
I don't think so - I have used the cloned repository commits rather that
the PR + the code compiles and passes all tests.
I think your forgot to commit the changes to a few files: KeyUtils,
KeyPairProvider
Le dim. 19 avr. 2020 à 18:00, a écrit :
> This is an automated email from the ASF dual-hosted git repository.
>
> lgoldstein pushed a commit to branch master
> in repository
>> Unless there's a strong objection, i'll soon commit the changes in
I have no strong objection, but I am a bit confused why this is better than
checkstyle. Please bear in mind that checkstyle is not only about
indentations but also imposes what are currently considered good practices
(e.g.,
The socket buffers don’t do anything with listening TCP sockets nor do
accepted sockets automatically inherit any settings therefore it isn’t
necessary.
On Wed, Apr 15, 2020 at 5:09 AM Marcin L (Jira) wrote:
> Marcin L created DIRMINA-1123:
> -
>
>
>> unfortunately our servers are staying in corporate network which desnt
have access to outside sftp server and we wanted to use proxy over to
transfer the file.
>> Could you please help us with any java sample on sshd connection over
proxy for sftp or any documentation to use proxy would be
Hi Emmanuel,
Things are definitely moving smoothly; I can say the migration already has been
completed and
mina.a.o is served from git now.
One thing that may be good to do is add a MOVED_TO_GIT here [1]. MINA has
already been
disabled from the CMS. Also, the Jenkins job [2] seems to do its
Hi Roy,
are things moving smoothly ? When do you think we would be able to done
? (just wondering, no urgence).
Thanks a lot !
-
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail:
Thanks Guillaume! The Jenkins job for building the site has been created [1],
and a PR for moving
over is created as well [2]
Last chance to say goodbye to the CMS :P
[1] https://builds.apache.org/job/mina-site/
[2] https://github.com/apache/infrastructure-puppet/pull/1730
On 2020/02/24
I've pushed the 4 branches.
Thx !
Le lun. 24 févr. 2020 à 16:41, Roy Lenferink a
écrit :
> Thanks Emmanuel! Requesting repositories is selfservice, so indeed they
> will be available pretty
> quick :)
>
> I have everything available in my copy of the mina-site repository here
> [1]
>
> The
Hey Emanuell,
I missed the vote… but I am +1 too…
Jeff
> On Feb 24, 2020, at 8:41 AM, Roy Lenferink wrote:
>
> Thanks Emmanuel! Requesting repositories is selfservice, so indeed they will
> be available pretty
> quick :)
>
> I have everything available in my copy of the mina-site
Thanks Emmanuel! Requesting repositories is selfservice, so indeed they will be
available pretty
quick :)
I have everything available in my copy of the mina-site repository here [1]
The repository contains the 4 needed branches:
- asf-site => contains the generated content which will be
On 24/02/2020 09:38, Emmanuel Lécharny wrote:
Hi,
On 22/02/2020 16:21, Roy Lenferink wrote:
Hi,
The vote has passed with the following results:
+1 Guillaume Nodet (binding)
+1 Emmanuel Lécharny (binding)
+1 Jeff Maury (binding)
+1 Roy Lenferink (non-binding)
No -1 votes have been cast.
Hi,
On 22/02/2020 16:21, Roy Lenferink wrote:
Hi,
The vote has passed with the following results:
+1 Guillaume Nodet (binding)
+1 Emmanuel Lécharny (binding)
+1 Jeff Maury (binding)
+1 Roy Lenferink (non-binding)
No -1 votes have been cast.
To continue I'll need some help from a PMC member
Adding my +1 (non-binding) as well.
On 2020/02/19 13:45:51, Roy Lenferink wrote:
> Hi MINA community,
>
> After last weeks proposal [1] I'd like to start a formal vote for moving over
> from the current Apache
> CMS (and SVN) to use Hugo and git.
>
> Short recap about Hugo: Hugo is a static
+1
Le mer. 19 févr. 2020 16:56, Emmanuel Lécharny a
écrit :
> +1 too.
>
> On 19/02/2020 16:03, Guillaume Nodet wrote:
> > +1
> >
> > Thx for pushing that. The change will be a huge gain.
> >
> > Le mer. 19 févr. 2020 à 14:45, Roy Lenferink a
> > écrit :
> >
> >> Hi MINA community,
> >>
> >>
+1 too.
On 19/02/2020 16:03, Guillaume Nodet wrote:
+1
Thx for pushing that. The change will be a huge gain.
Le mer. 19 févr. 2020 à 14:45, Roy Lenferink a
écrit :
Hi MINA community,
After last weeks proposal [1] I'd like to start a formal vote for moving
over from the current Apache
CMS
+1
Thx for pushing that. The change will be a huge gain.
Le mer. 19 févr. 2020 à 14:45, Roy Lenferink a
écrit :
> Hi MINA community,
>
> After last weeks proposal [1] I'd like to start a formal vote for moving
> over from the current Apache
> CMS (and SVN) to use Hugo and git.
>
> Short recap
Apologies if I missed something!
This is about moving the source for the mina.apache.org site, which is
currently served from SVN [1],
to a new mina-site git repository (to be created after vote passes). This
repository will be synced
between gitbox.a.o and GitHub. After this, I will create a
Just to clarify - is this about moving to Git on GitHub, or is it
about moving to Git using a different host for the upstream
repository?
On Wed, Feb 19, 2020 at 7:52 AM Roy Lenferink wrote:
>
> Hi MINA community,
>
> After last weeks proposal [1] I'd like to start a formal vote for moving over
Hi all,
Any further thoughts on this? Otherwise I'll start a (lazy) vote for moving
over.
Roy
On 2020/02/13 12:35:33, Roy Lenferink wrote:
> Hi folks,
>
> Following up on this.
>
> After doing a bit of research I noticed Apache Beam is doing something
> similar that could be useful
> for
Hi folks,
Following up on this.
After doing a bit of research I noticed Apache Beam is doing something similar
that could be useful
for Apache MINA as well.Their generated documentation is hosted on a separate
branch, e.g.
release-docs [1] which is then propagated into the site [2].
This
Hi Emmanuel,
Thanks for your reply! See my inline comments.
On 2020/02/10 23:34:29, Emmanuel Lécharny wrote:
> Hi Roy,
>
> On 10/02/2020 16:00, Roy Lenferink wrote:
> > Hello MINA developers,
> >
> > I noticed MINA is still serving its site from SVN with help of the Apache
> > CMS.
>
> Yes.
Hi Roy,
On 10/02/2020 16:00, Roy Lenferink wrote:
Hello MINA developers,
I noticed MINA is still serving its site from SVN with help of the Apache
CMS.
Yes. It has been this way for around a decade (actually, as soon as the
CMS was proposed). before that we were using a buggy Confluence ->
Open up Wireshark and figure out what is going on.
What is the domain name on your SSL cert? Is it your IP address or is it
localhost?
On Sat, Feb 1, 2020 at 4:10 PM Kutay C. Zorlu wrote:
> Hi - ALL,
>
> I am student, I have a master thesis project, I Integrated Apache mina to
> my Project,
The release is available on the apache distribution sites, but it has a
problem syncing to central, see
https://issues.apache.org/jira/browse/INFRA-19798
I'll update the web site, but feel free to prepare an announcement email so
that we can send it when the sync is done.
Le lun. 27 janv. 2020 à
>> I'm thus closing the vote with 3 +1s and no other votes and will
publish the release and update the web site asap.
Great - let me know if you want me to publish an announcement or you will
do it.
Thanks,
Lyor
Did I miss this?
+1 from me.
Jeff
> On Jan 26, 2020, at 4:07 PM, Guillaume Nodet wrote:
>
> I think we're still missing a binding vote..., we need at least 3.
>
> Le sam. 18 janv. 2020 à 09:02, Guillaume Nodet a écrit :
>
>> I've staged a release candidate:
>> * Repo:
>>
On 27/01/2020 00:07, Guillaume Nodet wrote:
I think we're still missing a binding vote..., we need at least 3.
Hi Guillaume,
AFAICT, I count 3 +1 binding votes : you, Lyor and me...
Le sam. 18 janv. 2020 à 09:02, Guillaume Nodet a écrit :
I've staged a release candidate:
* Repo:
I think we're still missing a binding vote..., we need at least 3.
Le sam. 18 janv. 2020 à 09:02, Guillaume Nodet a écrit :
> I've staged a release candidate:
> * Repo:
> https://repository.apache.org/content/repositories/orgapachemina-1047
> * Distributions:
>
+1
Le sam. 18 janv. 2020 à 09:02, Guillaume Nodet a écrit :
> I've staged a release candidate:
> * Repo:
> https://repository.apache.org/content/repositories/orgapachemina-1047
> * Distributions:
>
My +1
Packages built from repository and distribution, signature checked.
Good to go !
On 18/01/2020 09:02, Guillaume Nodet wrote:
I've staged a release candidate:
* Repo:
https://repository.apache.org/content/repositories/orgapachemina-1047
* Distributions:
So I've removed the md5 and sha1 files for the distributions:
https://repository.apache.org/service/local/repositories/orgapachemina-1047/content/org/apache/sshd/apache-sshd/2.4.0/
Le lun. 20 janv. 2020 à 14:09, Guillaume Nodet a écrit :
> I think we're fine, we do provide the .asc PGP armored
I think we're fine, we do provide the .asc PGP armored signatures.
I'll remove the .md5 and .sha1 files from the repository.
Le lun. 20 janv. 2020 à 13:47, Emmanuel Lécharny a
écrit :
> Hi guys,
>
>
> I'm sorry, but new release *MUST* be signed using something stronger
> than MD5 or SHA1 :
>
>
Hi guys,
I'm sorry, but new release *MUST* be signed using something stronger
than MD5 or SHA1 :
https://www.apache.org/dev/release-distribution.html#sigs-and-sums :
"SHOULD NOT supply a MD5 or SHA-1 checksum file (because these are
deprecated)"
On 18/01/2020 09:02, Guillaume Nodet
Thanks Guillaume...
+1
I've staged a release candidate:
* Repo:
https://repository.apache.org/content/repositories/orgapachemina-1047
* Distributions:
https://repository.apache.org/content/repositories/orgapachemina-1047/org/apache/sshd/apache-sshd/2.4.0/
* Git Tag:
>> Some of the tests do consistently fail on my laptop during the release
process
Strange but not surprising - the MINA and NETTY tests do have inconsistent
intermittent failures . Usually if I run `mvn -rf :sshd-mina` (or whatever
failed) a few times they succeed. Note that it can happen
dump files (if any exist) [date].dump,
[date]-jvmRun[N].dump and [date].dumpstream.*
*[ERROR]* -> *[Help 1]*
*[ERROR]*
*[ERROR]* To see the full stack trace of the errors, re-run Maven with the
*-e* switch.
*[ERROR]* Re-run Maven using the *-X* switch to enable full debug logging.
*[ERRO
Great - then we can proceed
Yes, it seems to fix the issue.
Le ven. 17 janv. 2020 à 09:04, Lyor Goldstein a
écrit :
> I have downgraded the plexus.archiver.version back to 4.1.0 and now I
> believe it works (have not committed or pushed to master). Please check
it,
> and if it works make the
Yes, it seems to fix the issue.
Le ven. 17 janv. 2020 à 09:04, Lyor Goldstein a
écrit :
> I have downgraded the plexus.archiver.version back to 4.1.0 and now I
> believe it works (have not committed or pushed to master). Please check it,
> and if it works make the necessary commit in the master
I have downgraded the plexus.archiver.version back to 4.1.0 and now I
believe it works (have not committed or pushed to master). Please check it,
and if it works make the necessary commit in the master branch.
I have looked and there is no upgrade for javadoc plugin. A quick look at
the root pom.xml commit history shows (commit
794ebd83f931c15c4343480cc393c5f2cc486416)
previous
-3.4.0
-4.1.0
upgraded
+3.5.0
+4.2.1
I suggest you try the older combination and see if it
>> Sorry for the late reply.
>> I did start the release process 2 days ago but hit the following
problem.
>> Any idea ?
I will look into it and let you know shortly - I do have some ideas -
basically either try to see if there is a more recent version of the
javadoc plugin or
f foreign imports: 1
[ERROR] import: Entry[import from realm
ClassRealm[project>org.apache.sshd:sshd:2.4.0, parent:
ClassRealm[maven.api, parent: null]]]
[ERROR]
[ERROR] -
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full st
Gentle reminder..
From: Riyas K K
Sent: Monday, November 18, 2019 1:05 PM
To: dev@mina.apache.org
Subject: Reg: Bypassing Proxy with SSHD SFTP Connection
Importance: High
Hi,
Could you please help me out with setting up Proxy connection in SSHD to upload
file to SFTP.
An early response
I’ll look at this tomorrow
On Sat, Nov 2, 2019 at 8:37 PM Srikanth Chadalavada (Jira)
wrote:
>
> [
> https://issues.apache.org/jira/browse/DIRMINA-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16965529#comment-16965529
> ]
>
> Srikanth Chadalavada edited comment
Hi Bruce,
the difference between MINA 2.0 and 2.1 is explained on this page :
http://mina.apache.org/mina-project/2.1-vs-2.0.html
I don't think that impacts SSHd, as sshd-mina module does not check if
the session is secured, it is supposed to be secured anyway !
FTR, the mechanism is
Hi All,
I have a diferent problem now
I want to use the scpclient tp upload and download files
Is there a way to upload and download as a different user
e.g connect as user A and upload as user B using different passwords
Please let me know
Thanks
Prajwal
On 10/16/2019 9:12 PM, Prajwal
Hi Prajwal,
Did you see and try something like this?
https://mina.apache.org/sshd-project/tips.html
---
*Thanks & Regards*,
Vijay Shanker |*Software Architect*
On Wed, Oct 16, 2019 at 9:15 PM Prajwal M wrote:
> Hi All,
>
> I am currently trying to migrate from JSCH to MINA sshd api's
>
>
We do not have any current PKCS11 support in MINA SSHD. We do support SSH
agents in general, so one could add the necessary support - Java even seems
to have some PKCS11 support in it (
https://docs.oracle.com/javase/7/docs/technotes/guides/security/p11guide.html)
but I have never looked into it.
1101 - 1200 of 11689 matches
Mail list logo
