SSH again

[yoh-dah]

Please be fore-warned that any talk of breaking into the ReadyNAS will NOT be tolerated on this forum . The forum exists for the reason of supporting our customers with legitimate problems and listening to our users for feedback and feature requests. We understand that shell access is a desired feature, and we've already committed to doing this.

Hi yoh-dah,
I accept that Infrant is waiting to open ssh to protect their development
and to avoid users to mess up their system. Fine!

But in the mean time I would appreciate if you give the owner the right to
close your ssh remote support backdoor through Frontview and open it when its needed!!!

Is it a crime in the US when you break in your own house when you have lost the key?
I was not aware of this law.
Thanks

Andi, the "backdoor" actually requires you to forward port 22 on your router to the ReadyNAS. Without the port forwarding, there's no way we can remotely access your box. The reason why we do enable this is that there are some cases where users have lost web access to the box, but we can get through with ssh to fix a problem nevertheless -- of course with user permission and forwarding of the ssh port. And also keep in mind that each box has a unique password and we don't know what your router IP is. So to complete your analogy, we would need for you to tell us your home address, let you unlock the front door before we can try to unlock your file cabinet.

[andi]

Andi, the "backdoor" actually requires you to forward port 22 on your router to the ReadyNAS. Without the port forwarding, there's no way we can remotely access your box. The reason why we do enable this is that there are some cases where users have lost web access to the box, but we can get through with ssh to fix a problem nevertheless -- of course with user permission and forwarding of the ssh port. And also keep in mind that each box has a unique password and we don't know what your router IP is. So with complete your analogy, we would need for you to tell us your home address, let you unlock the front door before we can try to unlock your file cabinet.

Yes, nevertheless I would feel saver if you let me lock the backdoor myself.
I can decide to open it when you need access. Please consider to give the owner this option in Frontview.
I take the risk if I lose the key.

Regarding the analogy.
Yes, I know my home address and you know it too as you can see the public IP address from this post.

[bhoar]

Yes, nevertheless I would feel saver if you let me lock the backdoor myself.
I can decide to open it when you need access. Please consider to give the owner this option in Frontview.
I take the risk if I lose the key.

I can see why Infrant wants to ensure that the door can be opened, even if the User Interface (Frontview) becomes unavailable. That allows them to fix things so that customers who have lost access to their boxes are not forced to go to data recovery specialists and pay a huge chunk of money to get to the data again.

I like the idea of the option, but I'd only be in favor of this option if the 5-second-OS-reinstall process always forced the port 22 to become available again for ssh by Infrant.

-brendan

[andi]

I like the idea of the option, but I'd only be in favor of this option if the 5-second-OS-reinstall process always forced the port 22 to become available again for ssh by Infrant.

-brendan

Hi Brendan,

yes, that would be a good compromise that suits both Infrants any my needs. Great idea! Thank you

[grill]

We understand that shell access is a desired feature, and we've already committed to doing this.

yoh-dah,

Does this mean you are 'commited' to "shell" access or "root/shell" access?

Big difference there...

I vote for "root/shell".

G./

P.S. Still on the fence...

[yoh-dah]

Does this mean you are 'commited' to "shell" access or "root/shell" access?

That's definitely our goal.

[grill]

Does this mean you are 'commited' to "shell" access or "root/shell" access?

That's definitely our goal.

Didn't really answer my question did you?

Is it "we are committed to give you SSH/TELNET access, but not with root access"?

Or is it "we are committed to give you SSH/TELNET access, WITH root access"?

G./

[yoh-dah]

Does this mean you are 'commited' to "shell" access or "root/shell" access?

That's definitely our goal.

Didn't really answer my question did you?

Is it "we are committed to give you SSH/TELNET access, but not with root access"?

Or is it "we are committed to give you SSH/TELNET access, WITH root access"?

G./

Sorry, too many late night drinking Our goal is for root access.

[Hi-Jack]

Opening root access will have the Infrant popularity blow way up...
I dissagree opening it will cause data loss and all that nonsens...

There are hundreds of projects going on this kind of devices with a
userbase of millions. You can't avoid having problems but the big crowd is
happy getting more out of the product... and they can install it with install
packages and don't need to start poking around...

If a good resource page is build that accepts only user friendly packages
and with own in house dev to make more difficult packages easier i doubt
a lot of people will have issues.

There's more options then black and white. A good balance will make
everyone happy and it's all true according to the info we get through
thousands of people interested, once the community can start adding
features, it will be the device they will buy.

Things will really start boiling if a timeline is set which from my point of
view, considering the last final release not being so long ago, can take
several months from today.

This way of messaging could mean it will come in 2015 or might be here
tomorrow. Nothing you can build on just yet but I trust it will be done
before the end of 2006.

Brands just love to keep us longing...
It's marketing (and safe to not get the "you promised us by now.... blabla
kind of posts if the targeted dates are not met)

ENjoy
Hi-Jack

[bhoar]

Here I go guessing again, but I suspect that in order to enable root access, you'll have to click through a warranty modification page, with perhaps the creation of a notification email/packet sent to Infrant that you've "broken the seal" around the OS partition.

This way, they'd no longer be responsible for proper operation of the entire device, but rather, just the hardware itself. And therefore, they'd be less willing to offer help in data recovery on such a unit.

Even then, there might be further warranty limitations for the hardware, because certain lifetime-effecting things, such as fan rates, are software modifiable.

-brendan

[derek]

Here I go guessing again, but I suspect that in order to enable root access, you'll have to click through a warranty modification page, with perhaps the creation of a notification email/packet sent to Infrant that you've "broken the seal" around the OS partition.

This way, they'd no longer be responsible for proper operation of the entire device, but rather, just the hardware itself. And therefore, they'd be less willing to offer help in data recovery on such a unit.

Even then, there might be further warranty limitations for the hardware, because certain lifetime-effecting things, such as fan rates, are software modifiable.

-brendan

ya i figure the same, a CoverYourAss for infrant. someone will fsck up their system, then try and get infrant to fix it for them, i wouldnt want to support that either.

main thing id be doing myself would be making symlinks in the main share to the usb drives i have, so i dont need to mount 5 separate shares, just 1. some things i just wouldnt want on the nas with its limited cpu, bye bye fast transfer speeds.

[moffutt]

I saw an end of Q2 for this functionality. Any progress?

[bhoar]

I saw an end of Q2 for this functionality. Any progress?

Last I read it was end of Q4 2006 or Q1 2007. I wouldn't be surprised if they'd said Q2, though.

-brendan

[Signal64]

brendan - was that posted somewhere else?

[bhoar]

brendan - was that posted somewhere else?

That's just from my memory, I'm not sure where I read it.

-brendan